DEV Community: atakanozt

5 Awesome Ways to Deploy DocuSeal in 2026

atakanozt — Tue, 20 Jan 2026 20:04:20 +0000

Looking for the best way to deploy DocuSeal, the open-source document signing platform? Whether you need a quick setup for production, want full control over your infrastructure, or just need to test locally: there's an option for you.

DocuSeal is a powerful alternative to expensive SaaS solutions like DocuSign and HelloSign. The best part? You have multiple deployment options depending on your needs, budget, and technical expertise.

In this guide, I'll walk you through 5 different ways to deploy DocuSeal, from the simplest one-click deployment to enterprise-grade Kubernetes setups. Want the quick summary? Skip to the comparison table at the end.

Let's dive into each option!

1. Sliplane — The Easy Way

If you want the simplest and most cost-effective way to self-host DocuSeal in production, Sliplane is your answer. Deploy DocuSeal in under 30 seconds with just a few clicks. No server management, no Docker knowledge required.

Here's how fast it is:

Sliplane is a Platform-as-a-Service (PaaS) built on top of Hetzner's infrastructure, giving you the best of both worlds: ease of use and affordable pricing.

How it works:

Sign up at sliplane.io (free GitHub login)
Create a server (or use the free 48-hour trial server)
Click "Deploy Service" → Select the DocuSeal preset
Done! Your DocuSeal instance is live with automatic HTTPS

Category	Rating
Complexity	Very Easy: No technical knowledge required
Price	€9/month flat, no per-signature fees
Customizability	Medium: Environment variables, volumes, domains

Pros:

✅ One-click deployment: No Docker or server knowledge needed
✅ Fixed pricing: €9/month flat, no surprise bills
✅ Automatic HTTPS: SSL certificates handled for you
✅ Easy updates: One-click redeploy to update DocuSeal

Cons:

❌ No perpetual free tier: 48-hour free trial only

Best for: Developers, startups, and small businesses who want DocuSeal running in production without the DevOps overhead.

2. Self-Hosted on a VPS — The DIY Way

For developers who love full control and want the absolute lowest cost, self-hosting DocuSeal on a Virtual Private Server (VPS) is the way to go. Providers like Hetzner, DigitalOcean, or Linode offer affordable servers where you can run DocuSeal with Docker.

How it works:

Rent a VPS (e.g., Hetzner CX23 for ~€3/month)
Install Docker and Docker Compose
Set up a reverse proxy (Caddy or Nginx) for HTTPS
Deploy DocuSeal using Docker Compose
Configure DNS and SSL certificates

We have a complete step-by-step guide with screenshots: Self-hosting DocuSeal on a Hetzner Ubuntu Server

Category	Rating
Complexity	Intermediate: Docker, Linux, networking knowledge
Price	€3-10/month (cheapest option)
Customizability	High: Full SSH access, any configuration

Pros:

✅ Cheapest option: As low as €3-5/month on Hetzner
✅ Full control: SSH access, custom configurations, any OS
✅ No vendor lock-in: Move to any provider anytime
✅ Learn valuable skills: Great for understanding DevOps

Cons:

❌ Manual setup required: Docker, reverse proxy, SSL, firewall
❌ You handle everything: Updates, backups, security patches
❌ Time investment: Initial setup takes 30-60 minutes
❌ Debugging is on you: No support if something breaks

Best for: Developers with Linux/Docker experience who want maximum cost savings and enjoy managing their own infrastructure.

3. Local Development — The Testing Way

Need to test DocuSeal or develop integrations? Running it locally on your laptop is the fastest way to get started. No server needed, no costs involved.

How it works:

# Using Docker (one command!)
docker run -d -p 3000:3000 -v docuseal_data:/data docuseal/docuseal:2.2.9

# Open http://localhost:3000

Or with Docker Compose, create a compose.yml:

services:
  docuseal:
    image: docuseal/docuseal:2.2.9
    ports:
      - "3000:3000"
    volumes:
      - docuseal_data:/data

volumes:
  docuseal_data:

Then run:

docker compose up -d

Category	Rating
Complexity	Easy: Just need Docker installed
Price	Free, no hosting costs
Customizability	High: Full local control

