Deploy Plane
Open-source Jira and Linear alternative. Plane v1.4.3, admin set at deploy
Redis
Just deployed
/data
Just deployed
Just deployed
/var/lib/rabbitmq
Just deployed
/var/lib/postgresql/data
Bucket
Bucket
Just deployed
Deploy and Host Plane on Railway
Plane is an open-source project management tool, often used as a self-hosted alternative to Jira and Linear. Teams track work items in projects, plan cycles (sprints) and modules, write pages and docs, and share views and analytics. This template runs Plane Community Edition v1.4.3 on infrastructure you control.
About Hosting Plane
Plane is several programs: the web app, the admin panel (god-mode), public spaces, a real-time editor server, a Django API, and Celery workers. It needs PostgreSQL, Redis, RabbitMQ and S3-compatible storage. This template runs Plane's official all-in-one image, built from a public GitHub repo, next to Railway Postgres, Redis, a RabbitMQ service and a Railway bucket for uploads. On first boot the start script runs the database migrations and creates your admin account from the email you enter, before the site goes online, so nobody else can claim the instance. The first deploy takes five to ten minutes, mostly database migrations. Updates come as "update available" notices when the repo moves to a new Plane release.
Common Use Cases
- Issue tracking and sprint (cycle) planning for software teams
- Roadmaps, modules and project docs in one place for product teams
- A self-hosted Jira or Linear replacement that keeps project data on your own infrastructure
Dependencies for Plane Hosting
- PostgreSQL (Railway Postgres) for all project data
- Redis (Railway Redis) for caching and the real-time editor
- RabbitMQ for Plane's background job queue
- An S3-compatible bucket (Railway bucket) for attachments, images and exports
Deployment Dependencies
- Plane: https://github.com/makeplane/plane
- Plane self-hosting docs: https://developers.plane.so/self-hosting/overview
- Plane v1.4.3 release: https://github.com/makeplane/plane/releases/tag/v1.4.3
- Template source and changelog: https://github.com/aalfath/plane-community-railway-template
Implementation Details
The only thing you enter is PLANE_ADMIN_EMAIL. After the deploy, open the Plane service's Variables tab, copy PLANE_ADMIN_PASSWORD, and sign in at your Railway domain. Change the password in your profile afterwards. Instance settings (email/SMTP, Google, GitHub or GitLab login, sign-up) are in /god-mode on the same domain. New sign-ups are off by default: invite people from your workspace, or set ENABLE_SIGNUP=1 on the Plane service before the first deploy. Optional Plane service variables: FILE_SIZE_LIMIT (bytes, default 5 MB) and CELERY_WORKER_CONCURRENCY (default 2). With a custom domain, set DOMAIN_NAME to it and redeploy.
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.
Template Content
Redis
redis:8.2PLANE_ADMIN_EMAIL
Your email: becomes Plane's instance admin and first user, created on first boot
Bucket
Bucket
