01
Upload
Upload the document you need signed.
Send documents. Get them signed. Keep the complete record.
Upload your document, place the fields, add your signers and send. Start with 10 envelopes each calendar month.
Illustrative example. Not a real envelope.
The document
Journey of a document
A visual story of a file moving from blank to complete. Nothing is sent.
The file, before fields are placed.
Try it
Place a mark on the page
Draw in the signature field, or place a sample mark. It never leaves this page.
Chain Anchor
Pre-sign video / voice
EnvelopeRecipientCompletePage 1 of 1
Signature
Draw here
Date
Date
Signer Check
The signature field is empty until you draw or place a sample mark.
How it works
Three steps to a complete record
02
Add fields
Place signature, initials, dates and text fields.
03
Send or sign
Add your recipients and send—or complete the document yourself.
API
Electronic signature API access for every plan
Connect document preparation and signing workflows to your own systems. API access is included on Free, Growth, and Custom; contact us for current integration guidance.
Your system
Upload the document you need signed.
Your systemUpload
The packet
The evidence stack
Optional records can sit with the completed file. They are not a statement of legal validity.
A mark on the page. Not a completed envelope.
Illustrative example. Not a real envelope.
Global Assurance
Statutory frameworks for electronic records
Electronic signature statutes establish the legal framework for digital transactions across jurisdictions.
Swipe to compare.
| Jurisdiction | Statute | Year | Scope | Details |
|---|---|---|---|---|
| United States | ESIGN Act | 2000 | A federal statute on electronic records and signatures in interstate and foreign commerce. | Summary |
| United States (uniform state act) | UETA | 1999 | A uniform state act on electronic records and signatures, adopted in most U.S. states. | Summary |
| European Union | eIDAS | 2014 | An EU regulation on electronic identification and trust services for electronic transactions. | Summary |
| United Kingdom | ECA 2000 | 2000 | The primary statute for electronic signatures and communications in the UK. | Summary |
| Canada | PIPEDA | 2000 | Federal law regarding data privacy and electronic documents in Canada. | Summary |
Global signer verification
Choose the evidence appropriate to each signing risk
Signer verification can range from a simple one-time code to a photo ID and liveness check. The appropriate method depends on the document, jurisdiction, participants, and risk—not on a universal requirement.
These verification methods are planned and are not available in the current preview. Identity evidence does not by itself determine legal enforceability.
Email and SMS verification
PlannedOne-time codes can add a possession check before a signer opens or completes a document.
The code is sent to the email address or mobile number assigned to that recipient.
- Email OTP
- SMS OTP
Photo ID and liveness
PlannedAn identity check can compare a government-issued photo ID with a live facial capture.
Supported documents and checks will vary by country and the selected verification provider.
- Passport
- Driver’s licence
- National ID
Enterprise identity
PlannedBusiness signers can be verified through an organisation’s existing identity provider.
Planned connections include common workforce identity services using standard SSO protocols.
- Microsoft Entra ID
- Google Workspace
- Okta
Document access codes
PlannedA sender-defined code can place an additional gate in front of a confidential document.
The code is shared separately and does not replace stronger identity verification when required.
- Sender-defined code
- Recipient-specific access
Self-service signing
PlannedTurn repeat documents into reusable signing links
A WebForm gives each signer a fresh document workflow from one reusable link. It can support public links, embedded experiences, prefilled fields, and signer access without a product account.
This capability is planned and is not available in the current preview.
- 01
Reusable links
Share one link for repeat NDAs, waivers, intake forms, and onboarding documents.
- 02
Embedded signing
Place the signing flow inside a website or customer portal without sending visitors elsewhere.
- 03
Prefilled fields
Pass known details such as name, company, or reference number into a new signing session.
- 04
Signer-friendly access
Let recipients review and sign without creating a DocuMantra account.
Document intelligence
PlannedReview document language before it enters a signing workflow
Document intelligence can organise clauses, summarise selected text, and highlight language for human review. It should support—not replace—legal judgment or professional advice.
This capability is planned and is not available in the current preview.
- 01
Clause extraction
Locate obligations, dates, renewal terms, and termination language for faster review.
- 02
Risk review
Flag selected patterns such as broad indemnities or uncapped liability for a person to assess.
- 03
Merge and conditional fields
Prepare documents from approved data and show fields according to recipient responses.
- 04
Collaborative redlining
Collect proposed edits before the final document is locked for signature.
Workflow automation
PlannedRoute every document through the right people and next steps
A structured signing workflow can control recipient order, request supporting files, send reminders, and direct a signer after completion. Each rule remains visible to the sender before dispatch.
This capability is planned and is not available in the current preview.
- 01
Sequential or parallel routing
Send in a fixed order or invite all recipients at the same time.
- 02
Signer attachments
Request supporting files such as proof of insurance or business registration.
- 03
Reminders and expiry
Set follow-up intervals and a clear date after which the request closes.
- 04
Completion redirects
Guide signers to a thank-you page, scheduling page, or customer portal.
Connected workflows
PlannedConnect signing with the systems your team already uses
Planned integrations and developer interfaces are intended to move document data between business systems. Connection names describe the roadmap and do not imply current endorsement or availability.
This capability is planned and is not available in the current preview.
- 01
Sales and CRM
Salesforce and HubSpot workflows for preparing and tracking agreements.
- 02
Productivity
Google Workspace, Microsoft 365, Slack, and Dropbox connections.
- 03
Automation
Zapier triggers for common no-code document workflows.
- 04
Developer interfaces
A REST API and webhooks for envelope creation, status events, and embedded signing. Documentation is not published yet.
Trust
What we will say in public
Only controls that exist, and statements we can stand behind. No badges until they are verified.
Published
Account sign-in
A workspace can sign in with an email address and password.
Security overviewCompare
What we publish, and what to check elsewhere
Swipe to compare.
| Compare | DocuMantra | DocuSign | PandaDoc |
|---|---|---|---|
| Published starting price | $0 · 10 envelopes / calendar month | See their pricing | See their pricing |
| API | Included on every plan | See their plans | See their plans |
| Audit trail | Included | See their product | See their product |
| Optional evidence extras | Signer Check, Pre-sign video / voice, Chain Anchor | See their product | See their product |
Pricing
Free, Growth, and Custom
Free includes 10 envelopes each calendar month at $0. Growth is $5 per month per workspace.
Envelopes this calendar month
$0/ month
Free · 10 envelopes / calendar month
A monthly number of envelopes is included. Unused envelopes do not roll over on the published plans.
Free
$0/ month
- 10 envelopes / calendar month
- API included
Growth
$5/ month per workspace
- 25 envelopes included
- API included
- Pay only for what you use
Custom
Let's talk
- Contracted volume
- API included
- White-label
- Priority support
Send
Start with a PDF or DOCX file
Upload the document you need signed.
SendComplete