Back to articles
AI & Cloud

Deploy OpenSign on VPS: Build a Secure, Cost-Optimized Internal Document Signing Platform to Replace DocuSign

A detailed guide to deploying OpenSign on a VPS for secure, self-hosted internal document signing, reducing costs and enhancing control compared to DocuSign.

DPTCloud Engineering4 min read
Deploy OpenSign on VPS: Build a Secure, Cost-Optimized Internal Document Signing Platform to Replace DocuSign

Image credit: VISHNU_KV · Pixabay Content License

In an era where businesses increasingly seek secure, cost-effective alternatives to third-party signing services like DocuSign, deploying OpenSign on a VPS (Virtual Private Server) offers a powerful solution. OpenSign is an open-source internal document signing platform that enables electronic signing of PDFs, Word documents, and other formats without relying on external SaaS providers. By self-hosting, organizations gain full control over their signing workflows, enhance data privacy, and significantly reduce operational costs. This guide provides a step-by-step deployment of OpenSign on a VPS to build a secure, efficient, and cost-optimized internal signing platform.

Introduction to OpenSign and Benefits of Self-Hosting on VPS

OpenSign is an open-source electronic document signing platform that allows users to sign documents securely within their own infrastructure. Unlike DocuSign or Adobe Sign, which are hosted SaaS solutions, OpenSign enables full self-hosting, providing organizations with:

  • Internal Security: Document data and signatures remain within your network, minimizing exposure to external threats.
  • Cost Reduction: Eliminate per-signature or per-user fees common with commercial services.
  • Full Customization: Adapt signing workflows, user interfaces, and integrations with internal systems (ERP, CRM, etc.) as needed.
  • Infrastructure Control: Manage servers, backups, updates, and maintenance independently.

Deploying OpenSign on a VPS provides scalability, stable performance, and remote access, making it ideal for small and medium-sized businesses with internal signing needs.

Prerequisites and Environment Setup

To deploy OpenSign on a VPS, ensure you have the following:

  • A High-RAM Cloud VPS (minimum 4GB RAM, 2 vCPU, 50GB SSD).
  • Operating System: Ubuntu 20.04/22.04 or Debian 11/12.
  • Node.js (v16+), npm, and Docker (recommended for containerized deployment).
  • SSL/TLS certificate (use Let's Encrypt for free certificates).
  • Basic software: nginx, PM2 (for application process management).

Ensure the VPS has a stable internet connection and SSH access to run installation commands.

Deploying OpenSign on VPS: Step-by-Step Guide

The following steps outline a Docker-based deployment of OpenSign, which is the simplest and most common method.

Step 1: Install Docker and Docker Compose

sudo apt update
sudo apt install -y docker.io docker-compose
sudo systemctl enable docker
sudo systemctl start docker
sudo usermod -aG docker $USER

Step 2: Create Directory and Download Configuration

mkdir -p ~/opensign && cd ~/opensign
wget https://raw.githubusercontent.com/opensign/opensign/main/docker-compose.yml

Step 3: Configure Environment Variables

Create a `.env` file in the `~/opensign` directory:

NODE_ENV=production
OPENSIGN_API_PORT=3000
OPENSIGN_FRONTEND_PORT=3001
OPENSIGN_DB_HOST=localhost
OPENSIGN_DB_PORT=5432
OPENSIGN_DB_NAME=opensign
OPENSIGN_DB_USER=opensign
OPENSIGN_DB_PASSWORD=your_secure_password
OPENSIGN_SSL_ENABLED=true
OPENSIGN_SSL_CERT_PATH=/etc/letsencrypt/live/yourdomain.com/fullchain.pem
OPENSIGN_SSL_KEY_PATH=/etc/letsencrypt/live/yourdomain.com/privkey.pem

Step 4: Launch OpenSign

docker-compose up -d

Performance Optimization and Maintenance

After deployment, consider these optimizations:

  • Set up nginx as a reverse proxy to manage traffic and enhance security.
  • Integrate Let's Encrypt for automatic SSL certificate issuance and renewal.
  • Use PM2 to manage the OpenSign process and enable automatic restarts on failure.
  • Perform regular backups of the PostgreSQL database and signature storage directory.

Testing and Verification

Once the service is running, access it via:

https://yourdomain.com

Log in with the admin credentials and verify core features: document creation, signing requests, signature collection, and signing history.

Security Measures

  • Always use HTTPS (via Let's Encrypt or internal certificates).
  • Configure a firewall (UFW) to allow only necessary ports (80, 443, 3000, 3001).
  • Keep the server and OpenSign software updated.
  • Never expose signed documents publicly on the server.

Replacing DocuSign: Comparison and Benefits

Feature DocuSign Self-Hosted OpenSign
Cost Per-signature or per-user pricing Fixed cost (VPS + maintenance)
Security Dependent on third-party provider Full internal control
Customization Limited Highly flexible
Reliability Dependent on service uptime Self-managed and self-controlled

Conclusion

Deploying OpenSign on a VPS provides a secure, cost-effective, and customizable alternative to DocuSign for internal document signing. With its open-source nature, organizations gain full control over their signing processes, ensure data privacy, and adapt to evolving business needs. This guide offers a complete path from setup to optimization and security, enabling successful deployment.

References

DPTCloud Tier III Infrastructure

High-RAM Cloud VPS Plans Optimized for AI, Databases & Cache

Enterprise RAID 10 NVMe SSDs, CMC & FPT District 9 uplinks with Anycast Anti-DDoS and 99.99% SLA.

View 22 VPS Plans
ECO · vn-02Recommended

VPS-4E

297.000 ₫ / mo

10% VAT included

  • CPU: 4 vCPU
  • RAM: 8 GB
  • SSD: 50 GB NVMe
ECO · vn-02

VPS-5E

614.900 ₫ / mo

10% VAT included

  • CPU: 8 vCPU
  • RAM: 16 GB
  • SSD: 100 GB NVMe
ADVANCED · vn-03Recommended

VPS-4T

548.900 ₫ / mo

10% VAT included

  • CPU: 4 vCPU
  • RAM: 8 GB
  • SSD: 50 GB NVMe

Related Articles

View all
ZaloZalo SupportDiscord0384 753 478