$8,100/year: Kevin Rose replaced Docusign with open-source SignuDoc
Kevin Rose said Docusign wanted $8,100/year for 15 people to sign PDFs. He posted SignuDoc instead, MIT code you deploy yourself.
Kill posts8 min read
Tim Neunzig
$8,100/year is what Kevin Rose said Docusign wanted from a 15-person team that needed to sign PDFs.
So he did the obvious thing. He built SignuDoc, posted it as open source, and cut the seat meter out of the workflow.
This is the kind of subscription that survives because nobody wants to touch PDFs, audit trails, email links, and signature fields. That fear has a price. In this case, $24,300 over 3 years.
What happened
On 16 Nov 2026, Kevin Rose posted that Docusign wanted $8,100 a year for a 15-person team to sign PDFs. His replacement was SignuDoc, an MIT-licensed e-signature app that runs in the user’s own Vercel account.
The claim was narrow. Not a full Docusign clone. Not a global agreement platform. A signing workflow. Upload PDFs. Send them. Collect signatures. Keep an audit trail. Seal the result.
The post said the replacement had $0 per seat, white-label branding, full audit trails, tamper-evident seals, and documents staying in the user’s own cloud. The kill sheet says the post reached about 2.83M views within about a day.
The pricing line is the whole story. The Business Pro calculation in the kill sheet is $45 per user per month × 15 users × 12 months = $8,100. Over 36 months, the same setup is $45 per user per month × 15 users × 36 months = $24,300.
The Docusign pricing source listed here is Docusign’s eSignature plan page. The kill sheet says the $45 USD Business Pro price comes from the SignuDoc README, not verified on Docusign’s own site. The same sheet lists Docusign’s German annual Business Pro price as €38 per user per month, billed annually at €456 per user per year.
That detail matters. You are not looking at a mystical enterprise quote. You are looking at seat math. One sender becomes 15 seats. The workflow stays boring. The invoice does not.
SignuDoc’s repo is public. The kill sheet lists it at 1,153 stars, last commit 2026-11-17, not archived, and MIT licensed. Its stack is also boring in the right way: Next.js 16, Vercel, Neon Postgres, Resend email, Vercel Blob storage, and PAdES-sealed PDFs.
That is the point. A small team did not need a cathedral. It needed a locked room with a pen, a PDF, a log, and a door.
What it actually did for you
Docusign eSignature lets businesses send documents for legally binding electronic signature, collect signatures and form data, and store completed agreements with an audit trail. Higher tiers add bulk sending, PowerForms, and payment collection.
What people use every day is smaller.
You send PDFs for e-signature. That is the job Rose described. A 15-person team needs to sign PDFs. You do not need to pretend every user is running a revenue operations department.
You need an audit trail. Every completed signature flow needs a record of what happened. SignuDoc is described as having full audit trails and an audit certificate. That is not decorative. That is the receipt.
You need tamper-evident signed files. SignuDoc seals signed PDFs with PAdES and tamper-evident seals. The output can be checked after signing. That is the part your process actually depends on.
You may need white-label branding. Rose cited white-label branding as part of the replacement. That removes vendor branding from the signing flow. Your client sees your process, not your subscription vendor.
You may need own-cloud document storage. Rose said documents never leave the user’s own cloud. The repo uses Vercel Blob storage under the user’s deployment. You still have to operate it. But the documents are not sitting in a third-party SaaS tenant by default.
Then comes the padding.
Business Pro adds bulk send, PowerForms, and payments. The kill sheet also lists scheduled send, real-time data validation, calculated fields, SMS delivery, ID verification add-ons, real-time comments, CRM and ERP integrations, delegated signing, in-person signing, mobile signing, and reminders as paid features outside the narrow daily workflow.
Some teams need those. Most teams say they might. That is how you end up renting a platform to move a signature onto a PDF.
The invoice is not based on your real workflow. It is based on the vendor’s menu.
The math
| Option | Price per user per month | Team size | Months | Total |
|---|---|---|---|---|
| Docusign Business Pro | $45 | 15 | 36 | $24,300 |
| Owned SignuDoc build, pro scope | $0 seat rent | 15 | one build | $2,500 to $8,000 |
You keep up to $16,300 over 3 years after the high end $8,000 build, and you keep MIT-licensed code running in your own account. At the high end of the build range, payback is 12 months.
That is before add-ons. That is before sales-assisted plans. That is before another department asks for 5 more seats and turns your PDF chore into a budget line.
The build range here is $2,500 to $8,000. The kill sheet marks it as pro scope because this is not a toy form. It needs multi-user signing, PDF upload and storage, email delivery, audit trails, tamper-evident sealing, and hosted deployment.
It is still not enterprise scope. The public replacement does not claim broad CRM or ERP integrations. It does not claim complex migration tooling. It does not claim the full Docusign advanced-plan feature set. Good. That is how the price stays attached to the job.
What you would build instead
- Signing web app: deploy SignuDoc for the browser UI that sends documents and lets recipients complete signatures.
- Stack: use SignuDoc with Next.js 16, Vercel, Neon Postgres, Resend email, Vercel Blob storage, and PAdES-sealed PDFs.
- Database: use Neon Postgres to store users, document metadata, signing state, and audit trail records.
- File storage: use Vercel Blob storage for uploaded and completed PDFs inside your own deployment.
- Email delivery: use Resend for signing links and workflow emails.
- PDF sealing and audit certificate: seal signed PDFs with PAdES and produce an audit certificate.
- Hosting: one-click deploy to your own Vercel account, as described by Rose’s post and the SignuDoc repo.
- Data migration: start with new signing workflows. No public migration details were provided. Historical Docusign agreements and templates are not covered by the public story.
- Open-source building blocks: SignuDoc, MIT license, 1,153 stars, last commit 2026-11-17. Documenso, AGPL-3.0 license, 15,792 stars, last commit 2026-11-17. DocuSeal, AGPL-3.0 license, 19,063 stars, last commit 2026-11-16. OpenSign, AGPL-3.0 license, 7,273 stars, last commit 2026-11-13.
You lose Docusign’s managed SaaS service. You lose its broad integration list, including Google Drive, OneDrive, Dropbox, Box, Google Workspace, Microsoft 365, Slack, Microsoft Teams, Zoom, Stripe, Salesforce, Microsoft Dynamics, and NetSuite. You lose Business Pro features outside the narrow replacement scope, including bulk send, PowerForms, and payment collection. You lose advanced add-ons such as SMS delivery, ID verification, real-time validation, calculated fields, and real-time comments. You lose Docusign vendor support and sales-assisted enterprise plans.
That is the trade. You stop paying seat rent. You start owning the surface area. If you cannot operate a small deployed app, keep renting. If your team already runs production software, this is not exotic.
The legal part is not magic either. The product summary says Docusign eSignature is used for legally binding electronic signature. SignuDoc is described as using audit trails, audit certificates, tamper-evident seals, and PAdES-sealed PDFs. If your jurisdiction, customer, or compliance regime needs a specific signature standard, you verify that before replacing anything. Unknown in the public story means unknown. Do not invent certainty because the invoice annoys you.
Who should do this
Do this if you are a 10 to 25 person team mostly sending ordinary PDFs for signature, with a few internal senders and a simple approval process. At 15 seats, the kill sheet puts the Docusign Business Pro rent at $675 per month and $24,300 over 3 years. That gives you room to build once and stop counting seats.
Do this if you are an agency, consultancy, recruiter, property operator, or procurement team sending repeat documents that do not need Salesforce, Microsoft Dynamics, NetSuite, ID verification, SMS delivery, or payment collection inside the signing flow. You need templates, links, logs, files, and sealed output. Build that.
Do this if your team cares where documents sit. Rose’s replacement puts documents in your own cloud deployment. That does not remove operational responsibility. It moves control back to you.
Keep renting if Docusign is wired into your CRM, ERP, storage, chat, identity, and finance stack. Keep renting if you use bulk send, PowerForms, payment collection, advanced validation, calculated fields, in-person signing, delegated signing, SMS delivery, ID verification, or enterprise support. Keep renting if nobody owns production software in your company. The worst replacement is a neglected app that handles legal documents.
Also keep renting if historical template migration is the real project. The public story does not cover historical Docusign agreements and templates. It covers a new signing workflow. Different job. Different price.
The clean version is simple. If your Docusign usage is mostly signing PDFs, the platform is bigger than the job. If your Docusign usage is a full agreement machine, do not pretend a narrow app replaces it.
The SaaSKiller Take If you use Docusign mainly to sign PDFs, you are paying Business Pro rent for a narrow workflow. At 15 seats, that is $24,300 over three years before add-ons or sales-assisted plans. Build or deploy the signing flow you actually use, and accept that you will not get Docusign’s integrations or vendor support.
Sources
- https://api.fxtwitter.com/kevinrose/status/2122394902168473975
- https://x.com/kevinrose/status/2122394902168473975
- https://replacemrr.com/s/kevin-rose-replaced-docusign
- https://github.com/NYLLON-SOFTWARE/SignuDoc
- https://ecom.docusign.com/plans-and-pricing/esignature
AI-generated