Self-host Plane as a Jira or Linear alternative on Railway
Short answer: yes. Plane is an open-source project management tool for issues, cycles (sprints), modules, pages and roadmaps, and it is a common alternative to Jira and Linear. Tracklayer’s Plane v1 template deploys the community edition on Railway as separate services behind one domain, with Postgres, Redis, RabbitMQ and a file bucket. There are no per-seat fees, but it is a large install, so plan for the Hobby plan or above.
Deploy Plane on RailwayWhen Plane makes sense
Plane fits teams that want to own their planning data:
- replacing Jira or Linear for an engineering or product team,
- planning sprints, epics and roadmaps with Kanban, list, Gantt and spreadsheet views,
- writing specs and meeting notes as collaborative Pages next to work items,
- publishing a read-only roadmap or feedback board through Plane spaces.
What the template deploys
A full Plane install is more than one container. The template runs each process as its own Railway service, pinned to Plane v1.4.2:
| Service | Role |
|---|---|
| proxy (Caddy) | The only public domain; routes the app, API, public spaces, admin and real-time paths |
| web, admin, space | Main app, instance admin, public spaces |
| live | Real-time collaboration over WebSocket |
| api | Django API; runs migrations before each release |
| worker, beat-worker | Celery worker and scheduler |
| Postgres, Redis, RabbitMQ | Data, cache and sessions, message broker |
| bucket-cors | One-shot job that sets the Bucket CORS rule, then exits |
| Bucket | Attachments, images and exports |
Because this is 12 services, check that you want that footprint before you deploy.
Deploy Plane, step by step
These steps use Tracklayer’s Plane v1 template.
- Deploy the template. There is nothing to enter. All secrets are generated.
- Wait for the api service. It runs migrations in its pre-deploy step. Each HTTP service has a health check, so a broken release stops at deploy time.
- Create the instance admin. Open
https://<proxy domain>/god-mode/. The first visitor creates the admin. - Configure instance settings in the same admin UI: SMTP, Google, GitHub or GitLab sign-in, and AI settings. Plane stores them in its database.
- Create a workspace. Open the root URL, then create a workspace, project and first work item.
- Optional: disable open sign-ups under Authentication in the admin UI.
- Test an upload. Attach an image to a work item. The template’s open questions say the Bucket CORS rule was not run against a live Bucket, so a failed browser upload points to CORS.
Persistence
Postgres, Redis and RabbitMQ each use a volume. Uploads go to the Railway Bucket using presigned URLs, so the app services keep no local files.
Cost
The template’s TEMPLATE.md gives estimates, not measurements, at Railway’s usage prices of 10 USD per GB of RAM per month, 20 USD per vCPU per month and 0.15 USD per GB of volume per month:
| Load | Estimated RAM | Estimated monthly cost |
|---|---|---|
| Idle | about 1.35 GB | about 15 USD |
| Typical, 10 to 30 users | about 2.25 GB | about 34 USD |
The api and worker services use the most memory. The template names Hobby as the minimum plan, because Trial credit does not cover a month with 12 services.
Limitations and licence
- Licence: Plane is AGPL-3.0 per the NOTICE. See the FAQ.
- Template scope: the template’s notes say the Caddy routing was smoke-tested locally against dummy upstreams, and the Plane containers themselves were not run locally. Check the pages, uploads and live editing after your first deploy.
- RabbitMQ: Plane v1.4.2 pins the 3.13 line, and the template notes that moving to RabbitMQ 4.x should be tested first.
- Custom domain: add it to the proxy, then update
WEB_URLandCORS_ALLOWED_ORIGINSon api and the CORS rule on bucket-cors.
Scaling and upgrades
Raise CELERY_WORKER_CONCURRENCY or add worker replicas for background load, and raise GUNICORN_WORKERS or add api replicas for request load. Keep beat-worker at one replica. To upgrade, change the seven v1.4.2 tags together and redeploy.
Other options
If you also need a CRM, read the guide to self-hosting Twenty CRM. For all templates, see the template directory.
FAQ
How do I log in to Plane for the first time?
Open /god-mode/ on the proxy domain and create the instance admin. The first visitor can do this, so do it straight after deploying. There you also configure e-mail and sign-in methods. Then open the root URL to create your first workspace.
Which licence does Plane use?
The template's NOTICE lists Plane under AGPL-3.0. Review that licence before you modify Plane or offer it to others over a network, and ask a lawyer if you are unsure. Redis 8 is listed under a tri-licence (RSALv2, SSPLv1 or AGPLv3).
What does Plane cost to run on Railway?
The template's figures are estimates, not measurements: about 1.35 GB of RAM at idle, roughly 15 USD per month, and about 2.25 GB for 10 to 30 users, roughly 34 USD per month. The template names Hobby as the minimum plan because it runs 12 services. Check Railway's current prices.
Is my data kept across redeploys?
Yes. Postgres, Redis and RabbitMQ each have a volume, and uploaded files go to the Railway Bucket. Redeploying does not remove them.
How do I upgrade Plane?
All Plane services share one tag. Change the seven v1.4.2 tags together and redeploy. Migrations run once in the api pre-deploy step. Back up Postgres first.