RXed AI News

The contract signing station: get documents signed without the per-envelope bill

Clients sign on their phone the same day — on a box you own, with no per-user fee

A signing page on a box you own: client signs on their phone, you get the PDF back with an audit trail, and the per-user subscription goes to zero.

The problem

A signature should cost nothing. The market leader charges roughly €25/user/month on Standard and €40–65/user/month on Business Pro, with envelope caps on most plans — verify current rates, they move. For a two-person shop that signs 15 quotes a month, that is €600–1,500 a year to put a name on a PDF. And the alternative most small businesses actually use is worse: print, sign, scan, email — a day or two of round-trip on every quote, which is a day or two in which the client can change their mind. The self-hosted answer is mature now: two open-source signing platforms, both actively maintained, both free to run on the same small server that already runs the other blueprints in this library.

The architecture

One container plus a reverse proxy. DocuSeal runs on SQLite out of the box, so there is no separate database to operate at small-business volume. If you already run the vault, the analytics box or the reminder engine from this library, this lands on the same server for €0 extra.

Tool choices — and why

DocuSeal (AGPL-3.0, 18.0k stars, active — v3.1.4 released 13/07/2026) is the default pick. It is the simplest credible deployment in this category: one container, SQLite by default, SMTP configured from the web UI, a genuinely good drag-and-drop template builder, and a mobile signing flow your clients will not need help with. The free self-hosted version covers the whole everyday loop — templates, multi-signer order, audit trail, reminders. A paid Pro tier exists for SSO, white-label branding and embedding into your own software; none of that is needed for this blueprint. One naming trap: DocuSeal's cloud free tier caps at 10 signature requests/month. That cap is the hosted service, not the software — self-hosted is unlimited.

Documenso (AGPL-3.0, 14.0k stars, active — v2.14.0 released 28/06/2026) is the alternative when signature weight matters more than simplicity. It signs PDFs cryptographically with a real certificate (PKCS#12), which gives the file itself tamper-evident, verifiable integrity — closer to the qualified end of the e-signature spectrum. The price of that is a heavier setup: PostgreSQL required, a signing certificate to generate or buy, more configuration before first run. If your contracts are routine quotes and service agreements, DocuSeal is enough. If you regularly sign higher-stakes agreements and want the strongest self-hosted evidence trail, take Documenso and budget a weekend instead of an afternoon.

Caddy (Apache-2.0, 74.2k stars, active) does HTTPS with automatic certificates, same as in the password-vault blueprint. A signing link that throws a browser security warning kills trust before the client reads a single line.

Legal validity, plainly. For routine business documents — quotes, service contracts, NDAs — a standard electronic signature with an audit trail is broadly accepted in the EU (eIDAS) and the US (ESIGN/UETA), and the validity does not depend on which brand collected it. Some documents are different by law: notarised deeds, certain HR and real-estate documents, anything a counterparty's compliance department names a specific vendor for. This is reference information, not legal advice — for the exceptions, one question to your accountant or lawyer settles it.

Monthly cost. Software: €0 for both platforms. Hosting: €0 on the box you already run, or €4–6/month for a small VPS if this is your first automation. Email: your existing mailbox's SMTP at this volume. That is the whole bill.

Setup outline

1. Deploy DocuSeal's official Docker image on your server with a persistent volume for the SQLite data and documents.
2. Put Caddy in front: sign.yourbusiness.example, HTTPS handled automatically.
3. Configure SMTP in the DocuSeal admin UI, and set SPF, DKIM and DMARC on the sending domain before the first real signing request — ten minutes of DNS decides inbox or spam folder.
4. Build your first template from the quote or contract you send most. Drag the fields once; every future send reuses them.
5. Send a test to yourself, then to a colleague — and have them sign it on a phone, because that is where your clients will sign.
6. Set the reminder schedule for unsigned documents (one nudge after 2–3 days is plenty).
7. Route the signed PDFs plus completion certificates into your document archive — if you run the receipt-intake blueprint, an email-in to paperless-ngx does this automatically.
8. Run two weeks in parallel with your current method, then cancel the subscription — not before.

Pitfalls — the real ones

Deliverability is the whole product. A signing link in the spam folder is a deal that stalls silently. SPF/DKIM/DMARC are not optional here, and test with a Gmail and an Outlook recipient before going live.
Keep the completion certificate with the PDF. The audit trail (who signed, when, from where, document hash) is your evidence if a signature is ever disputed. Archive both files together, always.
A contract archive on one disk is a liability. Signed agreements are exactly the data the 3-2-1 backup blueprint exists for. Set that up the same afternoon.
Know the exception documents. Notarised deeds and some HR/property paperwork have their own signature rules by jurisdiction. Self-host the routine 95%, ask a professional about the rest once.
Cloud-tier confusion in tutorials. Guides that mention a "10 documents/month limit" are describing DocuSeal's hosted cloud tier. The self-hosted software has no such cap.
AGPL is fine for you. Using DocuSeal or Documenso internally to sign your own business documents is exactly what the license permits for free. The license only starts to matter if you build their code into a product you sell.

Verified repos

DocuSeal — AGPL-3.0, 18.0k stars, active (v3.1.4, July 2026)
Documenso — AGPL-3.0, 14.0k stars, active (v2.14.0, June 2026)
Caddy — Apache-2.0, 74.2k stars, active (July 2026)