---
title: "Deploy SignuDoc"
description: "Self-hosted e-signature app to send, sign and seal PDFs"
category: "Other"
url: https://railway.com/deploy/deploy-signudoc-e-signature
---

# Deploy SignuDoc

Self-hosted e-signature app to send, sign and seal PDFs

**[Deploy SignuDoc on Railway](https://railway.com/template/deploy-signudoc-e-signature)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/deploy-signudoc-e-signature/manifest.json

- **Creator:** onepush
- **Category:** Other

## Template content

### signudoc https://api.iconify.design/mdi/draw-pen.svg

- **Image:** ghcr.io/onepush-dev/signudoc:0.5.2
- **Health check:** /api/auth/ok
- **Public domain:** Yes

### postgres https://devicons.railway.app/postgres

- **Image:** postgres:17-alpine

## Documentation

# Deploy and Host self hosted SignuDoc (Other) on Railway

This template runs SignuDoc, an MIT-licensed self-hosted e-signature app, as independent community packaging of NYLLON-SOFTWARE/SignuDoc v0.5.2 at commit 24ecc5d (Copyright 2026 Nyllon Software). It is not affiliated with or endorsed by SignuDoc, Nyllon Software, or DocuSign.

## About Hosting SignuDoc open-source software on Railway (self hosted SignuDoc template)

SignuDoc is an MIT-licensed e-signature app you can run yourself, so the PDFs and signatures stay in infrastructure you control.

Railway provisions both services, wires the database connection, gives you an HTTPS domain, and restarts the app if its health check at /api/auth/ok fails.

## Why Deploy SignuDoc, the self-hosted e-signature app on Railway

Hosted e-signature services charge per user or envelope, and that grows with your team.

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying SignuDoc on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

### Railway vs Other Hosting Providers and VPS for SignuDoc self hosting

Self-hosting SignuDoc means running the app, Postgres and a volume of signed PDFs, so your platform choice sets how much you maintain.

| Provider | What You Get with Railway | What You Get with the Other Provider |
| --- | --- | --- |
| DigitalOcean | Both services, bundled Postgres and the /data volume come from the template, with health checks and restarts set. | A Droplet you control, so you install Docker, set up Postgres, manage the volume and keep the app updated. |
| AWS | The template connects signudoc and postgres over private networking with no manual network setup. | Broad control over instances, storage and networking, but you design and maintain the whole stack. |
| Hetzner | A few clicks with generated secrets and a persistent volume, without managing the server underneath. | Low-cost servers, but you handle the OS, Docker, backups and the SignuDoc setup yourself. |

## Common Use Cases for hosted SignuDoc

- **Sending a contract for signature:** Upload a PDF, place signature and date fields for each party, and invite signers by link so they can sign from any browser.
- **Collecting an NDA or offer letter:** Add signers in order, track who has signed, and receive a sealed PDF with an audit trail once everyone is done.
- **Keeping signed records in one place:** PDFs are stored on the Railway volume at /data and envelope data lives in the bundled Postgres service, so your signed copies stay with your deployment.
- **Running a small team's approvals:** Give colleagues an account on your own install and send internal documents for sign-off without routing them through a third-party service.
- **Testing e-signature workflows privately:** Spin up a throwaway instance to try the full send, sign and seal flow before deciding whether to adopt it.

## Dependencies for SignuDoc Docker hosted on Railway

This template runs two services: signudoc, the web app, and postgres:17-alpine, which holds application data on the private network and restarts On Failure.

### Deployment Dependencies for Managed SignuDoc Service

The signudoc service is public on port 8080 with a volume at /data for stored PDFs. Keep one replica of each.

### Implementation Details for SignuDoc

The image ghcr.io/onepush-dev/signudoc:0.5.2 is built from unmodified NYLLON-SOFTWARE/SignuDoc at commit 24ecc5d on Node 24, since there is no upstream image.

The template variables are DATABASE_URL, which references the bundled postgres service, APP_URL, which uses the Railway HTTPS domain and should be updated for a custom domain, BETTER_AUTH_SECRET, SETUP_TOKEN, which /setup requires, RETENTION_JOB_SECRET, and POSTGRES_PASSWORD on postgres.

## How does SignuDoc compare against other tools

### SignuDoc vs a hosted e-signature service (Hosted E-Signature Alternative)

- **Where it stays:** SignuDoc runs in your Railway project, with PDFs on a /data volume and data in bundled Postgres.
- **Cost model:** You pay Railway usage instead of per-seat fees, and SignuDoc is MIT licensed.
- **Where hosted wins:** Mature hosted products offer more integrations and single sign-on.
- **Signing emails:** These are not delivered unless you add RESEND_API_KEY.

### SignuDoc vs emailing PDFs for wet-ink signatures (Wet-Ink Signature Alternative)

- **Audit trail:** SignuDoc produces a sealed PDF with an audit trail, which an emailed PDF does not.
- **Round trips:** Signers open a link on any device, so you skip printing and rescanning.
- **Where wet ink wins:** Some documents still require a physical signature.
- **Setup cost:** Emailing needs no setup, while SignuDoc needs a first-run /setup with SETUP_TOKEN.

### SignuDoc with Docker vs Railway (Docker and Railway Deployment Comparison)

- **Docker:** Running the ghcr.io/onepush-dev/signudoc:0.5.2 image gives full host control, but you supply Postgres and storage yourself.
- **Railway:** The template wires signudoc and postgres together, adds a /data volume, and checks /api/auth/ok.
- **Replicas:** Keep one replica of each service, since local persistent state does not scale across replicas.
- **Where Docker wins:** A bare Docker host avoids a platform dependency.
## How to use SignuDoc on Railway?

1. Open the public domain from your signudoc service. It goes to /setup on first visit.
2. Paste the SETUP_TOKEN value from the signudoc Variables tab, enter a support address, and create the first administrator account.
3. Sign in, upload a PDF into a draft envelope, place the signature and date fields, and invite your signers.
4. Without RESEND_API_KEY, signing emails are not delivered. Share the signing links directly, or add a Resend key to send them.
5. If you add a custom domain, update APP_URL to match it so links and emails point to the right address.
6. Keep one replica of each service, since local PDF storage and Postgres data are persistent state.

```
Health check: /api/auth/ok (timeout 300 seconds)
Restart policy: Always (signudoc), On Failure (postgres)
```

## How to self host SignuDoc on other VPS Services (SignuDoc self hosting guide)

### Clone the Repository

Clone the unmodified upstream source at the pinned commit, then move into the folder. Check the commit before you build.

```bash
git clone https://github.com/NYLLON-SOFTWARE/SignuDoc.git
cd SignuDoc
git checkout 24ecc5d
```

### Install Dependencies

Use Node 24, then install the packages the app needs. Postgres runs on the same machine or on a host you can reach.

```bash
npm install
```

### Configure Environment Variables

Copy the example file and set your own values. Generate each secret yourself and keep it stable. Add a Resend key only if you want signing emails sent.

```bash
cp .env.example .env
# set DATABASE_URL, APP_URL=https://your-domain, BETTER_AUTH_SECRET,
# SETUP_TOKEN and RETENTION_JOB_SECRET
# optional: RESEND_API_KEY, RESEND_FROM_EMAIL, SUPPORT_EMAIL
```

### Start the SignuDoc Application

Follow the upstream flow: upstream: follow the self-hosting guide for a machine with Postgres, local file storage and an optional Resend key; see the upstream repository.

## Pricing and License of SignuDoc (SignuDoc pricing)

SignuDoc is open-source software released under the MIT license, so you can run it yourself at no software cost.

## SignuDoc hosted vs self hosted comparison (Pricing, features, costs, and more)

This template packages the MIT-licensed upstream software.

### Monthly cost of self hosting SignuDoc on Railway

Your monthly cost on Railway is usage-based. Check your Railway dashboard for the figures that match your own documents.

### System Requirements for Hosting SignuDoc on a VPS

Running the upstream app on a VPS requires a Node 24 runtime, a Postgres database, and persistent disk space for uploaded PDFs.


After each deploy, open the public domain and confirm the health check passes before you treat the service as ready. Keep one replica of any service that holds local persistent state, because a second replica would not see the same volume data. Copy the generated values from the Variables tab into your own records, and keep signing or encryption keys stable across redeploys. If you attach a custom domain, update the public URL variables to that origin before you rely on callbacks, invites, media links or sign-in. Optional mail, AI or agent features need credentials you supply later and are not required to boot this template. Untested upgrades, backups and restores stay your responsibility; this overview only reports the recorded first-deploy checks. When something fails, start with the service logs and the health path before you rotate generated secrets. The template is zero-input: generated secrets and service references are created at deploy time, so you can open the service as soon as it is healthy. Do not change variable names or values from this overview; set only what you need after the first boot, such as a custom domain or an optional provider key. Read the service logs on first boot if migrations or first-run setup take longer than you expect, and wait for the health check to pass before you.

## Frequently Asked Questions (FAQs)

### How do I claim the install?

Open your public domain, which takes you to /setup.

### Why are signing emails missing?

EMAIL_DRIVER is intentionally left unset, so signing emails are not delivered by default.

### What should I back up?

Back up the /data volume, which holds the stored PDFs, and the Postgres volume at /var/lib/postgresql.

### Can a stranger finish setup?

Not if SETUP_TOKEN stays set. The first-run setup page requires that token, so someone without it cannot claim the install.

### Is this affiliated with DocuSign?

No.


## Similar templates

- [Rocky Linux](https://railway.com/deploy/rocky-linux) — Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀
- [Foundry Virtual Tabletop](https://railway.com/deploy/X5tR6G) — Self-hosted virtual tabletop for role-playing games (license required)
- [Double Commander in your browser](https://railway.com/deploy/double-commander-in-your-browser) — The Double Commander file manager in the cloud, from any device

Open this page in a browser: https://railway.com/deploy/deploy-signudoc-e-signature
