Documenso

What Documenso is

Documenso does the DocuSign job: you upload a document, drop fields on it, invite signers by email, and each signer completes their part in the browser. The output is a signed PDF plus the record of who signed what and when. Under the hood it is a modern TypeScript stack — React Router, Hono, tRPC, Prisma on PostgreSQL, with PDF signing handled by dedicated libraries rather than a black box — and it runs on Node 22 or newer with a Postgres database. Docker images are published officially, and one-click deploys exist for Railway, Render, Koyeb and Elestio alongside Docker Compose, Kubernetes and manual installs.

The README frames the project as trust infrastructure rather than a cheaper seat: signing tools insert a provider into every signature, and the counter-proposal is that you should be able to read the code and host it yourself. Two governance details are worth knowing before you adopt it. The licence is AGPL-3.0, which carries network-copyleft obligations if you offer a modified version as a service — fine for internal use, worth a lawyer's five minutes if you plan to build a product on top. And the project has paused external pull requests except from a small set of invited contributors, with a public post explaining why: it remains open to read, audit, run and fork, but it is not open to arbitrary contribution. Open source and open contribution are separate things, and more projects are making that split explicit.

Where a signature sits in a founder's funnel

Signing is easy to file under admin, but for anything sold rather than self-served it is a conversion step — and usually the one with the least instrumentation on it.

• The deal that stalls in the paperwork In founder-led sales, the gap between yes and signed is where enthusiasm evaporates. Sending the document within the hour of the call, pre-filled, is a bigger win than most pricing-page experiments.
• Order forms and pilots Early enterprise deals rarely close on a checkout page. A simple order form that a buyer can sign moves a pilot forward without inventing a procurement process.
• Everything that is not a customer Contractor agreements, NDAs before a partner conversation, advisor letters. Not growth, but the same tool, and the reason a signing account exists at all in most small companies.
• What it does not fix If deals die before the document, the problem is upstream — how to do sales as a founder is the more useful reading. And if your product is self-serve, adding a signature step is a cost, not a feature.

Before you self-host a signing service

Signing has a property most self-hosted tools do not: the evidence it produces has to survive longer than the server that produced it. That changes the checklist.

A first-party note on audit trails

We build AgentCeres — the AI Growth Officer at agentceres.com — and we arrived at the same conclusion this project is built on, from a different direction. Our agents cannot publish a post, send an email, or spend an advertising budget without a human approving that specific action first, and every approval writes a row: what was proposed, who approved it, when, and what the result was. We did not build that because approvals are pleasant. We built it because the question you need answered weeks later is never what did the system do — it is who agreed to this, and can I prove it.

That is exactly what a signature is: a claim plus the evidence that makes the claim checkable. Which is why the interesting part of an e-signature tool is not the drawing pad, it is the record behind it, and why being able to read the code that produced that record is a real argument rather than a marketing one. The same honesty applies to the operating cost, though. We run a fleet of self-hosted per-customer containers, and memory alone is roughly 95% of that bill — the licence is always the cheapest part of self-hosting. If you are choosing tools around a sales conversation rather than a signature, Papermark covers the document-sharing half of the same workflow.