Deploy and Host Plane on Railway

Plane is an open-source project management tool and an alternative to Jira, Linear and Asana. Teams track work items in list, board, calendar and timeline layouts, plan sprints with cycles, group work into modules, write specs in Pages and triage requests through Intake. This template runs Plane Community Edition (AGPL-3.0), the free self-hosted edition.

About Hosting Plane

Plane is not a single container. It runs a web app, a Space app for published views, an admin app, a real-time collaboration server, a Django API, a Celery worker and scheduler and its own proxy, on top of Postgres, Redis, RabbitMQ and S3-compatible storage. This template deploys the official Plane images, pinned to v1.4.2, as twelve Railway services on the private network, with only the proxy exposed. It also fixes what breaks Plane's Docker setup on Railway: your administrator is created on first boot so no visitor can claim /god-mode/, sign-ups are closed, every secret is generated, migrations run under a lock, storage stays private behind signed uploads, and Celery and RabbitMQ no longer start one process per host CPU.

Common Use Cases

Issue tracking and sprint planning for software teams leaving Jira or Linear
Product roadmaps organised in modules and cycles
Specs and internal docs in Pages, next to the work they describe
Collecting bug reports and feature requests through Intake
Sharing a public roadmap with published project views

Dependencies for Plane Hosting

Official Plane images: makeplane/plane-backend, plane-frontend, plane-space, plane-admin, plane-live and plane-proxy, pinned to v1.4.2
Railway PostgreSQL and Redis
RabbitMQ 3.13 for Plane's background task queue
Silo, the maintained MinIO fork Plane ships with, for uploaded files

Deployment Dependencies

Plane source code: https://github.com/makeplane/plane
Plane instance administration: https://developers.plane.so/self-hosting/govern/instance-admin
Template repository: https://github.com/jean82290/plane-railway

Implementation Details

The first deploy takes about five minutes while the API runs Plane's database migrations. Then open the public URL of the Plane service and sign in with the email you entered and the ADMIN_PASSWORD value from the Plane API service's Variables tab (use its copy button). Create your workspace and invite your team. The same account manages the instance at /god-mode/: email, Google or GitHub sign-in, AI features and sign-up rules.

Variable (Plane API)	Purpose
ADMIN_EMAIL	Email of the administrator created on first boot
ADMIN_PASSWORD	Generated password for that account, used on first boot only
PLANE_VERSION	Official image tag for every Plane service; set a newer release and redeploy to upgrade
ENABLE_SIGNUP	0 admits invited people only (default), 1 lets anyone with the URL sign up
GUNICORN_WORKERS	API processes, 1 by default to keep usage low

Measured idle, the stack uses about 1.3 GB of RAM, roughly $13 a month of Railway usage; expect $15 to $25 a month for a small team. Railway only allows outbound email (SMTP) on the Pro plan; without it, invited people can still create their account at your URL with the invited address.

This is a community template, not affiliated with Plane Software, Inc.

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