---
title: "SignuDoc vs DocuSign vs TurboSign: Cost and Adobe Trust | TurboDocx"
description: "SignuDoc vs DocuSign vs TurboSign: what each costs for a team, whether SignuDoc is legally binding, and how to give its PDFs a seal Adobe trusts."
url: "https://www.turbodocx.com/resources/signudoc"
---

# What Is SignuDoc? Kevin Rose's Open Source DocuSign Alternative, Explained

> SignuDoc is a free, MIT-licensed e-signature app that you deploy to your own Vercel account in one click, with no per-seat fees and your documents kept in your own cloud. Whether a given signature holds up depends on the document and the evidence behind it. Out of the box it seals PDFs with a self-signed certificate, so Adobe Acrobat shows the signature as "validity unknown"; an open source fork adds an Adobe-trusted seal through TurboSign.

Updated November 17, 2026. By Alex Martinez, Developer Relations & Automation Lead at TurboDocx. We make TurboSign, which the fork described below connects to. TurboDocx is not affiliated with SignuDoc.

## What is SignuDoc and who made it?

SignuDoc is an open source e-signature app published by Nyllon Software under the MIT license, with Kevin Rose among its contributors ([GitHub contributors](https://github.com/NYLLON-SOFTWARE/SignuDoc/graphs/contributors)). The Deploy to Vercel button copies it into your GitHub account and sets it up on the free plans of Vercel, Neon (Postgres) and Resend (email). Your PDFs sit in a private Vercel Blob store and everything else in your own database, in the region you choose. Nobody else hosts your agreements.

It covers what most teams need to get a document signed:

- Upload a PDF, add up to 10 signers in order, plus people who only get the finished copy
- Signature, initials, date, text, number, checkbox, dropdown and radio fields
- Signers need no account and sign on any phone, tablet or computer
- Access codes or emailed one-time codes for documents that need more than a link
- Templates, signing deadlines and automatic reminders
- Your own name, logo, brand color and domain on every page and email
- A hash-chained audit trail, an audit certificate and a public Verify page
- A PAdES seal on every finished PDF, so any later change shows

The full feature list and setup guide are in the [SignuDoc README on GitHub](https://github.com/NYLLON-SOFTWARE/SignuDoc).

## SignuDoc vs DocuSign vs TurboSign: how much does each cost?

DocuSign charges per user. Its Standard plan is $30 and Business Pro is $45 per user a month on an annual plan, each with 100 envelopes per user a year. For a 15-person team that is $5,400 or $8,100 a year. SignuDoc has no seats, so its cost is your hosting. As SignuDoc's README points out, Vercel keeps its free Hobby plan for personal, non-commercial use, so a company would normally run SignuDoc on Vercel Pro at $20 a month.

|                                       | SignuDoc                                                    | DocuSign eSignature                                                | TurboSign                                                                                                               |
| ------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| Price                                 | Free and open source (MIT)                                  | $30 (Standard) or $45 (Business Pro) per user a month, annual plan | Free for 5 signatures a month; Pro is $20 per user a month with unlimited in-app signatures                             |
| 15-person team, one year              | $0 on free plans, or $240 for Vercel Pro                    | $5,400 on Standard, $8,100 on Business Pro                         | $0 for 5 free signatures a month                                                                                        |
| Documents included                    | No limit of its own; the free plans carry about 250 a month | 100 envelopes per user a year                                      | 5 a month free; on Pro, unlimited in the app and 60 a month through the API (which the fork uses), then from $0.30 each |
| Where documents live                  | Your Vercel Blob store and Neon database, in your region    | DocuSign's cloud                                                   | TurboDocx's cloud. Through the fork, SignuDoc keeps your originals and each PDF goes to TurboSign to be signed          |
| API, integrations, bulk send          | Not yet                                                     | Yes, on higher plans or separate API plans                         | Yes: API and SDKs on every plan, including free, plus bulk send and integrations such as Salesforce                     |
| Seal in Adobe Acrobat, out of the box | Self-signed: shows as validity unknown                      | Trusted                                                            | Trusted: AATL certificate held in an HSM, plus an RFC 3161 timestamp                                                    |

DocuSign still does more: several documents and Word files per envelope, signing at the same time, bulk send, web forms, an API, more than a thousand integrations and signing pages in 44 languages. SignuDoc's own README says so plainly. If you send everyday agreements and want to own the whole thing, SignuDoc is a strong choice. Prices are DocuSign's US list prices, checked November 17, 2026.

TurboSign is the e-signature product we make. You can use it on its own, or keep SignuDoc and let the [open source fork](https://github.com/nicolasiscoding/SignuDoc) send each envelope through TurboSign. The first 5 documents each month are free, and the signed PDF opens as trusted in Adobe.

## Is SignuDoc legally binding?

It can be, depending on the document and on the evidence behind the signature. SignuDoc records what e-signature laws look for: each signer's consent to electronic records, who signed, when and how, optional access codes or emailed one-time codes, and a sealed copy that shows any change. Its README names the US ESIGN Act and UETA, and the EU's eIDAS rules for simple electronic signatures. When a signature is contested, the fight is usually over that evidence: who signed, and whether the file changed. A seal that PDF readers show as "validity unknown" gives the other side an easy question to ask; a seal they trust answers it on sight.

The limits are the usual ones for any e-signature tool. Wills, family-law matters and court orders are kept out of e-signature by many laws, and advanced or qualified signatures under eIDAS need a signing provider, which SignuDoc lets you add. Our guide to [whether electronic signatures are legal](https://www.turbodocx.com/resources/are-electronic-signatures-legal.md) covers the details.

Whether a signature is valid and whether Adobe trusts the seal are two different questions. The next section is about the second one.

## Why does Adobe Acrobat show "validity unknown" on a SignuDoc PDF?

By default, each SignuDoc install creates its own seal key and a self-signed certificate the first time it seals a document. Adobe Acrobat checks signatures against the Adobe Approved Trust List (AATL) and your computer's trusted certificates. A self-signed certificate is on neither, so Acrobat reports "At least one signature has problems" and shows the signature's validity as unknown.

The seal still does its job: it shows whether the file changed after sealing, and SignuDoc's Verify page lets anyone check a copy. What it cannot do is tie that seal to an authority Acrobat already trusts. For an internal NDA that rarely matters. For a client, candidate or auditor who opens the PDF in Acrobat and sees a warning banner, it often does.

## What do you take on when you self-host SignuDoc?

SignuDoc's own documentation is candid about what a self-hosted install leaves to you. Before customer contracts go through it, these are the questions to answer:

- **Your seal rides on one secret.** The seal key is encrypted with a key derived from BETTER_AUTH_SECRET. Change that secret and the install makes a new seal key; earlier PDFs only verify under the old certificate.
- **Free hosting is not for business.** Vercel keeps its free Hobby plan for personal, non-commercial use, as SignuDoc's README notes, so a company needs a paid plan.
- **Backups are off until you set them up.** The daily backup to a second storage bucket is optional. Lose the database or the files without it and the signed records go with them.
- **Long-term proof needs upkeep.** Without a timestamp server the seal carries no trusted time at all. With one, the archive timestamp keeps evidence checkable until that server's certificate expires, and renewing it is not automatic yet.
- **A link is the default identity check.** By default, anyone holding the emailed signing link can sign. Access codes and one-time codes are there, but they are off unless the sender picks them.
- **Stronger signatures are early.** Advanced and qualified signatures through a signing provider have been tested against stand-ins, not yet against the live services.
- **Compliance is yours to prove.** Part 11 mode covers the software's part. Validating the install, writing procedures and certifying your signatures stay with your organization.
- **Updates and fixes are on you.** The project ships changes most days. Keeping your install current, security fixes included, is your job, not a vendor's.

That is the trade for $0 per seat: you become the e-signature vendor, for every contract you will ever need to defend.

## How do you get a SignuDoc signature that Adobe trusts?

There are three ways, and each fits a different team.

### 1. Trust your install's certificate on each computer

Anyone can tell Acrobat to trust your install's certificate. That works inside your own company, where IT can roll it out, but you cannot ask every client and candidate to do it.

### 2. Bring your own certificate

SignuDoc reads a certificate from a PKCS#12 file (`SEAL_P12_BASE64` and `SEAL_P12_PASSWORD`) and can add an RFC 3161 timestamp (`SEAL_TIMESTAMP_URL`) for long-term validation. A certificate from a certificate authority your readers already trust works here. An AATL certificate does not: its private key must stay on FIPS 140-2 Level 2 or higher hardware and cannot be exported to a file.

### 3. Send through TurboSign with the open source fork

Our fork adds two settings, `TURBODOCX_API_KEY` and `TURBODOCX_ORG_ID`. With them set, simple-signature envelopes go out through TurboSign, which seals the signed PDF with an AATL certificate held in an HSM plus an RFC 3161 timestamp, so it opens as trusted in Adobe. The first 5 documents each month are free. After that, the fork sends with SignuDoc's own seal, so sending never stops.

### How do you set up the TurboSign fork?

1. Deploy [the fork on GitHub](https://github.com/nicolasiscoding/SignuDoc) the same way as SignuDoc, or merge it into your existing copy.
2. Create a free TurboDocx account. In TurboDocx, open Settings, then API keys, create a key and copy your Organization ID from the same page. No credit card is needed.
3. In your Vercel project, set `TURBODOCX_API_KEY` and `TURBODOCX_ORG_ID`, then redeploy.
4. Send an envelope. Download the signed PDF from the envelope's page and open it in Acrobat.

### What changes when you turn TurboSign on?

- Those envelopes leave your accounts: the PDF goes to TurboSign to be sealed, signers get TurboSign's signing link, and TurboSign keeps the audit trail. Leave the two settings unset and everything stays in your own accounts, as in the original.
- Envelopes with dropdown or radio fields stay on SignuDoc's own seal.
- When everyone has signed, TurboSign tells your install and the signed PDF lands on the envelope. That needs your install on https and an Administrator API key.
- The fork is new. Try it on a test install first.

## What are the alternatives to SignuDoc?

If you want open source and self-hosting, DocuSeal and Documenso are the established options. Both are licensed under the AGPL-3.0 rather than MIT, and both run on your own servers as well as their own clouds. If you want someone else to run signing for you, our [roundup of DocuSign alternatives](https://www.turbodocx.com/best-docusign-alternatives.md) compares six hosted options on price, free plans and API.

TurboSign is our hosted option: 5 free documents every month with no credit card, an AATL seal that opens as trusted in Adobe, an API with SDKs, and a price match on paid plans. Self-hosting TurboSign is available on Enterprise for an additional fee. If you already run SignuDoc, you do not have to choose: the fork keeps your install and uses TurboSign only for the seal.

## SignuDoc FAQ

### What is SignuDoc?

SignuDoc is a free, open source e-signature app under the MIT license, published by Nyllon Software with Kevin Rose among its contributors. You deploy it to your own Vercel account with a Neon database and Resend for email, then upload PDFs, place fields, send signing links and keep the sealed, signed copy with an audit certificate. Your documents stay in your own accounts.

### Is SignuDoc really free?

The software is free. It runs on the free plans of Vercel, Neon and Resend, which its README says carry about 250 documents a month. The README also notes that Vercel keeps its free Hobby plan for personal, non-commercial use, so a company would normally run it on Vercel Pro at $20 a month, whatever the size of the team. There are no per-seat fees.

### SignuDoc vs DocuSign: which should I use?

SignuDoc costs nothing per seat and keeps documents in your own accounts, so it suits teams that send everyday agreements and want to own the setup. DocuSign costs $30 to $45 per user a month and does far more, from bulk send to over a thousand integrations, and its PDFs open as trusted in Adobe. TurboSign sits between them: 5 documents a month free and an API on every plan, and the open source fork lets SignuDoc send through it so its PDFs open as trusted in Adobe too.

### Is SignuDoc legally binding?

It can be, depending on the document and on the evidence behind the signature. SignuDoc records each signer's consent to electronic records, who signed and when, optional access codes or emailed one-time codes, and a sealed copy that shows any change; its README says those are what the US ESIGN Act and UETA look for. When a signature is contested, the fight is usually over that evidence, and a seal PDF readers show as "validity unknown" is an easy thing to question. Like any e-signature tool, it is not meant for documents the law keeps out of e-signature, such as wills.

### Why does Adobe Acrobat say "At least one signature has problems" on a SignuDoc PDF?

Out of the box, each SignuDoc install seals finished PDFs with its own self-signed certificate. Adobe Acrobat does not know that certificate, so it shows the signature's validity as unknown. The seal still detects changes to the file. It only means Acrobat cannot tie the certificate to an authority it trusts.

### Can I use an AATL certificate with SignuDoc?

Not through its bring-your-own-certificate setting. SignuDoc reads your certificate from a PKCS#12 file in an environment variable, and certificates on the Adobe Approved Trust List (AATL) must keep their private key on FIPS 140-2 Level 2 or higher hardware, so they cannot be exported to a file. To get an AATL seal, the signing has to happen where that hardware is, which is what the TurboSign fork does.

### How do I make SignuDoc signatures open as trusted in Adobe?

Use the open source fork at github.com/nicolasiscoding/SignuDoc and set a TurboDocx API key and Organization ID. Simple-signature envelopes then go out through TurboSign, which seals the signed PDF with an AATL certificate held in an HSM plus an RFC 3161 timestamp, so it opens as trusted in Adobe. The first 5 documents each month are free. After that, the fork falls back to SignuDoc's own seal.

### Is TurboDocx affiliated with SignuDoc or Kevin Rose?

No. TurboDocx has no affiliation with SignuDoc, Nyllon Software or Kevin Rose, and they have not endorsed TurboSign or the fork. SignuDoc is open source under the MIT license, and the fork that adds TurboSign is published under the same license.

## Sources

1. [SignuDoc on GitHub (README, MIT license)](https://github.com/NYLLON-SOFTWARE/SignuDoc)
2. [SignuDoc contributors on GitHub](https://github.com/NYLLON-SOFTWARE/SignuDoc/graphs/contributors)
3. [SignuDoc self-hosting guide: signed PDFs and the seal](https://github.com/NYLLON-SOFTWARE/SignuDoc/blob/main/docs/self-hosting.md#signed-pdfs-and-the-seal)
4. [DocuSign eSignature plans and pricing](https://ecom.docusign.com/plans-and-pricing/esignature)
5. [Vercel fair use guidelines, cited by SignuDoc's README for the Hobby plan's non-commercial rule](https://vercel.com/docs/limits/fair-use-guidelines)
6. [IdenTrust: AATL-enabled certificates are issued on FIPS 140-2 Level 2+ hardware](https://identrust.com/aatl-enabled-digital-certificates)
7. [GlobalSign AATL FAQ: keys kept in a medium that prohibits export](https://support.globalsign.com/aatl-document/aatl-document-signing-faqs)
8. [SignuDoc fork with TurboSign (MIT)](https://github.com/nicolasiscoding/SignuDoc)

## Related

- [The best DocuSign alternatives in 2026](https://www.turbodocx.com/best-docusign-alternatives.md)
- [Electronic signature vs digital signature](https://www.turbodocx.com/resources/electronic-signature-vs-digital-signature.md)
- [Are electronic signatures legal?](https://www.turbodocx.com/resources/are-electronic-signatures-legal.md)
- [DocuSeal vs TurboDocx](https://www.turbodocx.com/docuseal-alternative.md)

Get an Adobe-trusted seal on your SignuDoc PDFs, 5 free documents every month with no credit card: [the fork on GitHub](https://github.com/nicolasiscoding/SignuDoc).

TurboDocx has no affiliation with SignuDoc, Nyllon Software or Kevin Rose, and they have not endorsed TurboSign or our fork. SignuDoc is open source under the MIT license. Our fork that adds TurboSign: https://github.com/nicolasiscoding/SignuDoc
