Find your fit
Who it is for
An individual or small office collecting occasional approvals can use the Basic cloud route to build a form and request signatures, while checking its 10 request-email monthly allowance against actual volume.
Teams that need multiple signers, managed templates and a view of pending versus completed requests can evaluate DocuSeal's signing workflow. Administrators who want to run it on their own infrastructure can instead evaluate the on-premises editions and their email setup.
The work it supports
Core capabilities
Prepare a signing template. Upload a PDF or DOCX, then place the fields that recipients must complete. The form builder includes signature-related fields alongside checkbox, image, date, multi-select and cells. Test a real document layout before using it repeatedly.
Invite the right parties. A sender adds recipients to a template and sends the request. DocuSeal supports two or more submitters on one document and provides each a copy after completion. Confirm signer order and field assignment in a sample request.
Watch progress. The submission view distinguishes sent, opened, awaiting and completed states. Use it to find requests needing follow-up, while checking the edition's reminder entitlement before promising automatic nudges.
Keep completion evidence. When all parties have signed, DocuSeal generates a signature certificate or audit log that can be downloaded separately or bundled with the signed PDF. Review that record and your retention process for the documents you handle.
Run it yourself if needed. DocuSeal supplies a Docker image for on-premises operation. The deployment choice brings hosting, storage, mail transport and maintenance into the buyer's scope.
Understand the offer
Pricing and getting started
Cloud Basic is displayed at $0 per app user per month with 10 signature-request emails monthly. Cloud Pro is displayed at $20 per app user per month and lists unlimited signature requests plus reminders and team features. These are current site displays; confirm currency, taxes and final terms at checkout.
On-premises Open Source is listed as free and uses the organization's own SMTP for emails. On-premises Pro is displayed at $20 per app user per month for paid additions such as branding, reminders and teams. Hosting and operations remain the organization's responsibility.
The vendor defines a priced user as a web-app seat for sending/managing documents or accessing the API key, rather than every recipient signer. Pro API and embedding use can carry a separate per-completion charge; scope that use independently from seats.
Look a little closer
Before you choose
Start with a representative agreement and two signers. Check field placement, each recipient's path, the status display, the completed document and its audit log before sending live paperwork at scale.
Compare cloud and on-premises costs as different operating models. The free offerings have different sending setups; Pro includes features beyond the free editions. Confirm the published limits and any optional API charges for the planned volume.
For a self-hosted deployment, test the Docker installation and outgoing SMTP with non-sensitive sample documents. Decide who maintains storage, backups and software updates before storing actual signed agreements.
Do not rely on a general legal-compliance slogan alone. Have counsel or the relevant records owner decide whether the chosen signing method and retained audit evidence meet the documents and jurisdictions involved.
4 distinct sources behind this profile. Research observed Oct 18, 2026. Features and offers can change.
View sources and research →
