Self-host Plane with Levelrail
An open-source project management tool for tracking issues and cycles, an alternative to Linear and Jira.
- Authormakeplane
- LicenceAGPL-3.0
- Memory2 GiB
- Archarm64
- Services7
How to self-host Plane
-
Pull the images
7 images are pulled on your server.
Show images
makeplane/plane-backend:v1.3.0postgres:15.7-alpineghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Zrabbitmq:3.13.6-management-alpinevalkey/valkey:7.2.11-alpinemakeplane/plane-proxy:v1.3.0makeplane/plane-frontend:v1.3.0
-
Create the app
7 services start in a single Compose app, with 7 named volume mounts for your data, on port 80.
-
Fill in the secrets
7 secrets are generated and stored encrypted, 16 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Plane requirements
- Memory
- About 2 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0, network copyleft (agpl) license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Plane. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Plane docs page.
Deploy Plane your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Plane from the CLI
levelrail-cli templates deploy plane --name my-plane Deploy Plane with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/plane/deploy Plane configuration
Plane services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| api | makeplane/plane-backend:v1.3.0 | none | plane_logs_api -> /code/plane/logs |
| plane-db | postgres:15.7-alpine | none | plane_db_data -> /var/lib/postgresql/data |
| plane-minio | ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Z | none | plane_uploads -> /export |
| plane-mq | rabbitmq:3.13.6-management-alpine | none | plane_mq_data -> /var/lib/rabbitmq |
| plane-redis | valkey/valkey:7.2.11-alpine | none | plane_redis_data -> /data |
| proxy | makeplane/plane-proxy:v1.3.0 | 80 | plane_proxy_config -> /configplane_proxy_data -> /data |
Show all 7 services
- webmakeplane/plane-frontend:v1.3.0Ports: none. Volumes: none
Plane environment variables
| Variable | Service | Value |
|---|---|---|
| AMQP_URL | api | Generated at deploy |
| AWS_ACCESS_KEY_ID | api | Preset by the template |
| AWS_S3_BUCKET_NAME | api | Preset by the template |
| AWS_S3_ENDPOINT_URL | api | Preset by the template |
| AWS_SECRET_ACCESS_KEY | api | Generated at deploy |
| DATABASE_URL | api | Generated at deploy |
| MINIO_ENDPOINT_SSL | api | Preset by the template |
| REDIS_URL | api | Preset by the template |
Show all 23 variables
- SECRET_KEYapiGenerated at deploy
- USE_MINIOapiPreset by the template
- WEB_URLapiPreset by the template
- POSTGRES_DBplane-dbPreset by the template
- POSTGRES_PASSWORDplane-dbGenerated at deploy
- POSTGRES_USERplane-dbPreset by the template
- MINIO_ROOT_PASSWORDplane-minioGenerated at deploy
- MINIO_ROOT_USERplane-minioPreset by the template
- RABBITMQ_DEFAULT_PASSplane-mqGenerated at deploy
- RABBITMQ_DEFAULT_USERplane-mqPreset by the template
- RABBITMQ_DEFAULT_VHOSTplane-mqPreset by the template
- APP_DOMAINproxyPreset by the template
- BUCKET_NAMEproxyPreset by the template
- FILE_SIZE_LIMITproxyPreset by the template
- SITE_ADDRESSproxyPreset by the template
Ports and volumes
- Ports
- 80
- Volumes
- 7 named mounts: plane_logs_api -> /code/plane/logs, plane_db_data -> /var/lib/postgresql/data, plane_uploads -> /export, plane_mq_data -> /var/lib/rabbitmq, plane_redis_data -> /data, plane_proxy_config -> /config, plane_proxy_data -> /data
Plane FAQ
How much memory does Plane need?
The catalog lists about 2 GiB of memory for Plane across its 7 services.
Does Plane run on arm64?
For Plane, an arm64 image is published; amd64 is image published.
What licence is Plane under?
Plane is licensed under AGPL-3.0, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Plane need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Plane bundle?
The template includes Postgres and Redis, running as its own service.
Which ports does Plane use?
Plane listens on port 80 inside the stack.
Where does Plane keep its data?
In named volumes: plane_logs_api mounted at /code/plane/logs, plane_db_data mounted at /var/lib/postgresql/data, plane_uploads mounted at /export and plane_mq_data mounted at /var/lib/rabbitmq.
Can I deploy Plane on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id plane for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image makeplane/plane-backend:v1.3.0, postgres:15.7-alpine, ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Z, rabbitmq:3.13.6-management-alpine, valkey/valkey:7.2.11-alpine, makeplane/plane-proxy:v1.3.0, makeplane/plane-frontend:v1.3.0 is what you deploy there.