Deploy Plane in one click.
Open-source project management with issues, cycles and modules. We review it, secure it and run it in production for you. Pick a region in Switzerland, France or Germany, or bring your own machines through a secure tunnel. We keep it patched, backed up and online. You just ship.
★ 49k stars · AGPL-3.0 · TypeScript · tested versions · shipped with a runbook
What is Plane?
Jira-shaped project management: open source, self-hosted, and considerably easier to look at.
Plane is an open-source project management tool. It gives teams issues, cycles for time-boxed work, modules for grouping it, and pages for the documentation around it. It’s the shape teams know from Jira, in a cleaner interface you can self-host. Multiple projects, custom states and priorities keep larger organizations organized in one place.
A project tracker is a map of everything you haven’t shipped yet. Roadmaps, security issues under embargo, customer escalations, who’s working on what. It’s some of the most strategically sensitive data a company writes down. Self-hosting Plane keeps that map on infrastructure you control instead of a third-party cloud.
The catch: self-hosting means someone has to run it. Plane is several services: web, API, workers and a database. Add reverse proxy, TLS, authentication, upgrades, security patches and backups of every issue your team tracks. That someone is usually you, at the worst possible time.
Plane, without the ops.
Everything below is what you’d otherwise build and babysit yourself.
Your roadmap stays where you put it.
Deploy to ch-zh1 (Zurich), fr-pa1 (Paris) or de-fr1 (Frankfurt). Issues, cycles and pages stay in the region you choose, under Swiss or EU law and in line with GDPR.
Reviewed before it ships.
Our Plane package is reviewed, secured and locked to versions we have tested, and it ships with a runbook. We track CVEs upstream and patch them fast.
Several services, one deploy.
Self-hosted Plane is a small fleet: web, API, workers, database. We ship it as one reviewed and tested package that deploys, upgrades and rolls back as a unit.
TLS, upgrades, scaling: handled.
Certificates issued and renewed, rolling zero-downtime updates, instant rollback, health checks. Plane ships releases steadily; we keep you current without stopping a sprint.
Backups you can actually restore.
Offsite backups of your issues, cycles, pages and attachments. We run restore drills, not just snapshots.
Leave whenever you want.
Plane is open source and so is your exit: your data leaves with you, in usable form. Pilae runs it for you. It never owns it.
Self-hosting Plane: DIY vs Pilae.
Both paths end with Plane in production. Only one of them ends there this afternoon.
| Self-hosted DIY | On Pilae | |
|---|---|---|
| Initial setup | Docker, reverse proxy, DNS, auth. An afternoon if nothing fights back | One click, live in minutes |
| TLS certificates | Issue, wire up, remember to renew | Issued and renewed automatically |
| Upgrades | Frequent releases to track, test and apply yourself | Tested versions, rolled out with instant rollback |
| Security patching | You watch the CVE feed | Upstream tracked, CVEs prioritized |
| Backups | cron + object storage + hope | Offsite, verified with restore drills |
| Data residency | Wherever your VPS happens to be | You pick: Zurich, Paris, Frankfurt, or your own racks |
| 3 a.m. failures | Yours | Ours |
| Moving parts | Web, API, workers, database, composed and babysat by you | One reviewed package, deployed and upgraded as a unit |
| Attachments & uploads | Object storage to provision and secure yourself | Provisioned with the deployment, backed up offsite |
From catalog to production in three steps.
No servers to set up, no configuration to write. The platform work is already done.
Pick Plane.
Find it in the catalog: reviewed, secured, locked to tested versions, runbook included.
Choose where it runs.
A Pilae region in Switzerland, France or Germany, or your own machine connected through a secure tunnel. Same console either way.
Deploy and move your projects in.
One click to production with TLS and backups from day one. Create your workspace, set up projects and cycles, invite your team, done.
Your roadmap is strategy in writing. Keep it close.
Every Plane deployment is pinned to the region you choose. Encryption, dedicated VLANs, and the option to hold your own encryption keys for regulated workloads. Or skip our regions entirely and run it on-prem.
Deploying Plane: the questions we get.
If yours isn’t here, reach out and we’ll answer it, usually the same day.
What’s the easiest way to self-host Plane?
Deploying it through a managed platform. On Pilae you pick Plane from the catalog, choose a region, and click deploy. TLS, backups, patching and upgrades are handled for you from the first minute. You get self-hosting’s control without its ops.
Is Plane a real alternative to Jira?
For many teams, yes. Issues, cycles, modules and pages cover the workflow most teams actually use, in a cleaner interface. The difference is where it runs: on infrastructure you control, in a country you chose.
What does self-hosted Plane need to run?
Several services: web, API, workers and a database. That’s exactly why DIY deployments drift. On Pilae the whole set ships as one reviewed and tested package that deploys and upgrades as a unit.
Where does my Plane data live?
In the region you choose: Zurich, Paris or Frankfurt, or on your own infrastructure. Issues, cycles, pages and attachments stay there, encrypted. For regulated workloads you can hold your own encryption keys.
How do Plane updates and security patches work on Pilae?
We track upstream, prioritize CVEs, and ship updates locked to versions we have tested, rolled out with zero downtime and instant rollback. You stay current without watching the release feed.
Can I move my Plane deployment off Pilae later?
Yes, and that’s by design. Plane is open source and your data exits with you in usable form: issues, cycles, pages, attachments. No proprietary formats, no lock-in.
Runs well next to.
Build your stack from the same catalog. One console, one click each.
Self-hosted team chat. Replace Slack while keeping conversations resident.
Files, mail, calendar, talk. A self-hosted workspace for the team.
Workflow automation with 400+ integrations. Self-hosted, source-available.
Bitwarden-compatible password manager, lightweight and self-hosted.
Plane, without the ops.
Deploy it in minutes, keep your data in the country you choose, and leave whenever you want. Your data goes with you.