Deploy Taiga
Open-source agile project management: Scrum, Kanban, issues and wiki
Just deployed
taiga-events
Just deployed
taiga-back
Just deployed
/taiga-back/media
RabbitMQ
Just deployed
/var/lib/rabbitmq
Just deployed
/var/lib/postgresql/data
taiga-protected
Just deployed
Deploy and Host Taiga on Railway
Taiga is an open-source project management platform for agile teams. It covers Scrum backlogs and sprints, Kanban boards, epics, issues, a wiki and time-boxed planning, with real-time updates in the browser. Developed by Kaleidos, it is a self-hosted alternative to Jira and Trello for software and non-software teams.
About Hosting Taiga
Taiga is made of several parts: a Django API (taiga-back), an async worker for exports, imports, emails and webhooks, the web app (taiga-front), a websocket server for live updates (taiga-events), a small service that signs attachment links (taiga-protected), RabbitMQ and PostgreSQL. This template runs Taiga 6.10 from the official images, pinned by digest and built from a public GitHub repository. Taiga's API, its async worker and the media server share one container, so attachments live on a single Railway volume. RabbitMQ and PostgreSQL keep their data on volumes. Secrets and the first admin password are generated per deploy, so there's no default login.
Common Use Cases
- Run sprints with a Scrum backlog, user stories, story points and burndown charts
- Track work on Kanban boards and manage bugs and requests as issues
- Self-host a Jira or Trello alternative and import existing projects from them
Dependencies for Taiga Hosting
- PostgreSQL (Railway's PostgreSQL service, included)
- RabbitMQ 4.4 (included, built from the template repository)
Deployment Dependencies
- Template repository: https://github.com/aalfath/taiga-railway-template
- Official Taiga Docker setup: https://github.com/taigaio/taiga-docker
- Taiga documentation: https://docs.taiga.io/
- Taiga releases: https://github.com/taigaio/taiga-back/tags
Implementation Details
The public Taiga service serves the web app and forwards /api, /admin, /static, /media and /events to the other services over Railway's private network. On the first start, taiga-back runs the database migrations and creates an admin user:
- Username:
admin - Password: the
TAIGA_ADMIN_PASSWORDvariable of the taiga-back service
Log in, then change the password and the email in your profile. Public sign-up is off. Invite people to projects, or create users in the Django admin at /admin/.
Optional settings on taiga-back: SMTP for invitations and notifications (EMAIL_BACKEND=django.core.mail.backends.smtp.EmailBackend, EMAIL_HOST, EMAIL_PORT, EMAIL_HOST_USER, EMAIL_HOST_PASSWORD, EMAIL_USE_TLS, DEFAULT_FROM_EMAIL). For a custom domain, set TAIGA_SITES_DOMAIN on taiga-back and TAIGA_DOMAIN on Taiga. Template updates arrive through the GitHub repository. Read its CHANGELOG before you apply one.
Why Deploy Taiga 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 Taiga 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
taiga-events
aalfath/taiga-railway-templatetaiga-back
aalfath/taiga-railway-templateRabbitMQ
aalfath/taiga-railway-templatetaiga-protected
aalfath/taiga-railway-template