Pros:

✅ Completely free: No hosting costs
✅ Instant setup: One command to start
✅ Great for testing: Experiment without consequences
✅ Development friendly: Test API integrations locally

Cons:

❌ Not for production: Your laptop isn't a server
❌ No public access: Others can't access your instance
❌ Data loss risk: If you forget to persist volumes
❌ Resource usage: Uses your laptop's CPU/RAM

Best for: Developers who want to test DocuSeal, develop integrations, or evaluate features before committing to a hosting solution.

4. Kubernetes — The Enterprise Way

For organizations with existing Kubernetes infrastructure or those needing enterprise-grade scalability and high availability, deploying DocuSeal on K8s is an option.

But before you go down this path: Read our article on why Kubernetes probably isn't for you. For most teams, it's massive overkill. Also check out Docker vs Kubernetes to understand the key differences.

How it works:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: docuseal
spec:
  replicas: 2
  selector:
    matchLabels:
      app: docuseal
  template:
    metadata:
      labels:
        app: docuseal
    spec:
      containers:
      - name: docuseal
        image: docuseal/docuseal:2.2.9
        ports:
        - containerPort: 3000
        volumeMounts:
        - name: docuseal-data
          mountPath: /data
      volumes:
      - name: docuseal-data
        persistentVolumeClaim:
          claimName: docuseal-pvc
---
apiVersion: v1
kind: Service
metadata:
  name: docuseal
spec:
  selector:
    app: docuseal
  ports:
  - port: 80
    targetPort: 3000
  type: ClusterIP

You'll also need:

Persistent Volume Claims for data storage
Ingress controller for HTTPS
Optionally: PostgreSQL deployed separately for scalability

