Zammad on Railway
Open-source helpdesk and ticketing with email, chat and SLAs, running the full stack on Railway.
Zammad is an open-source helpdesk and ticketing system. It turns email, web forms, live chat and other channels into tickets with owners, states, SLAs, triggers and a knowledge base. It is used for shared support inboxes and for internal IT or HR helpdesks.
It is often compared with Zendesk and Freshdesk; the difference is that you host it yourself and keep the data. Zammad is maintained by Zammad GmbH.
Zammad is licensed AGPL-3.0.
What Zammad can do
- Tickets from email, web forms and live chat
- SLAs, triggers and automations
- Knowledge base
- Groups and roles
- Elasticsearch-backed search
- Microsoft 365 and IMAP mailbox channels
What people use it for
- A shared support inbox with SLAs
- Live chat on a website with tickets from conversations
- An internal IT or HR helpdesk
- Replacing a hosted helpdesk with a self-hosted one
Videos
Running Zammad on Railway
The template deploys Zammad 7.2.2 as nine services: nginx, Rails server, scheduler and websocket from the official image, plus Elasticsearch 9.5, Postgres 18, Redis 8.2 and Memcached, and a backup service that writes a nightly pg_dump and keeps 10 days. Migrations run before start and the first administrator is created from your email. Elasticsearch is the largest memory user, so cost follows it and the Rails services. Idle usage measured locally was about 3.2 GB of RAM across the services.
Zammad templates on Railway
Tracklayer templates are listed first. Other Zammad templates follow, ordered by total deployments on Railway. How this works.
Deployment numbers as of 2026-11-20.
Questions about Zammad
How do I log in?
Enter your email in ZAMMAD_ADMIN_EMAIL when deploying. When zammad-nginx is healthy, log in with that email and the generated ZAMMAD_ADMIN_PASSWORD from the zammad-railsserver variables, then change the password.
Can it send email from Railway?
Fetching mail over IMAP works on every plan. Sending replies needs outbound SMTP, which Railway allows on the Pro plan, or the Microsoft 365 channel, which works over HTTPS.
What drives the cost?
Nine services run, and Elasticsearch is the largest memory user, followed by the Rails server and scheduler. It grows with ticket count.
How do backups work?
zammad-backup writes a compressed pg_dump every night to a volume in the same project. Restore by placing a dump in /var/tmp/zammad/restore/ on that service and redeploying it.
Which licences apply?
Zammad is AGPL-3.0. Elasticsearch and Redis 8 are multi-licensed upstream. This is a community template, not affiliated with Zammad GmbH.
Similar apps
Tracklayer maintains the templates marked as such; Zammad is a trademark of its owners and this site is not affiliated with them.