Skip to content

Introducing Esign Comply

Build the signing flow yourself. Let an independent third party record that it happened.

Blog

AI coding tools changed who builds signing flows. A founder can ask Cursor or Claude Code for a signup page with a terms checkbox or an NDA page with a typed-name field. A developer can build that interface without a vendor iframe.

What the generated code does not give you is the part that matters when someone disputes the agreement.

The gap

A home-built flow can have three gaps.

First, the ceremony. U.S. courts look at the screen the user saw: where the notice sat, whether links looked like links, and whether the button label matched the notice. In Berman v. Freedom Financial, the Ninth Circuit affirmed denial of arbitration after finding small gray notice text, links that did not clearly look like links, and no statement that clicking meant agreement.

Second, the evidence. A record in your database is under your control, and anyone with write access can edit it. In a dispute you have to show how you know it is intact.

Third, the evidence source. Your team can explain what your application recorded. A separate service can report what it observed independently.

What we built

Esign Comply is a compliance API for signing flows you build yourself. It does three things.

It gives your AI coding tool the rules. You choose your use cases, signer types, regions, and stack. We generate one prompt that tells the tool what to build, which API calls to make, and which design rules the screen must satisfy: unchecked boxes, notice beside the button, link styling, exact button wording, consumer e-consent steps where they apply, EU confirmation requirements.

It records direct browser ceremonies independently. Our headless SDK attaches to the elements you built and reports events directly to us. We add server time, bind the record to the exact document version, and seal the live record with a separate key. We obtain an external RFC 3161 timestamp asynchronously, with two authorities configured for failover, and publish ledger checkpoints outside our primary systems.

It gives you evidence you can check. Every plan includes evidence reports and packages that verify offline; a record ID alone does not reveal whether a record exists. We send a receipt with access to a copy when a signer email is known, unless an eligible L1 acceptance profile uses customer delivery. An on-request certificate adds a dated, sealed statement. Custodian declarations are a separate human service.

Choose the jurisdiction packs your flow needs. The record shows which rules applied. The recording API keeps working as guidance changes; new blocking conditions arrive as advisories until adopted. You can request a certificate for timestamped live records. It shows the recorded timeline and the verification results.

What the record says

You write the documents and build the screens. We store, hash, and version each document and record the ceremony. The evidence report, titled "Electronic Signature Evidence Report" or "Electronic Acceptance Evidence Report," keeps what we observed apart from what you supplied, so a reader can tell the two apart.

The product records simple electronic signatures and acceptance with independently verifiable evidence. EU, UK, and Swiss profiles have separate rule packs, and the API blocks a short list of special-form documents, such as wills and documents that need a notary. Live EU capture is minimal by default. EU online consumer flows include a durable confirmation and a withdrawal function with durable acknowledgment, both tested before going live.

How it works in practice

const ceremony = await EsignComply.attach({ clientToken });
await ceremony.presentDocument({ versionId, mode: "hyperlink", link });
ceremony.observeAssent({ region, checkbox, submit });
// Call this from your real submit handler after the SDK records trusted user intent.
async function submitCeremony() {
  const { recordId } = await ceremony.complete();
  await confirmOnYourServer(recordId);
}

Your server creates the session with a secret key and confirms the record before granting access. Test keys work on localhost before you touch DNS. A conformance checker opens your page at three screen sizes, runs the ceremony, tries to break it, and reports findings in a form you can paste back into your coding tool.

Pricing

Each self-serve plan covers one organization and one registrable domain, including its subdomains.

  • Free: 10 live signature events a month and a full test mode. No card required.
  • Starter: $200 per year for 2,000 live events, with optional event packs. No certificates are included; pay $20 per issued certificate.
  • Unlimited: $1,200 per year, subject to fair use. Includes 25 certificates per subscription year, then $20 each.
  • Enterprise: from $10,000 per year with unlimited certificates, security documentation, multi-domain and named-affiliate coverage priced per domain, and named support. Single sign-on and other advanced controls are on the roadmap.

A signature event is one sealed live record for one signer completing one ceremony, whether accepting terms at signup or signing an NDA. Test records do not count toward the live quota; separate test limits apply. Quota does not block completion of a session already created.

Built on Vercel and Supabase

The application runs on Vercel and Supabase. We hold sealing keys and write-once evidence copies in a separate AWS account, so rewritten history is detectable. You choose a US or EU data region when you register your domain.

Start

Create an account, generate a prompt, and record a test signature. The Free plan requires no card.

Working with an AI tool? This page is also available as Markdown: /blog/independent-record.md