Skip to content
Build guide · signing links

Build your own signNow alternative

You want the short version of e-signing: upload a document, share a link, get it back signed. Vibe code it with Cursor, Claude Code or Lovable, and Esign Comply gives your AI tool the signing rules and keeps the independent record of each signature.

Free plan: 10 live signatures a month and a full test mode. No card required.

The flow, and who does each part
  1. 01
    Upload a documentYou
  2. 02
    Copy the signing link or email itYou
  3. 03
    Signer opens the link and signsYou
  4. 04
    Ceremony reported from the signer's browserEsign Comply
  5. 05
    Sealed record, receipt and timestampEsign Comply
  6. 06
    Signed PDF back to you and the signerYou

What you're building: signing links

A small tool that does one job well. These are the parts.

01

Quick send

Upload a PDF, type an email address, press Send. Three fields and a button.

02

Signing links

A link you paste into a chat, a text message or an email. Whoever you send it to signs.

03

One link, many signers

A single link for a waiver or a consent form. Each person who opens it signs their own copy.

04

Typed or drawn signatures

A name field or a finger-drawn signature on a phone.

05

A mobile signing page

Readable and signable on a small screen, with no app to install.

06

Signed notifications

You get an email the moment someone signs.

07

Signed PDF download

Every signed copy is listed in your app and downloadable.

You vibe code · Esign Comply handles

Who does what in your signNow alternative

You build the upload, the link and the page. Esign Comply supplies the rules for that page and holds the record behind every link.

Upload

You vibe code

The upload form and where the file is stored.

Esign Comply handles

Registers the document as an immutable version. Every record pins it by hash.

Signing links

You vibe code

The link, its token, and whether one person or many can use it.

Esign Comply handles

One session for each person who opens the link, and one sealed record for each signature.

Sharing

You vibe code

Copy-link, email with a provider such as Resend, or a QR code on a front desk.

Esign Comply handles

The one-time code email at L2, sent and confirmed by Esign Comply.

The signing page

You vibe code

A mobile page with the document, the notice, a name field or signature pad and a button.

Esign Comply handles

The rules prompt for the page, and the browser SDK that reports the ceremony from the signer's browser.

Signed copies

You vibe code

The signed PDF, stamped for example with pdf-lib, and the list of signed documents.

Esign Comply handles

An evidence report for each record, a public verification page and an optional emailed copy to the signer.

The record

You vibe code

Our receipt, stored with each signature in your table.

Esign Comply handles

The sealed record, a signed receipt (ES256), an RFC 3161 timestamp and a hash-chained ledger.

8 steps

How to build your signNow alternative, step by step

Eight steps, the shortest path from an uploaded PDF to a signed one.

  1. 01

    Generate the prompt

    In the Esign Comply dashboard, pick contract signing, your regions, your signer types and your stack. One prompt comes out with the ceremony rules for a signing page, and you paste it into your AI tool.

    Prompt generator
    Use case    Contract signing
    Method      Typed name or drawn signature
    Assurance   L2, one-time code by email
    Signers     Consumer or business
    Stack       Next.js on Vercel, Supabase
  2. 02

    Register the document version

    On upload, your server creates a document and publishes the PDF as a version. Keep the returned dv_ ID on your link row: everyone who uses the link signs that exact version.

    Server · on upload
    POST /v1/documents
    { "name": "Liability Waiver", "type": "contract" }
    
    POST /v1/documents/doc_Wv09/versions
    Idempotency-Key: waiver-2026-11
    
    {
      "version_label": "2026-11",
      "content": { "format": "pdf", "data_base64": "JVBERi0xLjcK..." }
    }
    
    // 201 Created
    { "id": "dv_Tz55", "content_hash": "sha256:c01e..." }
  3. 03

    Create one session per signer

    A signing link is a route in your app, and each person who opens it gets their own session on the same document version: one session per signer, even when fifty people use one link. On a shared link, ask for name and email first, then create the session with them.

    Server · when someone opens the link
    // One session per person who opens the link.
    // esc is the server SDK: new EsignComply(process.env.ESIGNCOMPLY_API_KEY)
    const { data: session, error } = await esc.sessions.create(
      {
        profile: "prof_links_6e4c", // typed name, L2
        signer: {
          external_id: visitor.id, email: visitor.email, name: visitor.name,
          class: "consumer", country: "US",
        },
        documents: [
          { document: link.documentId, version: link.versionId },
        ],
        context: {
          url: `${origin}/s/${link.token}`,
          locale: "en-US",
          purpose: "contract_signature",
        },
        metadata: { link_id: link.id },
      },
      { idempotencyKey: `link-${link.id}-${visitor.id}-${attempt}` },
    );
    // Send the browser only session.client_token, session.api_url
    // and session.documents.
  4. 04

    Share the link

    Show a copy button, or email the link for the sender with a provider such as Resend. The link is yours, so it works anywhere a URL works.

    Server · email the signing link
    import { Resend } from "resend";
    
    const resend = new Resend(process.env.RESEND_API_KEY);
    const url = `https://yourapp.com/s/${link.token}`;
    
    await resend.emails.send({
      from: "Acme Sign <sign@yourdomain.com>",
      to: recipientEmail,
      subject: `Please sign: ${link.title}`,
      html: `<p><a href="${url}">Open and sign</a></p>`,
    });
  5. 05

    Build the signing page with the browser SDK

    One page: the document, an emailed code, a signature, a button. @esigncomply/browser attaches to your elements and reports the ceremony from the signer's browser.

    Browser · app/s/[token]/sign.tsx
    import { EsignComply } from "@esigncomply/browser";
    
    const ceremony = await EsignComply.attach({ clientToken, apiUrl });
    
    await ceremony.presentDocument({
      versionId,
      mode: "scrollbox",
      container: viewer,
    });
    
    // L2: the signer confirms the code Esign Comply emailed them
    await ceremony.verify.start({ method: "email_otp" });
    await ceremony.verify.confirm({ code: codeInput.value });
    
    // A drawn signature: pass the canvas.
    // For a typed name, pass typedName instead.
    ceremony.observeAssent({
      region: assent,
      canvas: signaturePad,
      submit: signButton,
    });
    
    // From the click handler of your Sign button
    const result = await ceremony.complete();
    // { recordId, receipt, verifyUrl, status }
  6. 06

    Confirm on your server before you mark it signed

    Your server reads GET /v1/records/{id} with the secret key, or handles the signed record.completed webhook, and only then adds the signature to your list and notifies the sender.

    Server · confirm the record
    // A record ID from the browser is a claim until your server checks it.
    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.versionId) &&
      record.livemode === (process.env.VERCEL_ENV === "production");
    
    if (confirmed) {
      await saveSignature(link.id, visitor.id, record.id, record.receipt);
    }
  7. 07

    Produce the signed PDF and send copies

    Stamp the name or the drawn signature and the date onto the PDF, for example with pdf-lib. Email the signed copy to the signer and the sender, and list it in your app with its status.

  8. 08

    Keep our receipt and offer the evidence report

    Store the signed receipt next to each signature. Put the verification link on the signed PDF, and add a download button for the evidence report.

    Server · evidence for one signature
    // Use a key with full_access or read_only permission
    GET /v1/records/rec_Sn63/report      // evidence report (PDF)
    GET /v1/records/rec_Sn63/evidence    // evidence package (ZIP)
    
    // Anyone checks the package offline
    npx esigncomply-verify rec_Sn63.zip
