How different kinds of work are structured

Three fixed story types: feature, bug, and chore. Custom fields are pick-lists only, with up to 20 on Business.

Work item types with custom properties, required fields, defaults, visual identity, and activity history.

Timeboxes, progress, and unfinished work

Iterations with burndowns. Automatic rollover of unfinished stories needs a paid plan.

Project-based cycles with manual start and stop, burn-down charts, and unfinished-work transfer. An active-cycles view spans projects. Business adds automatic scheduling.

Track what ships across teams

No release object. Release work runs through Epics or Iterations.

Named releases gather work across projects with a lead, target date, status, and changelog, from Business.

What blocks what when dates change

Blocking, duplicate, and related-story links. No timeline dependencies or date shifting.

Finish-to-start, start-to-start, and finish-to-finish dependencies, with dates that move when upstream work changes. Critical path shows on the Timeline.

The speed people feel every day

Keyboard shortcuts for navigation and story updates.

Power K and shortcuts for navigation, search, filters, and common work-item actions.

How work rolls up across the organization

Objectives group epics. Key Results only on Business and above. Separate workspaces don’t report across each other.

Initiatives connect projects across teams with owners, states, dates, and updates. Teamspaces show each team’s work across projects.

Find the work that matters

Search operators combine with AND only. No query language.

Plane Query Language for precise filters, saved views, and dashboards, from Pro. Plane AI writes PQL from plain language.

Reporting people can open themselves

No custom dashboards. Metrics reports need a paid plan.

Dashboards start on Pro. Business adds advanced widgets for analysis across projects and teams.

Rules for how work moves

One workflow per team, and one in total on Free. No transition rules.

Control who moves work between states, with type-specific workflows and designated approvers.

Required sign-off before work moves

No

Designated approvers sign off before work moves, with a fallback state for rejected work.

Who can see, manage, and change work

Fixed roles, no custom roles. Permissions only at the workspace level, and no guests who can comment.

Admin, Contributor, Commenter, and Guest roles per project. Guests aren’t billed. Custom roles and granular permissions on Enterprise Grid.

Review project structure in Git

No native config as code.

Plane Compose defines project configuration in YAML. Version it in Git, sync through the CLI, and reuse across workspaces.

Support engineering and business teams in one workspace

Built for software teams. Other teams share one flat workspace or get their own, with no reporting across workspaces.

Engineering, product, and business teams share one workspace, with dedicated Teamspaces, custom workflows, docs, and cross-project reporting.

Long-form context beside the work

No workspace wiki. Docs sit in collections, with no version history for users.

Project Pages plus a workspace Wiki with nested pages, collections, page locking, external publishing, and Notion/Confluence imports.

Turn outside requests into trackable work

No intake forms or email intake. Requests arrive through Slack or integrations.

In-app Intake starts on Free. Business adds email intake and public forms that need no account.

Pull requests linked to work

GitHub, GitLab, and Bitbucket Cloud links for branches, commits, and pull requests.

GitHub (including Enterprise Server) and GitLab (including self-managed) with two-way sync. Bitbucket Cloud and Data Center for pull request automation.

AI teammates that take work

Coding agents can take stories. Spec writing and planning run in Korey, a separate paid product.

Plane Agents take assignments and mentions, run on schedules or work item events, and show up in the same activity trail as people.

Use AI tools with your workspace

Hosted by Shortcut only. Not self-hostable.

MIT-licensed MCP server, hosted by Plane or run on your infrastructure.

Your provider and your keys

No. Korey runs on Anthropic models only.

Self-hosted Plane (Commercial Edition) uses your OpenAI or Anthropic keys, AWS Bedrock, Ollama, or any OpenAI-compatible endpoint.

Run in your infrastructure

No. Cloud only.

Deploy Plane on your infrastructure using Docker or Kubernetes.

Run without external network access

No

Yes. Run Plane fully isolated, with no external network dependencies. Updates come from your own registry.

Controls procurement expects

SAML and SCIM are paid add-ons on Business, with SCIM through Okta only. No customer audit log.

SAML and OIDC with any identity provider. LDAP, granular access controls, and API-enabled audit logs on Enterprise Grid, plus IdP group sync on self-hosted.

Certifications, privacy, and contractual safeguards

SOC 2 Type II. No ISO 27001. BAA only on Enterprise.

SOC 2 Type II, ISO 27001:2022, and GDPR compliance. A standing BAA covers Plane Cloud.

What comes with you

Not applicable

CSV import with custom properties, interactive field mapping on Plane Cloud, and the REST API for the rest. Enterprise Grid adds migration and implementation services.