![DocuSeal]()
DocuSeal
Container
Open source DocuSign alternative for document filling and signing. Source: https://github.com/docusealco/docuseal
Image details
Source details
Configuration
TypeContainerlinuxdocuseal/docuseal:latest3000:3000/tcp/dataHOST=unless-stoppedNotes
Standalone Install
Select an install method, to see config/commands for deploying DocuSeal
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select DocuSeal, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation, or see docusealco/docuseal for app-specific guidance.
<a href="https://www.docuseal.com">
<img alt="DocuSeal" src="https://www.docuseal.com/logo.png" width="80" />
<br>
</a>
DocuSeal
<a href="https://www.docuseal.com">
<img alt="DocuSeal" src="https://www.docuseal.com/logo.png" width="80" />
<br>
</a>
DocuSealOpen source document filling and signing
<img alt="Docker releases" src="https://img.shields.io/docker/v/docuseal/docuseal"><img src="https://img.shields.io/discord/1125112641170448454?logo=discord"/><img src="https://img.shields.io/twitter/follow/docusealco?style=social" alt="Follow @docusealco" />
DocuSeal is an open source platform that provides secure and efficient digital document signing and processing. Create PDF forms to have them filled and signed online on any device with an easy-to-use, mobile-optimized web tool.
✨ Live Demo | ☁️ Try in Cloud
Features
- PDF form fields builder (WYSIWYG)
- 12 field types available (Signature, Date, File, Checkbox etc.)
- Multiple submitters per document
- Automated emails via SMTP
- Files storage on disk or AWS S3, Google Storage, Azure Cloud
- Automatic PDF eSignature
- PDF signature verification
- Users management
- Mobile-optimized
- 7 UI languages with signing available in 14 languages
- API and Webhooks for integrations
- Easy to deploy in minutes
Pro Features
- Company logo and white-label
- User roles
- Automated reminders
- Invitation and identify verification via SMS
- Conditional fields and formulas
- Bulk send with CSV, XLSX spreadsheet import
- SSO / SAML
- Template creation with HTML API (Guide)
- Template creation with PDF or DOCX and field tags API (Guide)
- Embedded signing form (React, Vue, Angular or JavaScript)
- Embedded document form builder (React, Vue, Angular or JavaScript)
- Learn more
Deploy
| Heroku | Railway |
|---|---|
 |  |
| DigitalOcean | Render |
| 
Docker
docker run --name docuseal -p 3000:3000 -v.:/data docuseal/docusealBy default DocuSeal docker container uses an SQLite database to store data and configurations. Alternatively, it is possible use PostgreSQL or MySQL databases by specifying the
DATABASE_URL env variable.Docker Compose
Download docker-compose.yml into your private server:curl https://raw.githubusercontent.com/docusealco/docuseal/master/docker-compose.yml > docker-compose.ymlRun the app under a custom domain over https using docker compose (make sure your DNS points to the server to automatically issue ssl certs with Caddy):
sudo HOST=your-domain-name.com docker compose upFor Businesses
Integrate seamless document signing into your web or mobile apps with DocuSeal
At DocuSeal we have expertise and technologies to make documents creation, filling, signing and processing seamlessly integrated with your product. We specialize in working with various industries, including Banking, Healthcare, Transport, Real Estate, eCommerce, KYC, CRM, and other software products that require bulk document signing. By leveraging DocuSeal, we can assist in reducing the overall cost of developing and processing electronic documents while ensuring security and compliance with local electronic document laws.Book a Meeting
License
Distributed under the AGPLv3 License. See LICENSE for more information. Unless otherwise noted, all files © 2023-2026 DocuSeal LLC.Tools
Serve DocuSeal on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying docuseal.example.com to http://docuseal:3000
Add this to your Caddyfile
docuseal.example.com {
reverse_proxy http://docuseal:3000
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs docuseal - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:3000 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :3000 - Stop the other service, or pick a different host port. In
3000:3000only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:3000. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, docuseal can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 3000
Image won't pull
Test the pull directly on the host: docker pull docuseal/docuseal:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect docuseal --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Required settings are blank
HOST has no default value, and docuseal may crash or misbehave if left empty.
- Fill it in on the deploy screen before hitting deploy.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue on docusealco/docuseal
- Template not working: Open an issue within the template's repo
- This website not working: Open an issue on lissy93/portainer-templates
A single container
DocuSeal runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.
The app image
An image is the app packed up ready to go, everything DocuSeal needs bundled into one download. This template pulls docuseal/docuseal:latest, which Docker fetches once (about 219 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. DocuSeal's comes from Docker Hub, published by docuseal.
Version tags
The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 3.2.0. Pin a specific tag if you would rather stay on one version.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. A mapping like 3000:3000 means it's reachable on port 3000 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:3000 in a browser. It opens:
3000:3000, likely the web interface
Volumes
A volume is where DocuSeal keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/dataas a volume Docker manages for you
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. DocuSeal takes 1 of them, and one needs a value before it'll start properly:
HOST, needs a value. Public domain (e.g. sign.example.com) — used for links and emails
Restart policy
The restart policy here is unless-stopped, so Docker restarts DocuSeal after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Networking
Nothing custom is set, so DocuSeal sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Container name
Once it's deployed, Portainer names the container docuseal. That's what you'll spot in the containers list and use in commands like docker logs docuseal.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Open source license
DocuSeal is open source, released under the AGPL-3.0 license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set DocuSeal up. Add the template list to Portainer once, then deploying DocuSeal is a click rather than a wall of config.