Signing service, operated by DENDAT

Send a document.
Get it back signed and provable.

DENSIGN reads an uploaded PDF, places the signature, date and text fields it finds, and routes it to each signer through a link that works once. Every action is written to an audit log, and the completed file is hashed so anyone holding it can check it was not altered.

Free tier: 3 documents per month, no card required
Verification is public and needs no account
Document lifecycle
Representative
> upload type=pdf fields=detected > route signers=ordered link=single use > sign ip=logged time=logged > seal hash=sha256 cert=issued > verify lookup=hash only
Lookup is by content hash, so document IDs cannot be enumerated and no signer address is ever returned.
PDF in, fields outSignature, date and text fields placed on upload
Ordered routingMultiple signers, one at a time, each by their own link
SHA-256 sealCertificate issued on every completed document
REST APISend, track and download from your own code

Holding a signed document? Check it here.

Paste the content hash printed on its certificate page. Lookup is by hash only, so no account is needed and no signer detail is ever returned.

01 / CAPABILITIES

What the platform actually does

Each of these is a shipped surface, not a roadmap item. If a capability is listed here you can exercise it on the free tier unless the plan table says otherwise.

Field detection on upload

The uploaded PDF is scanned for signature lines, date fields and labelled text inputs, and those positions are written into the document before you open the editor. Anything it gets wrong you move by hand.

Ordered multi-signer routing

A document can carry several signers in a defined order. Each one receives a personal link, and the next signer is only notified once the previous signature is recorded.

Access codes on the signing link

A signing link can be held behind a code the sender shares out of band, so possession of the link alone is not enough to open the document.

Audit trail and certificate

Every open, sign and decline is recorded with a timestamp and source address. On completion the signed file is hashed and a certificate page is generated listing each signer and when they signed.

Reusable templates

Any prepared document can be saved as a template with its fields and signer roles intact, then reissued to a new recipient without redoing the layout.

REST API and webhooks

Send a document, read its field map, poll its status and download the signed file over /api/v1. Webhooks push completion events to your endpoint. Reference is at /docs.

02 / PROCESS

Upload, route, seal

Three steps, and the third one happens without you. The output is a signed PDF plus a certificate that stands on its own if the document is ever questioned.

STEP 01

Upload and prepare

Drop in a PDF. Detected fields are placed for you. Assign each field to a signer role, adjust anything that landed wrong, and save it as a template if you will send it again.

STEP 02

Send and track

Each signer gets their own link, optionally behind an access code. The dashboard shows who has opened, who has signed and who has not, and reminders can be sent to the ones still outstanding.

STEP 03

Seal and verify

When the last signature lands, the file is hashed and a certificate is issued. Anyone holding the document can paste that hash into the public verifier and confirm it matches, without an account.

03 / AUDIT

What a signature carries with it

A signature is only worth what you can show about it later. Here is exactly what is recorded and what the public verifier will and will not reveal.

Recorded per document
No disclosure on lookup
> event open=time, address sign=time, address decline=time, reason > seal algorithm=sha256 scope=final rendered file > verify input=content hash returns=title, signers, completion time > verify emails=never returned enumeration=not possible
The verifier accepts a hash and nothing else. A wrong hash returns not found rather than a near match, so the endpoint cannot be walked to discover documents.
04 / PLANS

Start free, pay when volume needs it

Billing is per organization. The free tier needs no card, and the audit trail is on every tier including free.

Free
$0 /mo
  • 3 documents per month
  • Single signer
  • Audit trail
Create an account
Pro
$15 /mo
  • Unlimited documents
  • Multiple signers
  • Reusable templates
  • Reminders and bulk send
  • Signing certificate
Choose Pro
Business
$49 /mo
  • Everything in Pro
  • Full REST API at /api/v1
  • Webhooks
  • Priority support
  • Volume pricing
Choose Business
05 / QUESTIONS

Answered plainly

What makes a signature here defensible?

Three things are recorded and can be produced later: the timestamp and source address of every open and signature, the identity the signer authenticated against, and a SHA-256 hash of the final rendered file. The certificate page collects all of it, and the hash lets a third party confirm the copy they hold is the copy that was signed.

Do I need a card to start?

No. Registration puts you on the free tier, which allows three documents a month with a single signer and the full audit trail. Billing details are only collected if you move to a paid plan.

What does field detection actually place?

Signature lines, date fields and labelled text inputs it can locate in the uploaded PDF. It is a starting layout, not a guarantee: the editor lets you move, delete or add fields before anything is sent.

Can a signing link be forwarded?

The link is issued to one signer and is consumed once that signer completes. Put an access code on the document and the link alone will not open it, because the code is shared through a separate channel you control.

Can I drive this from my own application?

Yes, on the Business plan. The REST API at /api/v1 covers send, field map, status, audit and download, and webhooks push completion events to an endpoint you register. The reference is public at /docs.

Does this connect to the rest of DENDAT?

Yes. Sign-in can be brokered by DENDAT CRM, and documents created in the CRM signing module use the same field detection engine, so a document prepared in either place behaves the same way.

Free tier needs no card

Put a document through it

Create an account, upload one PDF, and see what comes back: a signed file, an audit log and a hash you can hand to anyone. If you only need to check a document someone sent you, the verifier is open and needs no account.