Self-host DocuSeal with Levelrail

A free, open-source document signing tool, a lighter alternative to DocuSign.

  • Authordocusealco
  • LicenceAGPL-3.0
  • Memory512 MiB
  • Archarm64
  • Services2

How to self-host DocuSeal

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • docuseal/docuseal:latest
    • postgres:16-alpine
  2. Create the app

    2 services start in a single Compose app, with 2 named volume mounts for your data, on port 3000.

  3. Fill in the secrets

    2 secrets are generated and stored encrypted, 3 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

DocuSeal requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 image published
Ports
3000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
AGPL-3.0, network copyleft (agpl) license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 3000 on the host, so open them in the VPS firewall only if you want that.
  • Review. Image is not pinned to a version tag, so a redeploy can pull different code (docuseal/docuseal:latest).

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then DocuSeal. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the DocuSeal docs page.

Deploy DocuSeal your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy DocuSeal from the CLI

levelrail-cli templates deploy docuseal --name my-docuseal

Deploy DocuSeal with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/docuseal/deploy

DocuSeal configuration

DocuSeal services

ServiceImagePortsVolumes
docuseal docuseal/docuseal:latest 3000 docuseal_data -> /data
postgresql postgres:16-alpine none docuseal_postgresql_data -> /var/lib/postgresql/data

DocuSeal environment variables

VariableServiceValue
DATABASE_URL docuseal Generated at deploy
HOST docuseal Preset by the template
POSTGRES_DB postgresql Preset by the template
POSTGRES_PASSWORD postgresql Generated at deploy
POSTGRES_USER postgresql Preset by the template

Ports and volumes

Ports
3000
Volumes
2 named mounts: docuseal_data -> /data, docuseal_postgresql_data -> /var/lib/postgresql/data

DocuSeal FAQ

How much memory does DocuSeal need?

The catalog lists about 512 MiB of memory for DocuSeal across its 2 services.

Does DocuSeal run on arm64?

For DocuSeal, an arm64 image is published; amd64 is image published.

What licence is DocuSeal under?

DocuSeal is licensed under AGPL-3.0, which is network copyleft, so source sharing also applies when it is offered as a hosted service.

Does DocuSeal need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does DocuSeal bundle?

The template includes Postgres, running as its own service.

Which ports does DocuSeal use?

DocuSeal listens on port 3000 inside the stack.

Where does DocuSeal keep its data?

In named volumes: docuseal_data mounted at /data and docuseal_postgresql_data mounted at /var/lib/postgresql/data.

Can I deploy DocuSeal on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id docuseal for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image docuseal/docuseal:latest, postgres:16-alpine is what you deploy there.

levelrail-cli templates deploy docuseal --name my-docuseal