---
title: "Deploy OpenSign"
description: "Self-hosted document signing — upload, place fields, send for signatures"
category: "Other"
url: https://railway.com/deploy/opensign
---

# Deploy OpenSign

Self-hosted document signing — upload, place fields, send for signatures

**[Deploy OpenSign on Railway](https://railway.com/template/opensign)**

- **Creator:** Gamified Studio
- **Category:** Other
- **Total deploys:** 11

## Template content

### MongoDB

- **Image:** mongo:8.0

### server

- **Source:** https://github.com/Sokanon/railway-opensign

### client

- **Source:** https://github.com/Sokanon/railway-opensign

## Documentation

# Deploy and Host OpenSign on Railway

OpenSign is an open-source digital document signing platform and a self-hosted alternative to DocuSign. It provides document upload, signature field placement, and email-based signing workflows, all running on your own infrastructure.

## About Hosting OpenSign

OpenSign is a MERN-stack application consisting of a React frontend, a Node.js/Express backend built on Parse Server, and a MongoDB database. This template deploys all three as separate Railway services with automatic credential wiring between them. The server stores uploaded documents and signed PDFs on a persistent volume. MongoDB credentials and Parse Server keys are auto-generated. The client connects to the server's API endpoint via Railway's public domain references. For production signing workflows, you'll want to configure SMTP credentials for email notifications, though the application is fully functional without them for testing.

## Common Use Cases

- Sending contracts and agreements for legally binding digital signatures
- Building internal document approval workflows without per-signature SaaS fees
- Running a self-hosted signing solution under your own domain for compliance requirements

## Dependencies for OpenSign Hosting

- MongoDB (included in this template)

### Deployment Dependencies

- [OpenSign Documentation](https://docs.opensignlabs.com/)
- [OpenSign GitHub Repository](https://github.com/OpenSignLabs/OpenSign)
- [OpenSign Website](https://www.opensignlabs.com/)

### Implementation Details

The template uses a monorepo structure with `server/` and `client/` subdirectories. MongoDB connects with `?authSource=admin` for Railway's managed MongoDB authentication. File storage defaults to local volumes (`USE_LOCAL=true`), but can be switched to S3-compatible object storage by setting `USE_LOCAL=false` and configuring the DO_SPACE variables.

## Resource Usage

This template deploys 3 services (React client, Node.js server, MongoDB) with persistent volumes for the database and uploaded files. Resource usage scales with document volume and signing activity — expect moderate baseline costs from running three services.

## Why Deploy OpenSign on Railway?

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 OpenSign 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.

## 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) — A Self-Hosted & Modern Roleplaying Platform
- [Letta Code Remote](https://railway.com/deploy/letta-code-remote) — Run a Letta Code agent 24/7. No inbound ports, just deploy.

Open this page in a browser: https://railway.com/deploy/opensign