Stop Sending Your Contracts to DocuSign: Self-Hosted E-Signatures Explained

Self-hosted digital signatures explained: how Form.io E-Sign+ signs submission data with a private key you own, inside your own environment, with no DocuSign, Adobe Sign, or PDF round trip. Most e-signature tools sign a document. E-Sign+ signs the data, so it knows when the data changes. Everything you see here runs on a real Form.io Enterprise server, and the repo below has the full setup so you can follow along on your own. 👉 Read the Form.io E-Sign+ Documentation: https://help.form.io/dev/form.io-e-sign+ 📁 LINKS & RESOURCES * Form.io E-Sign+ Documentation: https://help.form.io/dev/form.io-e-sign+ * E-Sign+ Product Announcement: https://form.io/product-announcement/introducing-e-sign-plus-enterprise-digital-signatures-for-self-hosted-applications/ * Part 1, What Is a Schema-Driven Form?: https://youtu.be/QyNpQTmeAKk 🧠 WHAT WE COVER The usual e-signature flow exports a submission to a PDF, sends it to a signing platform, and gets a different PDF back. Your data has left your environment, and the signature lives on a document instead of the record. In government, healthcare, banking, and insurance, that's a compliance conversation every time. In this walkthrough we stand up Form.io E-Sign+ from scratch and take one purchase request through a three-person approval chain, with every signature stored on the data itself. * Standing it up: two environment variables, a 2048-bit RSA key you own, and AWS KMS for production * Scoped approvals with signedData: change the quantity from 1 to 50 and two signatures clear, while the accountant's budget approval stays valid * Any field can sign: signature pads, checkboxes, typed names, dates, and file uploads * No signature code in your client: plain REST calls, and the server signs based on the form's configuration * The eSignatures array: who signed, when, what they covered, and whether it still holds, on a normal GET * Stamps in your own app with @formio/esignature in about five lines * Agent-ready approvals: a procurement agent that checks every signature before it releases a purchase order ⏱️ CHAPTERS 0:00 Why two of three signatures cleared themselves 0:50 What is Form.io E-Sign+? 2:20 Configure, sign, use: the three-step map 3:10 Setup: Docker, RSA keys, and the admin API 8:10 Building the approval chain with signedData 11:10 Signing through the normal REST API 13:00 What travels with the submission 15:10 Signature stamps in your own app 17:40 AI agents that check approvals before paying 19:30 Recap and next steps ❓ QUESTIONS THIS VIDEO ANSWERS * What is Form.io E-Sign+? * How do you add digital signatures to a self-hosted app without DocuSign? * How do you keep e-signatures inside your own environment for compliance? * What happens to a digital signature when the signed data changes? * How do you build an approval chain where each approver signs different fields? * How do you read signature status through the Form.io REST API? * How can an AI agent verify approvals before taking action? 🧰 STACK & PARADIGMS Form.io Enterprise, Form.io E-Sign+, @formio/esignature, Docker Compose, MongoDB, RSA Keys, AWS KMS, REST API, Digital Signatures, Approval Workflows, AI Agents #SoftwareEngineering #WebDevelopment #DigitalSignatures #Compliance #SystemDesign #AIAgents