Category	Rating
Complexity	Very Complex: K8s expertise required
Price	$70-200+/month (managed K8s clusters aren't cheap)
Customizability	Very High: Full infrastructure control

Pros:

✅ High availability: Multiple replicas, auto-healing
✅ Enterprise-ready: Fits into existing K8s workflows
✅ Infrastructure as code: GitOps-friendly deployments

Cons:

❌ Massive overkill for most — You probably don't need this
❌ Complex setup: Requires K8s expertise
❌ Expensive: Managed K8s clusters aren't cheap
❌ Operational overhead: More moving parts = more things to break

Best for: Large enterprises with dedicated DevOps teams who already run Kubernetes and need to integrate DocuSeal into their existing infrastructure.

5. DocuSeal SaaS — The Official Cloud

Don't want to self-host at all? DocuSeal.com offers their own managed cloud service. They handle everything: hosting, updates, backups, and support.

How it works:

Sign up at docuseal.com
Choose a plan
Start creating and sending documents

Category	Rating
Complexity	Very Easy: Just sign up and use
Price	$13+/month per user (most expensive option)
Customizability	Low: Limited to what they offer

Pros:

✅ Zero maintenance: DocuSeal team handles everything
✅ Official support: Direct help from the creators
✅ Always up-to-date: Automatic updates with latest features
✅ Free tier available: Limited free plan for testing

Cons:

❌ Most expensive option: Paid plans start at $13/month per user
❌ Per-user pricing: Costs scale with team size
❌ Data on their servers: Less control over data residency
❌ Usage limits: Document limits on lower tiers

Best for: Teams who don't want any technical responsibility and are okay paying premium prices for a fully managed experience with official support.

Comparison Table

Here's a quick summary to help you choose:

Feature	Sliplane	VPS (Self-Hosted)	Local	Kubernetes	DocuSeal SaaS
Complexity	Very Easy	Intermediate	Easy	Very Complex	Very Easy
Setup Time	30 seconds	30-60 minutes	1 minute	Hours/Days	5 minutes
Monthly Cost	€9+	€3-10	Free	$70-200+	$13+/user
Customizability	Medium	High	High	Very High	Low
Maintenance	Managed	You handle it	N/A	You handle it	Managed
HTTPS/SSL	Automatic	Manual setup	N/A	Manual setup	Automatic
Updates	One-click	Manual	Manual	Manual	Automatic
Scalability	Good	Manual	N/A	Excellent	Good
Data Control	Your server	Full control	Full control	Full control	Their servers
Best For	Most users	DIY enthusiasts	Testing	Enterprises	Non-technical

Which Should You Choose?

Let me make it simple:

Want the best balance of ease and cost? → Sliplane: One-click deploy, €9/month, no DevOps needed
Want the absolute cheapest option? → VPS Self-Hosting: €3-5/month, but you manage everything
Just want to test it out? → Local Docker: Free, instant, no commitment
Running a large enterprise with K8s? → Kubernetes: Only if you already have the expertise
Don't want to touch any infrastructure? → DocuSeal SaaS: Pay premium for zero maintenance

For 90% of users, Sliplane offers the best value: production-ready deployment in 30 seconds, predictable pricing, and zero server management. You get the cost benefits of self-hosting without the headaches.

Cheers,
Atakan

Self-hosting DocuSeal on a Hetzner Ubuntu Server

atakanozt — Fri, 16 Jan 2026 18:33:03 +0000

Want to sign documents using DocuSeal but prefer to fully control your infrastructure? By self-hosting DocuSeal on a Linux Ubuntu server, you can cut down costs, keep your sensitive documents private, and avoid per-signature fees!

Looking for something simpler? Deploy in 25 seconds

Prerequisites

Before we start, make sure you have:

A Hetzner account (or any other cloud provider)
Basic SSH experience
An SSH key pair on your local machine

Step 0: Create a Server on Hetzner

Log into your Hetzner Cloud Console and click Create Resource.

Choose Shared Resources > Cost-Optimized. The CX23 server (2 vCPU, 4GB RAM) is perfect at just €2.99/month.

Select a location close to your users and Ubuntu 24.04 as the operating system.

Add your SSH public key:

# On macOS
pbcopy < ~/.ssh/id_ed25519.pub

# On Linux
cat ~/.ssh/id_ed25519.pub

Give your server a name and click Create & Buy now. Once created, copy the IP address and connect:

ssh root@YOUR_SERVER_IP

Step 1: Update Your Server

sudo apt-get update
sudo apt-get upgrade -y

Step 2: Install and Configure UFW Firewall

sudo apt install ufw -y
sudo ufw allow 22    # SSH
sudo ufw allow 80    # HTTP
sudo ufw allow 443   # HTTPS
sudo ufw enable

Verify with sudo ufw status verbose.

Note: Docker can sometimes ignore UFW rules. See this guide for extra settings.

Step 3: Docker Installation

Setup dependencies and Docker's GPG key:

sudo apt-get update
sudo apt-get install ca-certificates curl gnupg

sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg \
| sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg

Add Docker repository:

echo \
  "deb [arch=$(dpkg --print-architecture) \
signed-by=/etc/apt/keyrings/docker.gpg] \
https://download.docker.com/linux/ubuntu \
$(. /etc/os-release && echo $VERSION_CODENAME) stable" \
| sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

sudo apt-get update

Install Docker Engine:

sudo apt-get install docker-ce docker-ce-cli \
containerd.io docker-buildx-plugin docker-compose-plugin -y

Verify with sudo docker run hello-world.

Step 4: Installing Caddy for Automatic HTTPS

Caddy handles SSL certificates automatically from Let's Encrypt.

Important: Point your domain's A record (IPv4) and AAAA record (IPv6) to your server's IP before this step.

sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https curl

curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' \
| sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg

curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' \
| sudo tee /etc/apt/sources.list.d/caddy-stable.list

sudo apt update
sudo apt install caddy -y

Edit the Caddyfile:

sudo nano /etc/caddy/Caddyfile

Replace contents with:

yourdomain.com {
    reverse_proxy localhost:3000
}

Restart Caddy: sudo systemctl restart caddy

Step 5: Running DocuSeal with Docker Compose

Create a directory and compose file:

mkdir ~/docuseal
cd ~/docuseal
nano compose.yml

Add the following:

services:
  docuseal:
    image: docuseal/docuseal:2.2.9
    restart: always
    ports:
      - "3000:3000"
    volumes:
      - docuseal_data:/data

volumes:
  docuseal_data:

Deploy:

sudo docker compose up -d

Step 6: Access Your DocuSeal Instance

Visit your domain in any web browser. Follow the setup steps to create your admin account.

🎉 Congratulations! You now have your own self-hosted DocuSeal instance!

Optional Configurations

Using PostgreSQL Instead of SQLite
For production environments, update your compose.yml:

services:
  docuseal:
    image: docuseal/docuseal:2.2.9
    restart: always
    depends_on:
      - postgres
    ports:
      - "3000:3000"
    volumes:
      - docuseal_data:/data
    environment:
      - DATABASE_URL=postgres://docuseal:your_secure_password@postgres:5432/docuseal

  postgres:
    image: postgres:16
    restart: always
    volumes:
      - postgres_data:/var/lib/postgresql/data
    environment:
      - POSTGRES_USER=docuseal
      - POSTGRES_PASSWORD=your_secure_password
      - POSTGRES_DB=docuseal

volumes:
  docuseal_data:
  postgres_data:

Restart: sudo docker compose down && sudo docker compose up -d

Configuring Email Notifications
Add SMTP settings to your compose.yml:

environment:
  - SMTP_ADDRESS=smtp.example.com
  - SMTP_PORT=587
  - SMTP_USERNAME=your-email@example.com
  - SMTP_PASSWORD=your-password
  - SMTP_DOMAIN=your-domain.com

Updating DocuSeal
Since we're using a specific version tag (2.2.9):

Check for new versions on DocuSeal's DockerHub
Update the image tag in compose.yml
Run:

cd ~/docuseal
sudo docker compose pull
sudo docker compose up -d

Security Recommendations

Regularly apply updates and security patches
Set strong passwords and control user access
Monitor server logs for suspicious activity
Install Fail2ban for extra security
Keep Docker images updated
Set up regular backups of your /data volume

Cost Comparison with SaaS Alternatives

Service	Monthly Cost	Documents/Month	Custom Branding
DocuSign	€45-€65+	Limited	Paid plans only
HelloSign	€25-€65+	Limited	Paid plans only
PandaDoc	€35-€65+	Limited	Paid plans only
Hetzner (self-hosted)	~€3-5	Unlimited	Free

Comparison with Managed Hosting

Provider	vCPU	RAM	Monthly Cost
Render.com	1	2 GB	~€35-€45
Fly.io	2	2 GB	~€20-€25
Railway	2	2 GB	~€15-€66*
sliplane.io	2	2 GB	~€9/month flat

*Railway charges for actual usage.

With self-hosting on Hetzner, you get similar specs for ~€3/month, but you handle all setup and maintenance.

See the full tutorial with screenshots on Sliplane.io

If managing your own server is too much, check out how easy it is to deploy DocuSeal on Sliplane in just 25 seconds!

Happy self-hosting! 🚀

Self-hosting DocuSeal the easy way

atakanozt — Fri, 09 Jan 2026 16:40:20 +0000

DocuSeal is an open-source document signing platform that enables you to create, send, and manage document signing workflows. Whether you're handling contracts, agreements, or any other documents that need signatures, DocuSeal provides a powerful alternative to expensive SaaS solutions like DocuSign or HelloSign.

The best part? You can self-host DocuSeal and maintain complete control over your sensitive documents while saving significant costs. In this tutorial, we're going to set up a DocuSeal instance on Sliplane for only €9 per month with full control and no usage limitations!

Deploy DocuSeal Now

Why Self-Host DocuSeal?

Cost Savings: Save 80%+ compared to SaaS document signing services
Data Privacy: Keep all your documents and signatures on your own infrastructure
No Usage Limits: Sign unlimited documents without per-signature fees
Full Control: Customize branding, workflows, and integrations
Compliance: Meet GDPR, and other regulatory requirements
No Vendor Lock-in: Your data stays with you, always

Setup

Signup at sliplane.io, the signup is free and you can use your Github Account to login.
Create a server: If you already have a server, you can skip this step. If not, go to > Servers and then click > Create Server
Create a service: go to your projects (create a new one or use the default one) and click > Deploy Service (top right)
- Select the DocuSeal preset (You can also use the Docker image directly if you prefer)
Click deploy, wait for the service to be up and then open the domain provided by sliplane. You can find that in the service settings, it should be service-name.sliplane.app
Follow the setup steps in the DocuSeal dashboard and you're done!

Your DocuSeal instance is ready for initial setup!

You did it! 🎉

Comparison to other Hosting platforms

Of course you can also self-host DocuSeal with other cloud providers. Here is a pricing comparison for the most common ones:

Provider	vCPU Cores	RAM	Disk	Estimated Monthly Cost	Notes
Render.com	1	2 GB	40 GB	~€35–€45	€35
Fly.io	2	2 GB	40 GB	~€20–€25	€17
Railway	2	2 GB	40 GB	~€15–€30	€66*
sliplane.io	2	2 GB	40 GB	~€9	~€9/month flat

Note: Railway charges for actually used memory and cpu time. €66 is the max price, actual price might vary.

Comparison to SaaS Alternatives

Self-hosting DocuSeal also saves you significant money compared to managed document signing services:

Service	Monthly Cost	Documents/Month	Custom Branding	Data Location
DocuSign	€45–€65+	Limited	Paid plans only	US servers
HelloSign	€25–€65+	Limited	Paid plans only	US servers
PandaDoc	€35–€65+	Limited	Paid plans only	US servers
Self-hosted DocuSeal	€9	Unlimited	Free	Your servers

FAQ

You got questions? We got answers!

Is self-hosted DocuSeal the same as the SaaS version?
Self-hosted DocuSeal gives you access to all the core features of the open-source version:

Create and manage document templates
Send documents for signing
Track signing status in real-time
Collect multiple signatures
Custom branding and white-labeling
API access for integrations
Webhook support

The main difference is that you manage the infrastructure yourself, but you get complete control and unlimited usage!

Can I use PostgreSQL or MySQL instead of SQLite?
Yes! By default, DocuSeal uses SQLite which is perfect for small to medium deployments. For production environments or larger scale usage, you can configure DocuSeal to use PostgreSQL or MySQL by adding the DATABASE_URL environment variable in your service settings:

DATABASE_URL=postgres://user:password@host:5432/dbname

You can deploy a PostgreSQL or MySQL service in the same project and connect DocuSeal to it.

Are there any usage based costs with sliplane?
Compute is always a flat, fixed price.

How do I update the DocuSeal version?
If you used the latest tag, you can simply redeploy the service (there is a button on the dashboard for that). If you used a specific version, you can update it by changing the image tag in the Sliplane settings and redeploying the service.

Can I customize the branding?
Yes! DocuSeal supports full white-labeling and custom branding. You can customize logos, colors, email templates, and more through the DocuSeal admin interface.

Is my data secure?
Absolutely! With self-hosting, you have complete control over your data:

All documents are stored in your own volumes
No data leaves your server unless you configure external storage
You can implement additional security measures as needed
Full compliance with GDPR, HIPAA, and other regulations

Can I integrate DocuSeal with my application?
Yes! DocuSeal provides a comprehensive REST API that allows you to:

Create and manage templates programmatically
Send documents for signing via API
Track signing status
Receive webhooks for signing events
Download completed documents

Check the DocuSeal API documentation for detailed integration guides.

What about email notifications?
DocuSeal can send email notifications for document signing events. You'll need to configure SMTP settings in the environment variables. Add these to your service settings:

SMTP_ADDRESS=smtp.example.com
SMTP_PORT=587
SMTP_USERNAME=your-email@example.com
SMTP_PASSWORD=your-password
SMTP_DOMAIN=your-domain.com

Do I need a custom domain?
No, you can use the default service-name.sliplane.app domain that Sliplane provides. However, if you want to use a custom domain for branding purposes, you can configure it in your service settings. Sliplane automatically handles SSL certificates for custom domains.

See the full tutorial on Sliplane.io

Happy self-hosting! 🚀

If you have any questions, drop them in the comments below!

[Boost]

atakanozt — Fri, 09 Jan 2026 12:17:19 +0000

Tech Stack Lessons from scaling 20x in a year

Jonas Scholz ・ Jan 9

#webdev #docker #devops #startup