Skip to content
Compare

Esign Comply vs. building it yourself

Build your own interface and keep your own log. Esign Comply adds a separate record keeper and independently verifiable evidence.

Your database is your word. Our record is a second one.

Building it yourself compared with Esign Comply
QuestionBuild it yourselfEsign Comply
Who writes the recordYour serverThe signer's browser reports to us directly
Who can edit itWhoever has write access to your databaseApplication roles cannot edit sealed ledger entries; signed checkpoints and external anchors make rewriting detectable
Time of signingYour server clockOur server records the event time; an external RFC 3161 timestamp attests when the live record hash existed
Document versionWhatever is in your repo todayRegistered, hashed, immutable versions
Presentation evidenceWhatever your application preservedScoped assent-region capture; minimal live capture by default in the EU
Signer checkWhatever your login doesL1 uses your own session. At L2 we confirm an email or SMS one-time code. L3 adds a passkey.
Signer's copyYour delivery processWe email the signer a receipt with access to their copy when the signer email is known, unless your L1 profile uses customer delivery.
Ceremony rulesYour implementationGenerated prompt plus conformance checks
Who explains it in a disputeYour team explains its system and recordsOur evidence report, system description, and separately requested statement or custodian declaration describe what we observed; your team explains customer-supplied facts
CostEngineering time and ongoing maintenanceStarter at $200 per year plus optional event packs and $20 per issued certificate. Unlimited at $1,200 per year, subject to fair use, includes 25 certificates per subscription year, then $20 each.
Why not just log it in Supabase

Your acceptances table works. It is also yours to edit.

In a dispute, the question is who could change the record and how anyone knows it is intact. A table you control cannot answer that on its own.

public.acceptances

Your table

  • Written by your own code, on your own server.
  • Editable by anyone with write access to your database.
  • Holds your account of what the interface presented and what the software received, with no second source.
rec_Z4m8 · receipt

Our record

  • In a direct browser ceremony, the signer's browser reports events straight to us, outside your server.
  • We add our server time, bind the record to the exact document version, seal it with a key held in a separate cloud account, and obtain an external RFC 3161 timestamp for the live record.
  • Keep the signed receipt in your own database. Export the evidence package to verify its integrity and timestamp offline.

Keep your table. Store our receipt in it.

The reasoning

Why you need a third party

You can build every screen yourself. The record is the one part that is worth more when someone else keeps it: signed with keys you do not hold and timestamped by an outside authority.

Why a third-party record
Go further

Build the whole signing app

The same API covers a clickwrap at signup and a full signing product of your own: upload a document, email each signer a link, and collect the signature in your UI.

Build your own

Stop being your own record keeper.

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

Working with an AI tool? This page is also available as Markdown: /compare/build-it-yourself.md