Vibe code the interface. Don't vibe code the record.
You're vibe coding e-signatures into your own app with Cursor, Claude Code, v0, Lovable, Bolt or Replit. Good. Build every screen that way. Two parts are different: the rules the signing screen follows, and the record that shows what happened. We give your AI tool the rules and keep the record, so it doesn't live in a table you can edit.
Every screen: the upload UI, the PDF viewer, field placement, the signed PDF, the emails, signer links, the dashboard, templates, teams and billing.
The rules the signing screen follows, and the record of what the signer was shown and what they did.
Esign Comply gives the rules to your AI tool in one prompt and keeps the record outside your database.
What to vibe code, and what to hand off
An AI coding tool is fast at anything you can look at and correct. A signing flow has two parts you cannot check by looking at the screen.
The interface
Everything a sender or a signer sees is yours to build: the upload UI, the PDF viewer, field placement, the signed PDF itself, invitation and reminder emails, signer links, the sender dashboard, templates, teams and billing. When a screen is wrong you see it, prompt again and ship the fix.
Build your own DocuSign-style appThe rules
Ask a tool to "add e-signature" and you get a page that looks finished: a ticked box, a line of gray text, a link to /terms. Nothing on the screen tells you the box has to start unchecked or that the notice has to name the button. We put the rules in the prompt, measure the page your tool built and report each miss with its fix.
The record
A row in your database is written by your code and editable by anyone with access to it. You are also a party to the agreement that row describes. The record belongs with someone who is not: sealed when the signer acts, signed with keys you do not hold, timestamped by an outside authority.
Why a third party keeps the recordElectronic signatures are recognized under the U.S. ESIGN Act and state UETA laws: a signature cannot be denied legal effect just because it is electronic. So the checkbox is not the hard part. The hard part comes later, when you have to show what the screen presented, what the signer did and when.
A row in your table, next to a sealed record
Both exist after a signup. Only one of them is clickwrap evidence you can hand to someone who has no reason to take your word for it.
The row your AI tool writes
| user_id | terms_version | accepted_at |
|---|---|---|
| user_7c1d | v3 | 2026-11-21 15:03:20+00 |
- Your server wrote it, or the browser did if your tool wired the insert on the client.
- Anyone with database access can change it, and the row looks the same afterward.
- It holds nothing about what the page showed or what the signer clicked.
The record we seal
- events[]
- Each step, reported from the signer's browser straight to us: documents presented, notice, assent, the signing act.
- documents[]
- The exact version of each document, pinned by SHA-256 hash.
- receipt
- Signed by Esign Comply with ES256 keys you do not hold.
- timestamp
- An RFC 3161 token from an outside authority over the record hash.
- ledger
- A place in a hash-chained, append-only ledger with signed checkpoints and a public anchor.
The row says it happened. The record shows it.
Evidence and verification referenceA customer says they never agreed to auto-renewal
They signed up a year ago. The renewal charge lands, and they tell you and their card issuer they never agreed to it. This is what you can put in front of someone outside your company.
From your own table
- One row: a user ID, a version label and a time from your own server.
- The terms page as it reads today.
- Your statement that nobody touched the row in a year.
From the sealed record
- The evidence report: the exact terms by hash, the notice, the checkbox label and the button text, and our server time for each event, the renewal consent included.
- The receipt you stored a year ago, signed with keys you do not hold.
- The evidence package, which the other side verifies offline with an open-source tool.
How a signature gets recorded when you build the UI yourself
Five steps. Your AI tool does the first two. The rest happens behind the page it built, and you never host a signing page of ours.
The Free plan includes a full test mode and 10 live signatures a month, so you can run all five steps before you pay for anything. Building a full signing product with documents and emailed links? Start with the build guide.
- 01You generate a promptPick your use case, regions, signer types and stack. You get one prompt with the rules for that flow.
- 02Your AI tool builds the screensPaste the prompt into Cursor, Claude Code, v0, Lovable, Bolt or Replit. It builds the signing page in your own UI, with your components.
- 03The signer's browser reports each stepThe headless SDK attaches to your checkbox and button. It reports the documents presented, the notice, the assent and the signing act straight to Esign Comply.
- 04We seal the recordThe record is hashed, chained into the ledger and signed. An outside authority timestamps it.
- 05You keep the receipt
complete()returns a signed receipt. Your server confirms the record withGET /v1and stores the receipt next to the user./records /{id}
The argument, one page at a time
- Who keeps itWhy a third party keeps the recordYou are a party to the agreement. See what changes when someone who is not holds the evidence.Read it
- What goes wrong7 things AI coding tools get wrongPre-checked boxes, vague notices, links to terms that change, and four more, each as code with the fix.Read it
- How it worksHow the record stays tamper-evidentHash, chain, signature, outside timestamp, Merkle checkpoints and offline verification, step by step.Read it
Questions about vibe coding e-signatures
Is it OK to vibe code e-signatures?
Yes. Vibe code every screen: the upload UI, the PDF viewer, field placement, the signing page, the emails and the dashboard. Two parts need more than a prompt: the rules the signing screen follows, and the record of what happened. Esign Comply gives your AI tool the rules and keeps the record.
Build your own signing appWhat part of an e-signature flow should I not build myself?
The record. A row in your own database is written by your code and editable by anyone with database access, and you are a party to the agreement it describes. Esign Comply receives the signing events straight from the signer's browser, seals them into a tamper-evident record and returns a signed receipt for you to store.
Why a third party keeps the recordCan I add a hash or an audit log to my own table instead?
A hash you compute and store yourself can be recomputed by you after an edit, so it shows nothing to anyone else. The seal has to come from someone who is not a party: a signature made with keys you do not hold, a timestamp from an outside authority, and a ledger you cannot rewrite. That is what the receipt, the RFC 3161 timestamp and the hash-chained ledger are.
How the record stays tamper-evidentWhat does an AI coding tool get wrong when I ask it to add e-signature?
Pre-checked boxes, notices that name neither the documents nor the button, a notice the signer has to scroll to find, tiny gray text, and links to whatever version of the terms is deployed today. The generated prompt gives your tool the rule for each one up front, and the conformance check reports every miss with its fix.
7 things AI coding tools get wrongHow much does Esign Comply cost?
The Free plan includes 10 live signatures a month and a full test mode, with no card. Starter is $200 per year for 2,000 live signature events, Unlimited is $1,200 per year, and Enterprise starts at $10,000 per year. One event is one signer's completed signing act.
See pricingPrompt the interface. Hand off the record.
Free plan: 10 live signatures a month and a full test mode. No card required.