Build your own DocSend alternative
You're sharing a deck or a data room behind a link, and visitors have to accept an NDA or your terms before they see a page. Vibe code the viewer, the links and the gate, and Esign Comply gives your AI tool the acceptance rules and keeps the independent record of who accepted.
Free plan: 10 live signatures a month and a full test mode. No card required.
- 01Upload a deck, create a linkYou
- 02Visitor opens the link, enters an emailYou
- 03Gate page shows the NDA and a Sign buttonYou
- 04Acceptance reported from the visitor's browserEsign Comply
- 05Sealed record of who accepted which versionEsign Comply
- 06Server unlocks the deckYou
What you're building: gated document sharing
Link-based sharing with a gate in front. The gate is a clickwrap or a signed NDA, and it is the part that needs a record.
Share links
One link per investor, customer or deal, each with its own settings.
A deck and document viewer
Pages render in the browser. Nothing to download unless you allow it.
Data rooms
Folders of files behind a single link, with access per visitor.
Email capture
Visitors enter an email address before they get in.
An NDA or terms gate
Visitors sign your NDA, or accept your terms, before the first page appears.
Link controls
Expiry dates, passcodes, download on or off, and a switch to revoke access.
Viewer analytics
Who opened what, which pages they read and for how long.
An acceptance log
Every visitor who accepted, the version they accepted and when.
Who does what in your DocSend alternative
Files, links, the viewer and the analytics are yours. Esign Comply handles the one step that has to hold up later: the acceptance at the gate.
Files and viewer
Upload, storage, the page viewer and the data room.
Your files stay in your storage. Esign Comply holds the NDA or terms that visitors accept.
The NDA or terms
Your text, and which links require it.
Registers the text as an immutable version. Every acceptance pins it by hash.
The gate page
The page between the link and the deck: agreement text, name field or checkbox, button.
The rules prompt for that page, and the browser SDK that reports the acceptance from the visitor's browser.
Knowing who is at the gate
The email field on your gate.
At L2, sends a one-time code to that email and confirms it inside the ceremony.
Unlocking the files
The server check, the viewer session and the signed URLs to your files.
GET /v1 and the signed record.completed webhook to confirm against first.
Who accepted
The acceptance log in your dashboard, per link and per visitor.
The sealed record, a signed receipt (ES256), an RFC 3161 timestamp, an evidence report and a public verification page.
Copies and analytics
Page analytics, view notifications and link emails.
An optional emailed copy of the accepted agreement to the signer.
How to build your DocSend alternative, step by step
Eight steps. The viewer is ordinary product work. The gate is where the rules and the record matter.
- 01
Generate the prompt
In the Esign Comply dashboard, pick NDA signing for a signed NDA, or a custom agreement with a checkbox for a lighter terms gate. Add your regions, signer types and stack, and paste the prompt into your AI tool.
Prompt generatorUse case NDA signing Method Typed name Assurance L2, one-time code by email Signers Business Lighter gate Custom agreement, checkbox, L1
- 02
Register the NDA or terms as a document version
The document you register is the agreement, in Markdown, HTML, plain text or PDF, while the deck stays in your own storage. When you change the NDA, publish a new version: old acceptances keep pointing at the version that visitor saw.
Server · publish the NDAPOST /v1/documents { "name": "Mutual NDA", "type": "nda" } POST /v1/documents/doc_Nd55/versions Idempotency-Key: nda-2026-11-22 { "version_label": "2026-11-22", "content": { "format": "markdown", "text": "# Mutual NDA\n..." } } // 201 Created { "id": "dv_3kT9", "render_hash": "sha256:41ab..." }
- 03
Create one session per visitor
When a visitor enters their email at the gate, your server creates a session for that person on the NDA version. It is one session per signer: ten visitors on one link means ten sessions and ten sealed records, and your app maps each one to the link.
Server · when a visitor reaches the gate// One session per visitor, on the NDA version this link requires. // esc is the server SDK: new EsignComply(process.env.ESIGNCOMPLY_API_KEY) const { data: session, error } = await esc.sessions.create( { profile: "prof_nda_9c2e", // typed name, L2 signer: { external_id: visitor.id, email: visitor.email, class: "business", country: visitor.country, }, documents: [ { document: "doc_Nd55", version: link.ndaVersionId }, ], context: { url: `${origin}/d/${link.token}`, locale: "en-US", purpose: "nda", }, metadata: { link_id: link.id, room_id: link.roomId }, }, { idempotencyKey: `gate-${link.id}-${visitor.id}-${attempt}` }, ); // Send the browser only session.client_token, session.api_url // and session.documents.
- 04
Share the link
The link points at your own viewer. Paste it wherever you like, or email it from your domain with a provider such as Resend.
Server · email a share linkimport { Resend } from "resend"; const resend = new Resend(process.env.RESEND_API_KEY); const url = `https://yourapp.com/d/${link.token}`; await resend.emails.send({ from: "Dana at Acme <dana@yourdomain.com>", to: investor.email, subject: `${company.name}: Series A deck`, html: `<p><a href="${url}">View the deck</a></p>`, });
- 05
Build the gate page with the browser SDK
The gate shows the NDA inline, confirms the visitor's email with a one-time code and takes a typed name, while
@esigncomply/browserreports the acceptance from the visitor's browser. For a terms gate, pass a checkbox instead of the name field.Browser · app/d/[token]/gate.tsximport { EsignComply } from "@esigncomply/browser"; const ceremony = await EsignComply.attach({ clientToken, apiUrl }); // The NDA, rendered from the registered version await ceremony.presentDocument({ versionId, mode: "inline", container: ndaArticle, }); // L2: a one-time code to the email the visitor entered await ceremony.verify.start({ method: "email_otp" }); await ceremony.verify.confirm({ code: codeInput.value }); // Signed NDA: typedName. Terms gate: checkbox. ceremony.observeAssent({ region: gate, typedName: nameInput, submit: signButton, }); // From the click handler of "Sign NDA and view" const result = await ceremony.complete(); // { recordId, receipt, verifyUrl, status }
- 06
Confirm on your server before you serve a page
The deck stays locked until your server has read
GET /v1with the secret key, or handled the signed/records /{id} record.completedwebhook. Only then start the viewer session and hand out signed URLs to your files.Server · confirm, then unlock// No confirmed record, no deck. const { data: record, error } = await esc.records.get(recordId); const confirmed = !error && ["recorded", "timestamped", "anchored"].includes(record.status) && record.signer.external_id === visitor.id && record.documents.every((d) => d.version_id === link.ndaVersionId) && record.livemode === (process.env.VERCEL_ENV === "production"); if (confirmed) { await grantAccess(link.id, visitor.id, record.id, record.receipt); }
- 07
Show who accepted in your dashboard
Next to your view analytics, list every visitor who accepted: email, link, NDA version, time and record ID. With receipts on, Esign Comply emails each visitor a copy of the agreement they accepted and a verification link.
- 08
Keep our receipt and offer the evidence report
Store the signed receipt with each acceptance. When a deal needs the paperwork, download the evidence report for that visitor: it names the NDA version by hash and lists each step of the acceptance.
Server · evidence for one visitor// Use a key with full_access or read_only permission GET /v1/records/rec_Ds27/report // evidence report (PDF) GET /v1/records/rec_Ds27/evidence // evidence package (ZIP) // Anyone checks the package offline npx esigncomply-verify rec_Ds27.zip
A starter prompt to paste into your AI tool
Paste this first. It describes the viewer and the gate. Then paste the generated prompt from the dashboard.
Generate the full promptBuild a DocSend-style document sharing app in this codebase. A user uploads a deck (PDF) or groups files into a data room, then creates share links with expiry, passcode, a download switch and an optional NDA. A visitor opening a link enters their email. If an NDA is required, show a gate page with the NDA text, a one-time code sent to their email, a name field and a "Sign NDA and view" button. Then show the deck in our viewer and record page views. Add a dashboard with views per link and a log of who accepted which NDA version, and when. 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. Register the NDA text as an Esign Comply document version. Deck files stay in our storage. One session per visitor. Serve no file or signed URL until 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 NDA gate exists for the day someone leaks the deck and says they never agreed to anything. On that day a row in your own analytics table is a claim made by the party who wants it to be true. Esign Comply receives the acceptance from the visitor's browser, pins it to the exact NDA version by hash, seals it with keys you do not hold and has an outside authority timestamp it (RFC 3161). You hold the receipt, and the evidence package verifies offline for anyone you give 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 visitor's completed acceptance. Page views are your own analytics and never count.
See pricingQuestions about building your own DocSend
Can I build a DocSend alternative with Cursor or Claude Code?
Yes. Share links, a deck viewer, a data room and page analytics are ordinary product code for Cursor, Claude Code, Lovable, v0, Bolt or Replit. Esign Comply generates one prompt with the rules for the NDA gate and records each acceptance from the visitor's browser.
Generate a promptHow do I require an NDA before someone views a deck?
Put a gate page between the link and the viewer. The visitor enters an email, reads the NDA, confirms a one-time code, types their name and clicks Sign. Your server confirms the record with GET /v1/records/{id} and only then serves the deck.
Does Esign Comply store my deck?
Your deck stays in your own storage. The document you register with Esign Comply is the NDA or the terms that visitors accept, and each record pins that version by hash. Your app links the record to the share link and the files it unlocks.
How do I record who accepted?
Each visitor gets their own session and their own sealed record. With email verification on, Esign Comply sends a one-time code to the address the visitor entered and confirms it inside the ceremony. Your dashboard lists the email, the NDA version, the time and the record ID.
Is an NDA signed at my own gate recognized?
Yes. Electronic 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. Your gate follows ceremony rules drawn from those laws and from leading U.S. online-assent decisions, and Esign Comply keeps an independent, tamper-evident record of each acceptance, signed with keys you do not hold.
U.S. rules we draw onBuild the gate. Leave the record to us.
Free plan: 10 live signatures a month and a full test mode. No card required.
DocSend is a trademark of its owner. Esign Comply is not affiliated with it.