Deploy Zammad
Open-source helpdesk with search, admin set up on first boot
Redis
Just deployed
/data
Just deployed
/var/lib/postgresql/data
Just deployed
/opt/zammad/storage
Elasticsearch
Just deployed
/usr/share/elasticsearch/data
Deploy and Host Zammad on Railway
Zammad is an open-source helpdesk and customer support system. It collects email, web forms, chat, phone and social messages into one shared inbox of tickets, with SLAs, triggers, macros, a knowledge base and reports. It is a self-hosted alternative to Zendesk and Freshdesk, licensed under AGPL-3.0.
About Hosting Zammad
This template deploys Zammad 7.2.3 with four services: Zammad (public), Elasticsearch, PostgreSQL and Redis (all private). The Zammad service runs nginx, the Rails server, the websocket server and the background workers together. Every start waits for the databases, then runs Zammad's own install or migration step before the site opens. On the first start Zammad's auto wizard creates your admin account from the email you enter and a generated password, so the setup page is never open to strangers. The first start takes 3 to 6 minutes. All data stays on Railway volumes.
Common Use Cases
- A shared support inbox for a team, with assignment, SLAs and customer history
- An internal IT or HR helpdesk with a searchable knowledge base
- Moving off Zendesk, Freshdesk or OTRS to a system you host yourself, using Zammad's importers
Dependencies for Zammad Hosting
- PostgreSQL (included): tickets, users, settings and attachments
- Elasticsearch 9.5.6 (included): full-text search across tickets, articles and attachments
- Redis (included): sessions, websocket messages and background job coordination
Deployment Dependencies
- Zammad 7.2.3 release and official Docker image
- Zammad Docker Compose setup and environment variables
- Template source on GitHub
Implementation Details
You enter one value: ZAMMAD_ADMIN_EMAIL, the login of the first admin. Everything else is generated or wired up by reference.
After the deploy: open the Zammad service's domain and log in with that email and the ZAMMAD_ADMIN_PASSWORD value from the Zammad service's Variables tab. Change the password under your avatar, then Profile, then Password. Set the organization name and logo under Settings, then Branding.
Email: connect a mailbox under Settings, then Channels, then Email. Fetching mail over IMAP or POP3 works on every plan. Zammad sends mail over SMTP, which Railway allows only on the Pro plan and above.
Custom domain: add it to the Zammad service and set ZAMMAD_FQDN to it, so links in emails use it.
Data: PostgreSQL, Elasticsearch, Redis and Zammad's storage folder are all on volumes, so redeploys and restarts keep your tickets. Use the Postgres service's Backups tab for backups.
Updates: the Zammad and Elasticsearch services build from the template's GitHub repo, with images pinned by version and digest. When a new version is merged, Railway shows an "update available" notice in your project, and you choose when to apply it. Zammad migrates its database on the next start. Read the changelog in the repo first.
Why Deploy Zammad 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 Zammad 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
Redis
redis:8.2ZAMMAD_ADMIN_EMAIL
Email (and login) of the first Zammad admin; read on the first start only
Elasticsearch
aalfath/zammad-railway-template