Self-hosted e-signature and the ESIGN Act

The platform records a signer identity and the consent given for that signer, and the evidence is only as strong as the verification step behind it. Auditors look for the email address or verification method tied to each signer, the time the signer accepted electronic delivery and signing, and any identity check the business required before signing. The platform writes these entries to its database, so the database backup and its access controls become part of the evidence. Whether an email link alone is enough for a given matter, or whether a stronger identity check is needed, is a question to settle with your own counsel before rollout.

Auditors expect the final signed file to be stored unchanged, with a cryptographic hash recorded at completion so anyone can later confirm the file has not been altered. The platform generates the hash and stores the completed PDF in its database or object storage, and the hash should be recorded in the audit trail as well. Confirm with the vendor how the hash is computed, where it is stored, and whether the signed PDF can be re-verified outside the platform, for example with a standard PDF validator. Keep a copy of the hash in a location separate from the platform so it can be checked if the platform is lost.

A usable audit trail records each step in the envelope lifecycle with a timestamp and the source of the event. The usual entries are:

• Document created and sent, with the sender account
• Recipient link opened or document viewed, with IP address and user agent
• Field completed and document signed, with the signer identity
• Document completed, voided or declined, with the reason

The platform's application layer generates these events, and the database stores them. Check that the platform records IP address and time consistently, and that the time source is synchronized, since a timestamp without a trusted clock carries little weight. Confirm the exact fields your matters require with counsel.

Where a platform applies a digital signature to the PDF, the signing certificate is part of the evidence, because it binds the document to the signing identity and shows whether the file changed afterward. Documenso documents options such as a self-signed .p12 certificate generated with OpenSSL or signing through Google Cloud KMS, and auditors will ask which option you chose, who controls the private key, how it is stored, and when it expires. A self-signed certificate proves integrity within your own trust domain but does not establish third-party trust, so ask counsel whether that is sufficient. Record the certificate fingerprint and key custody procedure in your evidence file.

Retention periods come from the law and regulation that governs each document type, not from the software, so the platform must make retention achievable rather than set the period. Some regulated broker-dealer communications, for example, must be preserved for not less than three years under SEC Rule 17a-4(b)(4), which shows how a single rule can set the floor. Confirm the retention schedule per document class with counsel, then test whether the platform can keep completed envelopes, audit trails and exports for that period, and whether deletion is logged. Export logs should show who exported what, when, and to where.

Access logs show who reached the platform and the documents in it, and auditors often test this separately from the signing trail. The reverse proxy records inbound requests, source addresses and TLS details, the application records logins, role changes and document views by internal users, and the database records administrative queries if auditing is enabled. Forward these logs to a SIEM so that they are retained and cannot be edited by administrators of the signing platform. Confirm with your security team which logs your monitoring design already collects, and whether the signing platform has to be in scope for them.

Each evidence item comes from a different layer, so the evidence map should name the owner of each one:

• The platform produces the signed document, its hash, the audit trail events and the export records
• The database stores envelopes, signer records and the audit rows, and its backups define what survives a failure
• The mail relay delivers signing invitations and reminders, and its logs show whether a notice was accepted or bounced
• The reverse proxy logs requests, and the SIEM retains and correlates them

The signer's email delivery log matters because a signer who never received the link is a common dispute. Document this map in your compliance file before the first live signature.

Your own counsel should decide which evidence items a given matter requires, because the answer depends on the document type, the jurisdiction, the consumer or business context and the dispute risk. Engineers can build and export every item listed above, but they should not decide legal sufficiency alone. A useful next step is a short written list per document class that names each evidence item, its retention period, its owner and the test that proves it can be produced. An implementation partner can help prepare that record, though the legal conclusions remain with counsel and auditors.

No. Where the ESIGN Act applies, a signature or record is not denied legal effect solely because it is electronic, and the hosting location does not change that rule. What matters is whether the signer intended to sign, whether the signer consented to electronic records where consumer disclosures are required, and whether the signed record can be retained and reproduced accurately. A self-hosted platform has to produce evidence for each of those points: an audit trail showing who signed, when, from where and against which document version, plus a retained copy of the final record. Ask your counsel to confirm how the ESIGN consent and disclosure steps map to your signing flow, and which document types fall outside the Act and need a different process.

The software license is only one line. Documenso and DocuSeal both publish free self-hosted editions, while their paid tiers add features such as SSO, bulk send, white-labeling and embedded signing. The DocuSeal pricing page, as read in October 2026, lists On-Premises Pro at $240 per user per year, and Documenso lists Enterprise pricing on request for self-hosted setups. Other costs are one-time or recurring: infrastructure, signing certificate setup, integrations with your systems of record, validation of templates and approval workflows, and ongoing support and upgrades. Costs rise with the number of integrations, the number of signing templates, and how much evidence design your compliance team needs. Ask any implementation partner for a quote built from a written scope, and confirm current edition prices with the vendor.

The duration depends on the scope, and no fixed timeline applies to every organization. The main variables are the number of document types, whether identity checks happen before signing, how many systems the signing flow must connect to, how many approvals your counsel and compliance teams need before go-live, and whether signing certificates must be arranged through your own certificate authority or a cloud key service. Simple templates on a single identity provider move faster than multi-department workflows with EHR, CRM or ERP integrations. DeployOpen agrees timelines, deliverables and acceptance criteria in writing before work starts, so ask for a scope-based schedule rather than a generic estimate.

Start with a document inventory: every form, agreement and notice that will be signed, with its owner, version history and the law or policy that governs it. Counsel should review which documents fall under ESIGN, which are excluded, and what consumer consent and disclosure text must appear before signing. You also need signer lists by group, identity verification rules, and retention periods for each record type, since those periods come from your own legal and regulatory obligations. Finally, name the systems the signing flow must read from or write to, and the people who will approve templates and access to signed records. Missing inputs are the most common cause of rework, so settle them before scoping begins.

A capable platform team can deploy simple workflows alone. Documenso supports Docker, Docker Compose, Railway, Kubernetes and manual installation, and DocuSeal runs from its Docker image with SQLite by default or PostgreSQL or MySQL through the DATABASE_URL variable. Most teams can stand up a test instance and a few templates in-house. Partner help becomes valuable when you need a signing certificate chain that your relying parties trust, evidence design that your auditors will accept, integrations with production systems, template validation, and backup, upgrade and monitoring practices. Those last items are where DeployOpen typically works, under a fixed-scope agreement or an ongoing support retainer.

Confirm every figure against the vendor's current page before you budget, because pricing changes. The Documenso pricing page, as read in October 2026, lists Free with 5 documents per month, Individual at $25 per month, Teams at $40 per month for 5 users plus $8 per extra user, and Platform at $250 per month. It also lists the ESIGN Act, UETA, 21 CFR Part 11, SOC 2 and HIPAA among its compliance references without tying them to plans, so ask the vendor what each reference covers in writing. The DocuSeal pricing page lists On-Premises Pro at $240 per user per year and API or embedding usage at $0.20 per completion on its cloud plans. Also confirm the current release each vendor supports: Documenso v2.20.0 and DocuSeal 3.3.2 were the latest versions published in the researched facts.

A usable audit trail records the document identifier and version, each signer's identity method, timestamps for sending, viewing and completion, the IP address and device details where your policy allows, the final hash of the sealed document, and any changes made after sending. Under the ESIGN framework, you also need to retain the record in a form that stays accurate and accessible for its retention period. Keep access logs for the signing platform itself, since they show who viewed signed documents. Confirm with your counsel whether the evidence meets your evidentiary needs, and ask any partner to demonstrate how a signed PDF is verified outside the platform.