A production checklist for self-hosted e-signing
Move from a local Docker demo to a resilient deployment with durable storage, mail delivery, backups, and observable document processing.
Separate application containers from durable state
Treat the Signa frontend and backend as replaceable processes. Keep the database, uploaded source files, generated previews, completed PDFs, and audit records on durable services with independent backup policies.
SQLite is useful for a single-node evaluation. PostgreSQL is the safer default once multiple processes, automated backups, or high availability matter. Configure the connection through DATABASE_URL so the deployment shape can change without application code changes.
Make document storage explicit
Local storage is simple and can be correct for one host with a durable volume. S3-compatible storage is usually easier to scale across multiple application instances. In either model, block public listing, use least-privilege credentials, encrypt backups, and test restoration.
The database and blob store form one logical record. Backing up one without the other can produce submissions that exist but no longer have their source or completed documents.
Configure delivery before inviting users
A signing platform can appear healthy while invitations never leave the queue. Configure SMTP, sender identity, public application URL, and any SMS provider before onboarding a team. Test delivery, bounce handling, and links from outside the deployment network.
DATABASE_URL=postgresql://signa:password@db:5432/signa
APP_URL=https://sign.example.com
STORAGE_DRIVER=s3
SMTP_HOST=smtp.example.com
SMTP_PORT=587Operate the document pipeline, not only the HTTP service
Monitor upload failures, preview generation latency, queue depth, email delivery, webhook retries, and completed-PDF generation. A green health endpoint does not prove that a signer can see a document or receive an invitation.
- Restore-tested database and object-storage backups.
- TLS termination and a stable public URL.
- Resource limits for document conversion workers.
- Metrics and alerts for queues and failed jobs.
- A documented upgrade and rollback procedure.
Primary references
Build the workflow in Signa
Continue with the product guides and API reference.