Self-host Plane on a VPS

An open-source project management tool for tracking issues and cycles, an alternative to Linear and Jira.

levelrail-cli templates deploy plane --name my-plane

Specification

Status
Listed
Category
Productivity
Services
api, plane-db, plane-minio, plane-mq, plane-redis, proxy, web
Ports
80
Volumes
7
Memory
about 2 GiB
arm64
image published
amd64
image published
Settings to fill in
none

About Plane

An open-source project management tool for tracking issues and cycles, an alternative to Linear and Jira. Runs 7 containers (api, plane-db, plane-minio, plane-mq, plane-redis, proxy, web), with proxy listening on port 80; data is kept in named volumes.

What it deploys

Plane runs as 7 services in a single Compose app, listening on port 80, with 7 named volume mounts.

ServiceImageTagPortsVolumes
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
web makeplane/plane-frontend v1.3.0 none none

Before you install

  • CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
  • Listed. It is in the catalog. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 80 directly on the host, so open them in the VPS firewall only if you want that.

Settings and environment

You do not have to fill in anything. 7 secrets are generated at deploy and stored encrypted. Values are never shown here.

ServiceVariableValue
apiAMQP_URLGenerated at deploy
apiAWS_ACCESS_KEY_IDPreset by the template
apiAWS_S3_BUCKET_NAMEPreset by the template
apiAWS_S3_ENDPOINT_URLPreset by the template
apiAWS_SECRET_ACCESS_KEYGenerated at deploy
apiDATABASE_URLGenerated at deploy
apiMINIO_ENDPOINT_SSLPreset by the template
apiREDIS_URLPreset by the template
apiSECRET_KEYGenerated at deploy
apiUSE_MINIOPreset by the template
apiWEB_URLPreset by the template
plane-dbPOSTGRES_DBPreset by the template
plane-dbPOSTGRES_PASSWORDGenerated at deploy
plane-dbPOSTGRES_USERPreset by the template
plane-minioMINIO_ROOT_PASSWORDGenerated at deploy
plane-minioMINIO_ROOT_USERPreset by the template
plane-mqRABBITMQ_DEFAULT_PASSGenerated at deploy
plane-mqRABBITMQ_DEFAULT_USERPreset by the template
plane-mqRABBITMQ_DEFAULT_VHOSTPreset by the template
proxyAPP_DOMAINPreset by the template
proxyBUCKET_NAMEPreset by the template
proxyFILE_SIZE_LIMITPreset by the template
proxySITE_ADDRESSPreset by the template

Install Plane on a VPS

  1. Install Levelrail on a fresh VPS

    Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.

    curl -fsSL https://levelrail.com/install.sh | sudo sh
  2. Sign in

    Open the setup link, choose a password, then log the CLI in. The CLI install command is curl -fsSL https://levelrail.com/install-cli.sh | sh if the machine does not have it. See Getting started.

    levelrail-cli login --device
  3. Read the template

    Shows the entry, including its full compose.yaml.

    levelrail-cli templates get plane
  4. Deploy it

    This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.

    levelrail-cli templates deploy plane --name my-plane

Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Plane.

More in Productivity

All Productivity templates