Build your own Adobe Acrobat Sign alternative
You're building the tool your team uses to send agreements for signature and see where each one stands. Vibe code the sending flow and the tracking dashboard with Cursor, Claude Code or Lovable, and Esign Comply gives your AI tool the signing rules and keeps the independent record of every signature.
Free plan: 10 live signatures a month and a full test mode. No card required.
- 01Pick an agreement and its recipientsYou
- 02Send for signature by emailYou
- 03Recipient signs on your pageYou
- 04Ceremony reported from the recipient's browserEsign Comply
- 05Sealed record and signed webhookEsign Comply
- 06Status flips to signed in your dashboardYou
What you're building: an agreements desk
An agreements desk for your company: send, chase, track, file. These are the parts.
Send for signature
Choose a PDF or a saved agreement, add recipients, write a message, send.
Recipients in order
Route an agreement through several people, one after another or all at once.
An agreements list
Every agreement your team has sent, with search, filters and owners.
Live status
Out for signature, viewed, signed, completed, declined, expired, at a glance.
Reminders and deadlines
Automatic nudges and an expiry date for agreements that stall.
Typed or drawn signatures
Recipients sign on a page in your app, on a laptop or a phone.
A history per agreement
Each event in order: sent, opened, signed, with the version it applied to.
Signed copies on file
The completed PDF is stored with the agreement and emailed to every party.
Who does what in your Adobe Acrobat Sign alternative
Sending, chasing and tracking are your product. Esign Comply supplies the rules for the signing page, tells your server when a signature lands and holds the record.
Agreement library and upload
The library, the upload form and your saved agreements.
Registers each agreement you send as an immutable document version with a content hash.
Recipients and routing
The recipient list, the routing order and the packet.
One session per recipient on the same document version, each with its own sealed record.
Sending and reminders
The invitation, the reminders and the deadline, from your domain with a provider such as Resend.
The one-time code email at L2, sent and confirmed by Esign Comply.
The signing page
The viewer, the fields, the notice, the signature control and the button.
The rules prompt for the page, and the browser SDK that reports the ceremony from the recipient's browser.
Status tracking
The status column, the filters and the notifications to the sender.
Signed webhooks your server acts on: record.completed, session.expired, session.cancelled.
History and proof
The timeline you show on each agreement.
The sealed record, a signed receipt (ES256), an RFC 3161 timestamp, an evidence report and a public verification page.
Signed copies
The completed PDF, stamped for example with pdf-lib, filed and emailed.
An optional emailed copy to each signer, from Esign Comply's own domain.
How to build your Adobe Acrobat Sign alternative, step by step
Nine steps from Send to a status board you can trust, because every signed badge is backed by a confirmed record.
- 01
Generate the prompt
In the Esign Comply dashboard, pick contract signing, your regions, your signer types and your stack, and choose webhook confirmation. Paste the prompt into Cursor, Claude Code, v0, Lovable, Bolt or Replit.
Prompt generatorUse case Contract signing Method Typed name or drawn signature Assurance L2, one-time code by email Confirmation Webhook Stack Next.js on Vercel, Supabase
- 02
Register the agreement as a document version
When a sender clicks Send, your server publishes the PDF as a version and stores the returned
dv_ID and content hash on the agreement. That version never changes, and every recipient signs the same one.Server · on SendPOST /v1/documents/doc_Ag17/versions Idempotency-Key: agreement-5530 { "version_label": "agreement-5530", "content": { "format": "pdf", "data_base64": "JVBERi0xLjcK..." } } // 201 Created { "id": "dv_3kT9", "content_hash": "sha256:9f2c..." }
- 03
Create one session per recipient
Each recipient gets their own session on that same document version, created on your server when they open their link. It is one session per signer: your app holds the packet and decides who is next in the routing order.
Server · when a recipient opens their link// One session per recipient. Your app owns the routing order. // esc is the server SDK: new EsignComply(process.env.ESIGNCOMPLY_API_KEY) const { data: session, error } = await esc.sessions.create( { profile: "prof_agreements_2d9a", // typed name, L2 signer: { external_id: recipient.id, email: recipient.email, name: recipient.name, class: "business", country: "US", }, documents: [ { document: agreement.documentId, version: agreement.versionId }, ], context: { url: `${origin}/agreements/sign/${recipient.token}`, locale: "en-US", purpose: "contract_signature", }, metadata: { agreement_id: agreement.id }, }, { idempotencyKey: `sign-${agreement.id}-${recipient.id}-${attempt}` }, ); // Send the browser only session.client_token, session.api_url // and session.documents.
- 04
Email each recipient their link
Send the invitation from your own domain with a provider such as Resend. In a sequential route, email the next recipient when your server has confirmed the record of the one before.
Server · send for signatureimport { Resend } from "resend"; const resend = new Resend(process.env.RESEND_API_KEY); const url = `https://yourapp.com/agreements/sign/${recipient.token}`; await resend.emails.send({ from: "Acme Agreements <agreements@yourdomain.com>", to: recipient.email, subject: `Signature requested: ${agreement.title}`, html: `<p><a href="${url}">Review and sign</a></p>`, });
- 05
Build the signing page with the browser SDK
The recipient sees your viewer, your notice and your Sign button, and
@esigncomply/browserattaches to them and reports each step from the recipient's browser. A Decline button callsceremony.cancel().Browser · app/agreements/sign/[token]/signing.tsximport { EsignComply } from "@esigncomply/browser"; const ceremony = await EsignComply.attach({ clientToken, apiUrl }); await ceremony.presentDocument({ versionId, mode: "scrollbox", container: viewer, }); // L2: a one-time code to the recipient's email await ceremony.verify.start({ method: "email_otp" }); await ceremony.verify.confirm({ code: codeInput.value }); // typedName for a typed signature, canvas for a drawn one ceremony.observeAssent({ region: assent, typedName: nameInput, submit: signButton, }); // From the click handler of your Sign button const result = await ceremony.complete(); // { recordId, receipt, verifyUrl, status } // From the click handler of your Decline button await ceremony.cancel();
- 06
Confirm on your server before the status changes
Signed is a server decision. Read
GET /v1with the secret key in the request that follows the signing act, and handle the signed/records /{id} record.completedwebhook for recipients who closed the tab.Server · confirm, then update the status// Runs after complete() and again from the record.completed webhook. const { data: record, error } = await esc.records.get(recordId); const confirmed = !error && ["recorded", "timestamped", "anchored"].includes(record.status) && record.signer.external_id === recipient.id && record.documents.every((d) => d.version_id === agreement.versionId) && record.livemode === (process.env.VERCEL_ENV === "production"); if (confirmed) { await markSigned(recipient.id, record.id, record.receipt); }
- 07
Produce the completed PDF and send copies
When every recipient has a confirmed record, stamp the names, signature images and dates onto the PDF, for example with pdf-lib, file it with the agreement and email it to every party.
- 08
Track status in your dashboard
Every status on your board maps to something your server knows. Derive it from your own rows, from confirmed records and from the session webhooks.
Your status columnout_for_signature invitation sent, link not opened yet viewed recipient opened the link, session created signed record confirmed on your server completed every recipient has a confirmed record declined session.cancelled with cancelled_by: signer expired your own deadline passed
- 09
Keep our receipt and offer the evidence report
Store the signed receipt and the record ID on each recipient row. From the agreement's history, link the public verification page and let the sender download the evidence report for each signature.
Server · evidence for one signature// Use a key with full_access or read_only permission GET /v1/records/rec_Ad44/report // evidence report (PDF) GET /v1/records/rec_Ad44/evidence // evidence package (ZIP) // Anyone checks the package offline npx esigncomply-verify rec_Ad44.zip
A starter prompt to paste into your AI tool
Paste this first so your AI tool builds the sending flow and the tracking board. Then paste the generated prompt from the dashboard.
Generate the full promptBuild an agreement sending and tracking app in this codebase, in the style of Adobe Acrobat Sign. A sender picks a PDF, adds recipients in order and clicks Send. Each recipient gets an email (use Resend) linking to a signing page in our app. There they read the agreement, confirm a one-time code sent to their email, then sign with a typed or drawn signature, or decline. Add an agreements list with statuses (out for signature, viewed, signed, completed, declined, expired), reminders and a deadline. When all have signed, stamp the PDF with pdf-lib and email everyone the completed copy. Use Esign Comply for the signing ceremony and the record. First read and follow https://esigncomply.com/setup.md and https://esigncomply.com/llms.txt. Never invent API methods, endpoints or parameters: if the docs do not cover it, stop and ask me. One Esign Comply session per recipient on the same document version. Our database holds the packet and routing order. Set signed only after our server has confirmed the record, and handle the record.completed webhook. Next I will paste the prompt generated in the Esign Comply dashboard. It has the exact rules for the signing screen and overrides this message.
Why not build the record yourself
A status board is only as good as the thing behind the word signed. If that is a boolean your own app set, a recipient who disputes it is arguing with your database, and you are the one who administers it. Esign Comply receives each ceremony from the recipient's browser, seals the record with keys you do not hold, timestamps it through an outside authority (RFC 3161) and chains it into an append-only ledger with signed checkpoints. Your board shows signed, and the evidence package behind it verifies offline for anyone you send it to.
Why the record should not be yoursPricing in one line
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, so an agreement routed through three recipients is three events.
See pricingQuestions about building your own Adobe Acrobat Sign
Can I build an Adobe Sign alternative with Cursor or Claude Code?
Yes. Sending, routing, reminders and the tracking dashboard are standard product code for Cursor, Claude Code, Lovable, v0, Bolt or Replit. Esign Comply generates one prompt with the rules for the signing page and sends your server a signed webhook the moment a signature is recorded.
Generate a promptHow do I track the status of an agreement?
Status lives in your own database. A recipient becomes signed when your server confirms their record with GET /v1/records/{id} or the record.completed webhook, and an agreement becomes completed when every recipient is signed. Declines arrive as session.cancelled and timeouts as session.expired.
Webhook eventsHow do multiple recipients work?
Create one session per recipient on the same document version. Each recipient signs in their own ceremony and gets their own sealed record. Your app tracks the packet and the routing order, and emails the next person when the previous record is confirmed.
Who sends the invitations and reminders?
You do, from your own domain, with a provider such as Resend. That covers invitations, reminders, expiry notices and the completed copy. Esign Comply sends the one-time code used to verify a recipient's email, and an optional receipt to each signer with a copy and a verification link.
Is a signature collected in my own app recognized?
Yes. Electronic signatures are recognized under the U.S. ESIGN Act and state UETA laws, under which a signature cannot be denied legal effect just because it is electronic. Esign Comply supplies ceremony rules drawn from those laws and from leading U.S. online-assent decisions, then seals a hash-chained record of each signature and has an outside authority timestamp it.
U.S. rules we draw onSend, sign and track in your own app. Leave the record to us.
Free plan: 10 live signatures a month and a full test mode. No card required.
Adobe Acrobat Sign is a trademark of its owner. Esign Comply is not affiliated with it.