E-signature
Signing that never leaves the system that made the document
The agreement, the signer details and the evidence trail all stay on your infrastructure. No upload to a signing vendor, and no per-envelope charge.
Self-hosted · No per-envelope fees · Evidence in your database
document service-agreement · rev 7
signer legal@northwind.example
intent accepted 2026-07-29 14:02:11Z
address 203.0.113.24
artifact sha256:9f2a…c471 sealed
# Written to your database, not ours.How it will work
Five stages, inside one boundary
The value is not the signature itself — it is that the document, the routing and the evidence never separate.
What is planned
What signing does
Signature is a stage of the document's life here, not an integration bolted to the end of it — which is why the evidence ends up in the same place as the document.
Multiple signature types
Drawn, typed and uploaded signatures, with per-field requirements so initials, dates and full signatures can be demanded separately.
Ordered signing workflows
Sequential, parallel or conditional routing, with reminders and escalation when a signer stalls.
Bulk signing
Send the same agreement to hundreds of counterparties from one job, each personalised from its own record.
Audit trail
Every view, action, address and timestamp recorded against the exact revision — written to your database, not a vendor's.
Sealed artifacts
The executed document is hashed and immutable, so later alteration is detectable without trusting the storage layer.
Self-hosted throughout
Signing happens inside your infrastructure. The agreement, signer details and evidence never transit a third party.
The legal frameworks
What makes an electronic signature hold up
These frameworks do not certify software. They set out what a process must demonstrate: that the signer intended to sign, that the signature is attributable to them, and that the document has not changed since. Wraft records all three and keeps them with the document.
ESIGN Act
US Electronic Signatures in Global and National Commerce Act
UETA
Uniform Electronic Transactions Act
eIDAS
EU Electronic Identification and Trust Services Regulation
Enforceability depends on your process and jurisdiction. Nothing on this page is legal advice, and any vendor claiming their software is by itself compliant with these frameworks is overstating what software can do.
An honest comparison
Against a dedicated signing vendor
Hosted signing products are mature and widely accepted, and for plenty of teams they are the right answer. The differences below are structural rather than a judgement about quality.
Describes the common architecture of hosted e-signature products. Some offer on-premise or private deployment at enterprise tiers — check the specific terms of whatever you are comparing against.
Evidence, not just a signature image
What gets recorded, and where it stays
A signature is only as good as the record behind it. Every item below is written to your own database and retained with the document.
- 01 Intent The signer's explicit action to sign, timestamped.
- 02 Attribution Identity, address and session, bound to the signer.
- 03 Integrity A hash of the exact revision that was signed.
- 04 Custody The full trail retained with the artifact, exportable as your own record.
If you already have a vendor
Hand the signing step to a provider you already run
Some agreements have to go through a named provider — a counterparty insists, an agreement has a year left on it, or the decision was made above you. Wraft routes the final step out to one of these and takes the executed document back. Authoring, routing and storage stay here; only the signature ceremony leaves.
DocuSign
Connected over OAuth. Envelopes are sent from the Wraft document, status is read back as the signer moves, and the executed file returns to the record when the envelope completes.
docusign.comZoho Sign
Not built yet. It is on the list because it keeps coming up with teams already standardised on the Zoho suite. Tell us you need it and we will be straight about where it sits.
zoho.com/signDocumenso
Open source and self-hostable, so the handoff can stay on infrastructure you control rather than leaving for someone else's. Connected with an API token; the document is created and sent from Wraft.
documenso.comWorth being plain about the trade: when a document goes out to an external provider, that provider sees it, and the evidence it holds is retained on their terms, not yours. The guarantees on the rest of this page describe signing that stays inside Wraft. Most teams move the step in-house once they watch the trail land in their own database.
Before you commit