Self-Hosted E-Signature: Why We Cut the Per-Envelope Fee to Zero
Most e-signature tools bill like a toll booth: a fee every time a document goes out, for as long as you use them. Here is why we self-host the signing engine instead, and what changed once we stopped paying per document.
September 28, 2026 · BSB Tech Hub
Every major e-signature vendor prices the same way: a fee per envelope, per document, or per seat, forever. Send more contracts as you grow, and the bill grows with you — regardless of how simple the underlying task actually is. For a company that builds software for a living, paying a per-document tax on something as basic as capturing a signature never made sense. So we stopped.
The Per-Envelope Tax Never Stops
Look at the pricing pages and the pattern is identical: a per-seat monthly fee, a cap on free documents, then a per-document charge after that — or, on the enterprise end, a flat cost per envelope sent. None of it scales down. A business sending ten contracts a month and one sending a thousand are both paying the same vendor a fee for every single one, indefinitely. That is a subscription on top of a subscription — the CRM or business system you already pay for, plus a tax on the one feature inside it that just needs a signature.
One Signing Engine, Every Client
We first built this into Candango, our sales CRM — the full story is in how its document builder works. Under the hood, it runs on Documenso, a self-hosted, API-first signing engine with no per-envelope fee. Once that infrastructure existed, reusing it was the obvious move: we recently stood up the same self-hosted signing engine for a bookkeeping services client who needed every business they serve to have its own signing account, instead of buying a separate subscription for each one. One instance, one infrastructure cost, unlimited signers underneath it — the same playbook, applied to a completely different business.
Ownership, Not a Subscription You Outgrow
Self-hosting does not mean cutting corners on what makes a signature legally binding. The same ESIGN Act and UETA requirements apply either way: intent to sign, consent to do business electronically, attribution to the right signer, and a tamper-evident audit trail with timestamps, IP, and device data. A self-hosted engine produces all of that just like a paid vendor does — the difference is who owns the infrastructure it runs on. Own it, and adding the hundredth client — or the thousandth document — costs nothing extra. Rent it, and every one of them shows up as a line item.
What This Means If You're Evaluating a Vendor vs. Building Your Own
If a recurring, per-document fee is baked into a tool you depend on every day, it is worth asking whether that cost is buying you something real or just renting infrastructure you could own outright. That question is not unique to e-signature — it is the same one behind any custom-built system versus an off-the-shelf one billed by the seat or by the transaction. For businesses in Miami running on a stack of rented tools, the math tends to look the same in every category: renting is cheap until you scale, then owning wins.
Share this article
Related: Custom software development · Candango case study · Back to Blog
Custom Software Development
Own the infrastructure your business runs on, instead of renting it by the seat.
Case Study: Candango
A multi-tenant sales CRM with pipelines, proposals, and built-in e-signature.
IT Consulting in Miami
Infrastructure decisions for South Florida teams that plan to scale.
Talk to Our Team
Ask us what self-hosted signing would look like for your business.