For Cursor, Claude Code, Lovable

A starter prompt to paste into your AI tool

Paste this first. It is deliberately small, like the product. Then paste the generated prompt from the dashboard.

Generate the full prompt
starter-prompt.md
Build a simple send-for-signature tool with signing links, in the style of signNow.

A user uploads a PDF and gets a signing link to our own app, to copy or email (use Resend). A link is for one named signer, or reusable: then each visitor first enters name and email. On the signing page the signer reads the document, confirms a one-time code sent to their email, types or draws a signature and clicks Sign. Then stamp signature and date onto the PDF with pdf-lib, email the signed copy to signer and sender, and list it as signed. The signing page must work on a phone.

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 person who opens a link, all on the same document version. Show a document as signed 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.
The record

Why not build the record yourself

A signing link is easy to build and easy to doubt. If the only trace of a signature is a row in the database of the person who wanted it signed, that row carries little weight with the person on the other side. Esign Comply takes the ceremony directly from the signer's browser, seals it with keys you do not hold and has an outside authority timestamp it (RFC 3161). The record is tamper-evident and hash-chained, and the evidence package verifies offline with an open-source tool.

Why the record should not be yours
Annual, per domain

Pricing 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 each person who signs through a link is one event.

See pricing

Questions about building your own signNow

Can I build a signNow alternative with Lovable?

Yes. Upload, a signing link, a mobile signing page and a list of signed documents are standard work for Lovable, Cursor, Claude Code, v0, Bolt or Replit. Esign Comply generates one prompt with the rules for the signing page, and its SDK records each signature from the signer's browser.

Generate a prompt

How does a signing link work?

The link is a route in your own app with your own token. When someone opens it, your server creates an Esign Comply session for that person and the page attaches the browser SDK. The signer signs on your page, and your server confirms the record before it shows the document as signed.

Can many people sign through one link?

Yes. Each person who opens the link gets their own session on the same document version and their own sealed record. Your app asks for a name and an email first, then tracks who has signed.

Who sends the emails?

You send the signing link and the signed copy from your own domain with a provider such as Resend, or you skip email and share the link any way you like. Esign Comply sends the one-time code that verifies the signer's email, and an optional receipt to the signer with a copy and a verification link.

Is a signature made through my own link recognized?

Yes. The U.S. ESIGN Act and state UETA laws recognize electronic signatures: a signature cannot be denied legal effect just because it is electronic. The rules your signing page follows are drawn from those laws and from leading U.S. online-assent decisions, and each signature is kept as an independent, tamper-evident record with a timestamp from an outside authority.

U.S. rules we draw on

Build the signing link. Leave the record to us.

Free plan: 10 live signatures a month and a full test mode. No card required.

signNow is a trademark of its owner. Esign Comply is not affiliated with it.

Working with an AI tool? This page is also available as Markdown: /build/signnow-alternative.md