Deploy Zulip

Threaded team chat with Postgres, RabbitMQ, Redis and Memcached

Deploy Zulip

Just deployed

Just deployed

/var/lib/rabbitmq

/data

Just deployed

/data

Just deployed

/var/lib/postgresql/data

Deploy and Host Zulip on Railway

Zulip is an open-source team chat app (Apache-2.0) where every conversation has a topic, so busy channels stay readable and people can catch up without scrolling. It has web, desktop and mobile apps, threads, search, file uploads, integrations and a full REST API. It is an open alternative to Slack.

About Hosting Zulip

Zulip needs five pieces: the Zulip server (Django, Tornado for real-time events, nginx and queue workers), PostgreSQL, RabbitMQ, Redis and Memcached. This template runs Zulip Server 13.2 with all five as separate Railway services on the private network, each password generated at deploy time and every piece of state on a volume. Railway provides HTTPS on a public domain. On the first boot Zulip runs its database migrations and creates an organization named "Zulip" with you as owner, which takes about four minutes. You only enter your email. Then read the generated ZULIP_ADMIN_PASSWORD in the Zulip service's Variables tab and log in.

Common Use Cases

  • Team and company chat where each discussion keeps its own topic
  • Open-source and community chat with public channels and guest access
  • Self-hosted Slack replacement that keeps message history and files on your own infrastructure

Dependencies for Zulip Hosting

  • PostgreSQL 14 with PGroonga and hunspell dictionaries (Zulip's zulip-postgresql image), for data and full-text search
  • RabbitMQ (queue), Redis (rate limits) and Memcached (cache)

Deployment Dependencies

Implementation Details

Services: Zulip (public, port 80, health check /health, volume /data for uploads and the secrets file), Postgres (volume /var/lib/postgresql/data), RabbitMQ (volume /var/lib/rabbitmq), Redis (Railway's Redis, with a volume) and Memcached (SASL password, cache only).

After deploy:

  1. Wait until the Zulip service is healthy (the first boot runs migrations).
  2. Open https://YOUR-DOMAIN/ and log in with ZULIP_ADMIN_EMAIL and ZULIP_ADMIN_PASSWORD (Zulip service, Variables tab). Change the password under Settings.
  3. Optional: add outgoing email so Zulip can send invitations and password resets (SETTING_EMAIL_HOST, SETTING_EMAIL_HOST_USER, SETTING_EMAIL_PORT, SETTING_EMAIL_USE_TLS, SETTING_NOREPLY_EMAIL_ADDRESS, SECRETS_email_password on the Zulip service). To use your own domain, add it in Railway and set SETTING_EXTERNAL_HOST to it.

Updates: every service builds from the template's GitHub repo with images pinned by version and digest. When a new Zulip release is merged there, Railway shows you an "update available" notice. Read the repo's CHANGELOG.md, then apply it, and Zulip runs its migrations on the next boot.

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


Template Content

More templates in this category

View Template
Rocky Linux
Hosted Rocky Linux 9 workspace with SSH and persistent storage. 🚀

codestorm
51
View Template
Foundry Virtual Tabletop
Self-hosted virtual tabletop for role-playing games (license required)

Lucas
71
View Template
NEW
Double Commander in your browser
The Double Commander file manager in the cloud, from any device

Nermin Sabanovic
0