What resources does Plane require?

The minimum configuration is 2 vCPU and 4 GB RAM for a small team (up to 10 users). For larger teams or high-volume projects, 4 vCPU and 8 GB RAM are recommended. Plane's stack requires PostgreSQL 16, Redis 7, RabbitMQ and MinIO — all included in the ServOrbit deployment recipe.

Does Plane support sprints and Gantt charts?

Yes. Cycles are Plane's equivalent of sprints: they have a start date, an end date, a burndown chart, and automatic rollover of incomplete issues. The Gantt view is available at the project level — it displays issue dependencies as a timeline and lets you drag deadlines directly on the chart.

Share information and collaborate.

Plane

Open-source alternative to Jira and Linear: issues, cycles, modules and wiki pages self-hosted — no per-seat pricing, data on your VPS.

4 GB minimum (8 GB recommended for teams > 10) RAM 2 vCPU Port 443 (HTTPS — domain required) Unavailable

Unavailable

The latest release published upstream doesn't install correctly. We've paused ordering until it's fixed, rather than handing you an installation that fails.

Tech stack

DockerDjangoReactPostgreSQL 16Redis 7RabbitMQMinIO

Minimum RAM4 GB minimum (8 GB recommended for teams > 10)

Minimum CPU2 vCPU

Default port443 (HTTPS — domain required)

Compatible OSChoice of Linux distributions

Plane (AGPL-3.0, 32 k+ GitHub stars) is an open-source project management platform designed to replace Jira, Linear and Asana. It gives engineering and product teams a complete workspace: issues with custom states and priorities, cycles (sprints) with burndown charts, modules to group related issues, and wiki pages to document decisions alongside the code.

Deployed on ServOrbit, Plane runs in a multi-container Docker Compose stack (Django API, React SSR, Celery worker, scheduler, PostgreSQL 16, Redis 7, RabbitMQ and MinIO) proxied behind Nginx on your own domain. You pay a fixed monthly cost per VPS — no per-seat licence, no token budget, no SaaS metering. The full REST API is open: Jira and GitHub Issues importers work out of the box, and GitHub webhooks close issues automatically on merge.

The analytics dashboard provides real-time views of issue throughput, cycle velocity and backlog trends — data that stays on your infrastructure and is never sent to a third-party analytics service.

Key features

Issues with custom states, priorities, labels and assignees — filtered in list, Kanban, spreadsheet and Gantt views

Cycles (sprints) with burndown charts, start and end dates, and automatic rollover of incomplete issues

Modules to group issues by feature, epic or release — with completion percentage

Wiki pages integrated in the project — write documentation and decisions where the team already works

One-click import from Jira, CSV and GitHub Issues — migrate an entire backlog in minutes

GitHub webhooks: commit to close, PR to transition, branch name to auto-link issue

AGPL-3.0 licence — source auditable, no vendor lock-in, self-hosted or on ServOrbit

When to use this solution?

1

Agile development tracking

Replace Jira with a self-hosted platform: create sprints as cycles, assign issues to team members, track progress on the Kanban board and measure velocity with the burndown chart. The REST API lets your CI close issues automatically at each successful deployment — no manual status update.

2

Migration from Jira or Linear

Use the built-in Jira importer: go to Settings → Importers → Jira, generate an Atlassian API token, paste your Jira project URL and start the import. Epics become modules, sprints become cycles, and issues keep their original descriptions, labels and priorities. The migration is non-destructive — nothing is deleted in Jira.

3

Product and engineering collaboration

Keep product decisions and engineering tasks in the same workspace. Product managers write requirements in wiki pages; engineers file issues linked to those pages; designers attach mockups to issues. Everything is searchable and versioned.

Deploy Plane on your VPS

Guide optimized for ServOrbit Cloud VPS.

01

Order the VPS

Choose a VPS with at least 2 vCPU and 4 GB RAM under Ubuntu 24.04. The Plane template automatically configures PostgreSQL 16, Redis 7, RabbitMQ and MinIO alongside the application stack.

02

Point your domain

Point your domain (e.g. plane.yourcompany.com) to the VPS IP address in your DNS provider. A domain is required for Plane to generate correct redirect URLs and TLS certificates.

03

First access

Open your domain in a browser. The setup wizard prompts you to create the first workspace and invite team members. Use the admin credentials provided by the deployment wizard.

04

Connect GitHub

In Settings → Integrations → GitHub, install the Plane GitHub App on your repository. Issues close automatically when a commit message references them, and branches are linked to issues in the sidebar.

Frequently asked questions

Plane is an open-source project management platform (AGPL-3.0, 32 k+ GitHub stars) that replaces Jira, Linear and Asana for engineering and product teams. It provides issues, cycles (sprints), modules, wiki pages and analytics — self-hosted on your own VPS, with no per-seat pricing.

Yes. Install the Plane GitHub App on your repository (Settings → Integrations → GitHub) and use commit messages like fix(#123) or closes #456 to transition issues automatically. Pull requests are linked to issues in the sidebar, and branches created from Plane are named after the issue.

Complementary solutions

Collaboration & Productivity

Plane isn't orderable yet.