---
title: "Deploy SimpleX SMP Server"
description: "Private SimpleX SMP relay with persistent identity and public TCP ingress"
category: "Queues"
url: https://railway.com/deploy/simplex-smp-server
---

# Deploy SimpleX SMP Server

Private SimpleX SMP relay with persistent identity and public TCP ingress

**[Deploy SimpleX SMP Server on Railway](https://railway.com/template/simplex-smp-server)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/simplex-smp-server/manifest.json

- **Creator:** Tom
- **Category:** Queues
- **Total deploys:** 2

## Template content

### simplex https://raw.githubusercontent.com/monotykamary/railway-template-simplex-chat/03a650e21bc565b44e14dace1b564cc3dde3ad49/icon.png

- **Source:** https://github.com/monotykamary/railway-template-simplex-chat
- **Health check:** /cgi-bin/healthz
- **Public domain:** Yes

## Documentation

# Deploy and Host a SimpleX SMP Relay on Railway

## About Hosting a SimpleX SMP Relay

A SimpleX SMP relay stores and forwards encrypted message queues without user identifiers. This template deploys the official SimpleXMQ SMP server `v7.0.1`, a Railway TCP-port adapter, and a secret-safe status page.

### Upgrading an existing deployment to v7.0.1

v7.0.1 starts on v6.5.2 data in place and keeps the server keys, so existing `smp://` addresses and older clients keep working. To roll back to v6.5.2 later, first rename `/etc/opt/simplex/state/smp-server-stats.log`, which v6.5.2 cannot read (only the cumulative statistics are lost).

## Common Use Cases

- Operate a private relay for SimpleX Chat users
- Control queue-creation access with a shared password
- Add geographic or organizational relay diversity
- Persist relay identity and undelivered queues

## Dependencies for SimpleX SMP Relay Hosting

### Deployment Dependencies

The template creates one source-backed service, one Railway TCP proxy targeting application port `5223`, one public HTTP domain targeting `8080`, and one volume mounted at `/etc/opt/simplex`. Do not change the generated TCP proxy references or volume mount.

### Implementation Details

The service advertises the Railway TCP hostname and externally assigned port while listening through an internal forwarding adapter. `/cgi-bin/healthz` checks the live TLS listener. On first boot, the official server generates its CA, fingerprint, and configuration. All identity and queue state is consolidated into the single volume; subsequent boots preserve it.

SimpleX SMP has no administrator account. The generated `SIMPLEX_CREATE_PASSWORD` controls new queue creation. The public landing page shows how to assemble the `smp://` address but never renders that password.

### Why Deploy a SimpleX SMP Relay on Railway?

Railway supplies a stable TCP ingress, HTTPS status page, generated secret, health checks, and persistent disk. The adapter handles the port translation required by the SMP protocol while leaving the official relay binary unchanged.

## Similar templates

- [Celery | Web, Worker and Scheduler as Three Services](https://railway.com/deploy/celery-or-web-work-1) — Web, worker and scheduler wired up: Celery on Redis, outcomes in Postgres.
- [Redpanda](https://railway.com/deploy/redpanda-1) — Redpanda 26.2: Kafka-compatible streaming, single node, with Kafbat UI.
- [smoothmq](https://railway.com/deploy/AJv-64) — A drop-in replacement for AWS SQS

Open this page in a browser: https://railway.com/deploy/simplex-smp-server
