Layer 5 · self-hosting reality check
What it actually takes to self-host Plane
The docs say 4 GB. In practice you want 8 GB, the vendor's recommendation for production. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from Jira alternatives, where Plane is one of the picks.
Wondering whether you need to at all? Is Jira free? — what the free tier actually allows, and where the wall is.
| RAM — documented minimum | 4 GB |
|---|---|
| RAM — what it really needs | 8 GB, the vendor's recommendation for production |
| CPU | 2 cores (x64 or ARM64), per the vendor |
| Disk | Not stated by the vendor. Uploads go into the bundled MinIO bucket (5 MB per file by default). PostgreSQL, Valkey and RabbitMQ keep their own volumes. Uploads are what grow. |
| Monthly cost | $24–48/mo for a 5–20 user instance on an 8 GB VPS, plus object storage if you follow the vendor's advice to move files off the box |
| Setup time | 1 hour with setup.sh; an afternoon if it sits behind your own reverse proxy and you test uploads properly |
| How you install it | setup.sh installs the AGPL Community Edition (the docs lead with the Commercial Edition via Prime CLI, whose free plan covers 12 seats). The Community compose runs 13 containers: web, space, admin, live, api, worker, beat-worker, migrator, PostgreSQL 15, Valkey, RabbitMQ, MinIO and a proxy. |
| Ongoing maintenance | Frequent releases (Community Edition v1.4.2 in August 2026, v1.4.3 in review in September), applied through setup.sh's upgrade option. For production the vendor strongly recommends an external database and object storage, which means more services for you to run. |
| Where it stops scaling | The compose file has replica counts for the web, api and worker containers, so you can widen one 8 GB box. Past that, the vendor points to an external PostgreSQL, S3 storage and a Kubernetes deployment. |
The thing that catches people out
File storage is Plane's weak point. Uploads go through a bundled MinIO, and upstream MinIO is gone. Its community images stopped in October 2025, and minio/minio disappeared from Docker Hub around 12 September 2026. Upgrades then failed on the image pull (#9823) until Plane switched its release compose to a community MinIO build on 28 September. Separately, behind your own HTTPS proxy, attachments break with http:// or wrong-host URLs, a recurring report (#5827, #6624, #6740). Set WEB_URL to the https address and MINIO_ENDPOINT_SSL=1, or point Plane at real S3-compatible storage. Test an upload before you invite anyone.
When not to self-host Plane
You want few moving parts. Plane's Community Edition is 13 containers, including a message broker and object storage. If a small team just needs boards, Vikunja or Kanboard runs as one container. If you want Plane itself without the operations work, use its hosted plans.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 5 self-hosting guides
- Self-hosting LibreOffice2 GB with a large spreadsheet open
- Self-hosting ONLYOFFICE6 GB for the Document Server with a handful of concurrent editors
- Self-hosting Collabora Online4 GB, and roughly 1 GB per 20 concurrent documents
- Self-hosting CryptPad2 GB for a small instance
- Self-hosting Mattermost4 GB for a team of 50 with PostgreSQL on the same box
- Self-hosting Rocket.Chat6 GB with MongoDB on the same machine
Common questions
- How much RAM does Plane actually need?
- 8 GB, the vendor's recommendation for production in practice. The documented minimum is 4 GB, which is the figure at which the process starts rather than the figure at which it works under real use. 2 cores (x64 or ARM64), per the vendor alongside it.
- What does self-hosting Plane cost per month?
- $24–48/mo for a 5–20 user instance on an 8 GB VPS, plus object storage if you follow the vendor's advice to move files off the box This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for frequent releases (Community Edition v1.4.2 in August 2026, v1.4.3 in review in September), applied through setup.sh's upgrade option. For production the vendor strongly recommends an external database and object storage, which means more services for you to run.
- How long does it take to set up Plane?
- 1 hour with setup.sh; an afternoon if it sits behind your own reverse proxy and you test uploads properly, via setup.sh installs the AGPL Community Edition (the docs lead with the Commercial Edition via Prime CLI, whose free plan covers 12 seats). The Community compose runs 13 containers: web, space, admin, live, api, worker, beat-worker, migrator, PostgreSQL 15, Valkey, RabbitMQ, MinIO and a proxy..
- When should I NOT self-host Plane?
- You want few moving parts. Plane's Community Edition is 13 containers, including a message broker and object storage. If a small team just needs boards, Vikunja or Kanboard runs as one container. If you want Plane itself without the operations work, use its hosted plans.
- What is the most common mistake when self-hosting Plane?
- File storage is Plane's weak point. Uploads go through a bundled MinIO, and upstream MinIO is gone. Its community images stopped in October 2025, and minio/minio disappeared from Docker Hub around 12 September 2026. Upgrades then failed on the image pull (#9823) until Plane switched its release compose to a community MinIO build on 28 September. Separately, behind your own HTTPS proxy, attachments break with http:// or wrong-host URLs, a recurring report (#5827, #6624, #6740). Set WEB_URL to the https address and MINIO_ENDPOINT_SSL=1, or point Plane at real S3-compatible storage. Test an upload before you invite anyone.