Build your own Dropbox Sign alternative
You're putting a signature step inside your product, the way Dropbox Sign (HelloSign) embeds one, and you want it to be your own component. Vibe code the embedded signing screen and the templates, and Esign Comply gives your AI tool the signing rules and keeps the independent record.
Free plan: 10 live signatures a month and a full test mode. No card required.
- 01Fill a template from your databaseYou
- 02Show the signing step inside your productYou
- 03User types a name and clicks SignYou
- 04Ceremony reported from the user's browserEsign Comply
- 05Sealed record, receipt and timestampEsign Comply
- 06Unlock the next step, deliver the copyYou
What you're building: embedded signing with templates
Signing that feels like one more screen of your app, plus the template machinery behind it.
Embedded signing
The signature step lives inside your product: an onboarding screen, a modal, a settings page. Nobody leaves for another site.
Templates
Reusable agreements with merge fields for names, dates and amounts.
Data from your database
Your app fills each agreement from the account, so nobody retypes what you already know.
Requests from your backend
Your server opens a signature request when something happens: a new contractor, a new order, a plan change.
Signer roles
Customer and company, contractor and client. Each role signs their own part.
Typed or drawn signatures
A name field or a signature pad, built from your own design system.
Status your code can act on
Your app knows the moment a request is signed and moves the user forward.
Signed copies
The final PDF sits in the user's account and lands in their inbox.
Who does what in your Dropbox Sign alternative
The component, the templates and the product logic are yours. Esign Comply supplies the rules for the screen and holds the record of each signature.
Templates and merge fields
The template editor, the merge fields and the filled agreement.
Registers each filled agreement as an immutable version, so the record pins the exact text that signer saw.
The embedded signing screen
The component inside your product: document, notice, name field or signature pad, button.
The browser SDK attaches to your elements and reports the ceremony from the signer's browser.
The rules for that screen
Pasting one prompt into your AI tool and reviewing what it builds.
The generated prompt: ceremony rules for your use case, regions, signer types and stack.
Who the signer is
Your own login. You pass the user's ID, name and email when your server creates the session.
At L2, sends a one-time code to that email and confirms it inside the ceremony.
Unlocking the next step
The server check that flips your own signed flag and continues the flow.
GET /v1 and the signed record.completed webhook to confirm against.
Signed PDF and copies
Rendering the final PDF with names and signature images, storing it, emailing it.
The evidence report for each record, the public verification page and the optional emailed copy to the signer.
The record
Our receipt, stored next to your own row.
The sealed record, a signed receipt (ES256), an RFC 3161 timestamp and a hash-chained ledger.
Request lists and admin
Lists, filters, team permissions and billing inside your product.
The record ID on every signature, to join your rows to ours.
How to build your Dropbox Sign alternative, step by step
Nine steps from a template to a signed agreement inside your product.
- 01
Generate the prompt
In the Esign Comply dashboard, pick contract signing, your regions, your signer types and the stack your product runs on. Paste the prompt into your AI tool: it carries the ceremony rules for the embedded screen.
Prompt generatorUse case Contract signing Method Typed name Assurance L2, one-time code by email Signers Business or consumer Stack Your framework, your database
- 02
Turn a filled template into a document version
Fill the merge fields on your server, then publish the result as a version: Markdown, HTML, plain text or PDF. Each filled agreement gets its own version, so two customers never share one.
Server · publish the filled templatePOST /v1/documents/doc_Ms02/versions Idempotency-Key: contractor-agreement-acct_5521 { "version_label": "acct_5521-2026-11-22", "content": { "format": "html", "text": "<h1>Contractor Agreement</h1>..." } } // 201 Created { "id": "dv_Qk18", "render_hash": "sha256:77d0..." }
- 03
Create one session for the signed-in user
The signer is the user in front of you, so pass your own user ID as
external_id. It is one session per signer: when a second party countersigns, they get their own session on the same document version, and your app tracks who is left.Server · start the embedded ceremony// Called by your signing component. One session per signer. // esc is the server SDK: new EsignComply(process.env.ESIGNCOMPLY_API_KEY) const { data: session, error } = await esc.sessions.create( { profile: "prof_embedded_4f1a", // typed name, L2 signer: { external_id: user.id, email: user.email, name: user.name, class: "business", country: user.country, }, documents: [ { document: request.documentId, version: request.versionId }, ], context: { url: `${origin}/onboarding/agreement`, locale: "en-US", purpose: "contract_signature", }, metadata: { request_id: request.id }, }, { idempotencyKey: `request-${request.id}-${user.id}-${attempt}` }, ); // Send the browser only session.client_token, session.api_url // and session.documents.
- 04
Bring each signer to the screen
Inside your product the link is a route: show the signing step where the user already is. For a signer who is away, or a countersigner on the other side, email a link to that route with a provider such as Resend.
Server · email a signer who is awayimport { Resend } from "resend"; const resend = new Resend(process.env.RESEND_API_KEY); const url = `https://yourapp.com/requests/${request.id}/sign`; await resend.emails.send({ from: "Acme <agreements@yourdomain.com>", to: countersigner.email, subject: `${request.title} is ready for your signature`, html: `<p><a href="${url}">Open the agreement</a></p>`, });
- 05
Embed the signing component with the browser SDK
Render the registered HTML unmodified inside your component, then attach
@esigncomply/browser, which reports each step from the signer's browser. In React, the@esigncomply/reacthooks wrap the same calls.Browser · components/sign-agreement.tsximport { EsignComply } from "@esigncomply/browser"; const ceremony = await EsignComply.attach({ clientToken, apiUrl }); // The <article data-esc-document> that holds the registered HTML await ceremony.presentDocument({ versionId, mode: "inline", container: article, }); // L2: the code goes to the email on the session await ceremony.verify.start({ method: "email_otp" }); await ceremony.verify.confirm({ code: codeInput.value }); 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 }
- 06
Confirm on your server, then unlock
The browser result is a claim. Your server reads
GET /v1with the secret key, or handles the signed/records /{id} record.completedwebhook, before it marks the request signed and lets the user continue.Server · confirm, then continue the flow// Only a confirmed record moves the user to the next screen. const { data: record, error } = await esc.records.get(recordId); const confirmed = !error && ["recorded", "timestamped", "anchored"].includes(record.status) && record.signer.external_id === user.id && record.documents.every((d) => d.version_id === request.versionId) && record.livemode === (process.env.VERCEL_ENV === "production"); if (confirmed) { await completeRequest(request.id, record.id, record.receipt); }
- 07
Render the signed PDF and deliver copies
Render the filled agreement to a PDF with each typed name, the signing time and the verification link, store it in the user's account and email it to both sides. With receipts on, Esign Comply also emails the signer a copy and a verification link.
- 08
Show request status inside your product
Awaiting signature, signed, countersigned: keep the status on your own request row and update it from server confirmation and the
record.completedwebhook. A badge on the account page is enough to start. - 09
Keep our receipt and offer the evidence report
Store the signed receipt with the request. Give your support team a button that downloads the evidence report, and link the public verification page next to the signed copy.
Server · evidence for one request// Use a key with full_access or read_only permission GET /v1/records/rec_Hn72/report // evidence report (PDF) GET /v1/records/rec_Hn72/evidence // evidence package (ZIP) // Anyone checks the package offline npx esigncomply-verify rec_Hn72.zip
A starter prompt to paste into your AI tool
Paste this first so your AI tool knows the shape of the feature. Then paste the generated prompt from the dashboard.
Generate the full promptAdd embedded signing to this product, in the style of Dropbox Sign (HelloSign), as our own component. Build agreement templates with merge fields (names, dates, amounts) that our server fills from the database. At the signing step, show the filled agreement inside our app with an emailed one-time code, a name field and a Sign button. No iframe, no redirect. After signing, unlock the next step, render a signed PDF, store it on the account and email a copy with Resend. If a second party countersigns, email them a link to the same screen. 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. Publish each filled agreement as its own Esign Comply document version. Create one session per signer on that version, with our user ID as the signer's external_id. Unlock anything only after our server has confirmed the record. 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
An embedded signing step that only writes to your own database leaves you as the single witness to your own contracts. Anyone with access to that database could have changed the row, and the other side knows it. With Esign Comply the ceremony goes from the signer's browser to a record sealed with keys you do not hold, timestamped by an outside authority (RFC 3161) and chained into an append-only ledger. You keep the receipt, and anyone you hand the evidence package to verifies it offline.
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. An agreement that a customer signs and you countersign is two events.
See pricingQuestions about building your own Dropbox Sign
Can I build embedded signing with Claude Code or Cursor?
Yes. Your AI tool builds the signing component, the templates and the server routes inside your existing product. Esign Comply generates one prompt with the ceremony rules for your stack, and a conformance check over your test records shows what is missing before you go live.
Generate a promptIs embedded signing an iframe?
It is your own component. The Esign Comply browser SDK is headless: it renders nothing and attaches to the document container, name field and button you built. Your design system, your fonts and your domain stay on screen the whole time.
How the SDK worksHow do templates work?
Templates live in your app. Your server fills the merge fields and publishes the result to Esign Comply as an immutable document version in Markdown, HTML, plain text or PDF. The record pins that version by hash, so it names the exact text each signer saw.
How do multiple signers work?
Create one session per signer on the same document version. A customer and your countersigner each run their own ceremony and each get their own sealed record. Your app tracks the request and the order, and treats it as done when your server has confirmed every record.
Is a signature made inside my product recognized?
Yes. Under the U.S. ESIGN Act and state UETA laws, a signature cannot be denied legal effect just because it is electronic, and that covers a signature made inside your product. The ceremony rules your AI tool follows are drawn from those laws and from leading U.S. online-assent decisions. Each signing is kept as an independent, tamper-evident record, signed with keys you do not hold.
U.S. rules we draw onPut signing inside your product. Leave the record to us.
Free plan: 10 live signatures a month and a full test mode. No card required.
Dropbox Sign (formerly HelloSign) is a trademark of its owner. Esign Comply is not affiliated with it.