How do I deploy continuwuity on Railway?

You can deploy continuwuity on Railway by clicking the "Deploy Now" button on this page. Railway will automatically set up all the necessary services and configurations for you.

What are the system requirements?

Railway handles all the infrastructure requirements. You only need a web browser to deploy and manage your application.

Is this template free to use?

Yes, this template is free to use within your existing Railway account.

Can I customize this template?

Yes, you can fully customize this template. After deployment, you will have full control of what you've deployed in your Railway project.

How do I get support for this template?

You can get support through our community forum: continuwuity-72e3abc6, or click "Get template help" for this template for more assistance.

Deploy and Host continuwuity on Railway

Continuwuity is a lightweight Matrix homeserver written in Rust — the community-driven continuation of conduwuit. It enables decentralized, federated real-time communication over the Matrix protocol, designed to run efficiently on modest hardware. It supports federation, appservice bridges, and per-user identities out of the box.

About Hosting continuwuity

Hosting continuwuity involves running a single stateful binary (or OCI container) that handles Matrix client and federation APIs. It uses RocksDB as its embedded database — no external database server needed. You configure a server name (your domain), expose port 8448 for federation and 443 for clients (typically via a reverse proxy with TLS), and mount a persistent volume for the RocksDB data directory. The container image is minimal (no shell, just the binary and TLS certificates), making it well-suited for platform deployments. Configuration is done entirely through environment variables or a TOML file.

Common Use Cases

Private team or family chat server — Run a self-hosted Matrix homeserver for internal communication with full control over data and identity
Bot and agent infrastructure — Register per-user accounts for AI agents, bots, or bridges that need native Matrix identities (no prefix hacks)
Federated communication hub — Join the wider Matrix network, bridge to platforms like Discord or Slack via appservices, and communicate across organizations

Dependencies for continuwuity Hosting

Persistent volume — RocksDB storage for the database at /var/lib/continuwuity/
Domain name with TLS — Required for Matrix federation and client access (Railway provides this automatically)

Deployment Dependencies

OCI image: ghcr.io/continuwuity/continuwuity (also mirrored to docker.io/jadedblueeyes/continuwuity)
Continuwuity deployment docs
Continuwuity Docker guide
Continuwuity configuration reference
Matrix federation spec

Implementation Details

Key environment variables for deployment:

CONTINUWUITY_ALLOW_FEDERATION=false
CONTINUWUITY_SERVER_NAME=your.domain.com
CONTINUWUITY_PORT=6167
CONTINUWUITY_ADDRESS=0.0.0.0
CONTINUWUITY_DATABASE_PATH=/var/lib/continuwuity
CONTINUWUITY_ALLOW_REGISTRATION=true
CONTINUWUITY_REGISTRATION_TOKEN=auto-generated-token

The container listens on port 6167 internally and alsready exposed for http connections. Map it to 8448 externally for federation, or let Railway handle TLS termination on port 443. Healthcheck endpoint: GET /_matrix/client/versions (unauthenticated, returns supported spec versions).

Why Deploy continuwuity 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 continuwuity 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.