Hanzo Sign
Upload a PDF, drop the fields where people need to sign, and send it.
01 / 05 02 / 05 03 / 05 04 / 05 05 / 05
A document, signed
What is in it
The parts of signing that are actually work: placing the fields, chasing the signers, and proving afterwards that it happened.
Where it is right now
Sent, opened, signed, declined — per recipient, as it happens. You know which of five people is holding up a deal without asking any of them.
person 1signed
person 2opened
person 3opened
person 4opened
person 5sent
5 recipientsTwelve languages
German, English, Spanish, French, Italian, Japanese, Korean, Dutch, Polish, Brazilian Portuguese, Albanian and Chinese. The signer reads the page in theirs, not yours.
Fields for a signature, initials, a date, a name, a checkbox or free text, placed where you want them on the page. The completed document carries a certificate recording each signer, the time, and the address they signed from.
The contract you send fifty times a month gets its fields placed once. After that, sending it is choosing a recipient.
Documents belong to a team rather than to whoever uploaded them, so a person leaving does not take the paperwork with them. Roles decide who can send, who can only see.
Your system creates the document, adds the recipients and sends it. A webhook fires when somebody opens, signs or declines, so your side of the workflow moves without anybody watching an inbox.
End-to-end encryption, a signed trail on every document, and data that stays in the region you choose.
The signing page carries your logo and your colours on your own domain, so the person signing sees the company they are doing business with rather than the company we are.
The invitation, the reminder for the one person who has not got to it yet, and the copy of the finished document to everybody who signed.
A passkey, or a password kept as a bcrypt digest. A document can also demand that a recipient authenticate before it will open, so the link alone is not enough to read it.
Each signer gets a link and signs in their browser.
Nobody installs anything and nobody prints anything.
signaturedraw here
What it costs
Run it yourself and pay nothing but your own hosting. Pay us and we run it, on the same code.
Community
Free
Self-host and own your data. Full source code on GitHub.
Get on GitHub- Unlimited documents
- All field types
- Templates
- API access
- Email notifications
- Community support
Starter
$30/mo
For individuals and small teams getting started with e-signing.
Contact Sales- Everything in Community
- Managed cloud hosting
- Custom branding
- Priority email support
- Signing certificates
- 5 team members
Business
$50/mo
For growing teams that need advanced features and integrations.
Contact Sales- Everything in Starter
- Unlimited team members
- Custom domain
- Advanced templates
- Webhooks
- SAML SSO
- Audit logs
- Priority support
Enterprise
Custom
For organizations with advanced security and compliance needs.
Contact Sales- Everything in Business
- Dedicated infrastructure
- Custom SLA
- On-premise deployment
- Compliance certifications
- Dedicated account manager
- 24/7 phone support
Built on Open Source
Hanzo Sign is built on Documenso, an open-source document signing platform, under the AGPL.
The upstream project is named here and in the licence, because naming what you forked is required and is a different act from branding yourself with it. Run our build, or run your own — the whole thing is a TypeScript application over Postgres, and you can read every line that touches a document before you trust it with one.
Send the first one
Upload a PDF and place a signature field. You will know inside five minutes whether this fits.
Documentation
Setup, self-hosting, and the API reference
View Docs →The source
Read it before you trust a contract to it
View on GitHub →Something more specific
Signing inside your own product, a flow with approvals before the send, or running it on your infrastructure. Tell us the shape and we will tell you whether it fits.
Contact Sales →Get started with Sign
Get Sign
E-signature