Layer 5 · self-hosting reality check
What it actually takes to self-host Documenso
The docs say 1 GB (the vendor's minimum for testing: 1 core, 1 GB RAM, 10 GB storage). In practice you want 2 GB or more (the vendor's production recommendation: 2+ cores, 2+ GB, 20+ GB), with PostgreSQL on the same box. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from DocuSign alternatives, where Documenso is one of the picks.
Wondering whether you need to at all? Is DocuSign free? — what the free tier actually allows, and where the wall is.
| RAM — documented minimum | 1 GB (the vendor's minimum for testing: 1 core, 1 GB RAM, 10 GB storage) |
|---|---|
| RAM — what it really needs | 2 GB or more (the vendor's production recommendation: 2+ cores, 2+ GB, 20+ GB), with PostgreSQL on the same box |
| CPU | 1 core to test, 2+ for production |
| Disk | 20 GB or more to start. By default documents go into PostgreSQL with about 33% base64 overhead; the vendor's example is roughly 60 GB a year at 10,000 documents a month. Switch uploads to S3 for production. |
| Monthly cost | $7–12/mo on a 2–4 GB VPS, plus an SMTP provider, plus a CA-issued signing certificate if recipients must see a verified signature |
| Setup time | 1–2 hours with Docker Compose, including the certificate. Longer if you buy a CA certificate. |
| How you install it | Docker Compose (Documenso plus PostgreSQL 15) with a .env file for secrets, SMTP and URLs. Mount a .p12 signing certificate at /opt/documenso/cert.p12, owned by UID 1001 and read-only. Put a reverse proxy in front for TLS. |
| Ongoing maintenance | Run `docker compose pull` and `up -d`; migrations run on start. Releases come every few weeks (v2.17 to v2.19 between 19 Aug and 29 Sep 2026). Back up the database first, and keep the certificate and encryption keys outside the container. |
| Where it stops scaling | One app container and PostgreSQL cover a small business. For volume, move documents to S3 (the docs rate database storage's scalability as limited) and share one certificate, stored outside the containers, across several instances. |
The thing that catches people out
Documenso does not ship with a signing certificate. Without one, the app starts normally but every document signing fails, so a broken install looks healthy until someone tries to sign. A self-signed .p12 fixes that, but Adobe Acrobat won't show a green checkmark, and recipients see a warning that the signature cannot be verified. Generate the .p12 before the first document and mount it from outside the container. Buy a CA-issued certificate if outside parties will open your PDFs in Acrobat.
When not to self-host Documenso
You send a handful of documents a month: Documenso's hosted free plan covers 5 documents a month with no certificate to manage. Skip it too if you need signatures that check out cleanly in Acrobat for outside parties and nobody will buy, install and renew a CA-issued certificate.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 5 self-hosting guides
- Self-hosting LibreOffice2 GB with a large spreadsheet open
- Self-hosting ONLYOFFICE6 GB for the Document Server with a handful of concurrent editors
- Self-hosting Collabora Online4 GB, and roughly 1 GB per 20 concurrent documents
- Self-hosting CryptPad2 GB for a small instance
- Self-hosting Mattermost4 GB for a team of 50 with PostgreSQL on the same box
- Self-hosting Rocket.Chat6 GB with MongoDB on the same machine
Common questions
- How much RAM does Documenso actually need?
- 2 GB or more (the vendor's production recommendation: 2+ cores, 2+ GB, 20+ GB), with PostgreSQL on the same box in practice. The documented minimum is 1 GB (the vendor's minimum for testing: 1 core, 1 GB RAM, 10 GB storage), which is the figure at which the process starts rather than the figure at which it works under real use. 1 core to test, 2+ for production alongside it.
- What does self-hosting Documenso cost per month?
- $7–12/mo on a 2–4 GB VPS, plus an SMTP provider, plus a CA-issued signing certificate if recipients must see a verified signature This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for run `docker compose pull` and `up -d`; migrations run on start. Releases come every few weeks (v2.17 to v2.19 between 19 Aug and 29 Sep 2026). Back up the database first, and keep the certificate and encryption keys outside the container.
- How long does it take to set up Documenso?
- 1–2 hours with Docker Compose, including the certificate. Longer if you buy a CA certificate., via Docker Compose (Documenso plus PostgreSQL 15) with a .env file for secrets, SMTP and URLs. Mount a .p12 signing certificate at /opt/documenso/cert.p12, owned by UID 1001 and read-only. Put a reverse proxy in front for TLS..
- When should I NOT self-host Documenso?
- You send a handful of documents a month: Documenso's hosted free plan covers 5 documents a month with no certificate to manage. Skip it too if you need signatures that check out cleanly in Acrobat for outside parties and nobody will buy, install and renew a CA-issued certificate.
- What is the most common mistake when self-hosting Documenso?
- Documenso does not ship with a signing certificate. Without one, the app starts normally but every document signing fails, so a broken install looks healthy until someone tries to sign. A self-signed .p12 fixes that, but Adobe Acrobat won't show a green checkmark, and recipients see a warning that the signature cannot be verified. Generate the .p12 before the first document and mount it from outside the container. Buy a CA-issued certificate if outside parties will open your PDFs in Acrobat.