A managed Plane environment for planning, delivery work and project knowledge.
Plane brings projects, work items, cycles, modules, pages and views into one workspace. Choose Plane Cloud or one of three self-hosted editions. iTmethods brings platform-operations expertise and Reign Ops to deploy and run a dedicated self-hosted Plane environment, with the edition, deployment location, operating duties and change process agreed in writing.
Plane offers one hosted edition and three self-hosted editions; Community is open source.
WHAT YOU GET
What a managed Plane environment gives you.
Planning, delivery work and project knowledge live together.
Projects, work items, cycles, modules, pages and views hold the plan, the work and the supporting documentation in one workspace.
Operating and change decisions have named owners.
The edition determines who hosts the environment. The written scope records the deployment location, administrative access, operating duties and change approvals.
Engineering teams have more time for product and software delivery.
Reign Ops takes on the agreed deployment, upgrades, monitoring, backup and recovery, access and change duties, allowing customer engineers to spend more time on delivery work.
Teams reach Jira cutover knowing what moved and what needs attention.
A representative pilot and Plane's Import Summary show what was imported, skipped or errored, and which other items need review or rebuilding before rollout.
PRODUCT FIT
One workspace for planning and delivery.
Plane organizes work through projects and work items. Cycles support time-boxed planning, Modules group work, Pages hold documentation, and Views show the same work in different layouts.
Roles and permissions, workflows and approvals, automations, estimates, time tracking, audit logs and dashboards support the way teams plan and govern work. Integrations, a REST API and webhooks connect Plane to the delivery tools around it.
EDITIONS AND DEPLOYMENT
Choose the edition and the deployment boundary.
Plane comes in four editions: Plane Cloud as its hosted edition, and Community, Commercial and Airgapped for self-hosting. Plane publishes setup guides for Docker Compose and Kubernetes.
Plane Cloud
Hosted by Plane.
Community
Self-hosted. Open source under AGPL v3.0.
Commercial
Self-hosted. Plane describes it as closed source.
Airgapped
A Commercial Edition built for isolated environments.
Community, Commercial and Airgapped are the self-hosted editions Reign Ops can operate. The edition sets the source model, available plans, feature set and update path.
MIGRATION
Move from Jira with a tested path to cutover.
iTmethods brings platform-migration experience and a staged method: inventory the current Jira environment, prepare Plane, run a representative pilot, reconcile the results, then move remaining projects in controlled waves.
Plane provides importer paths for Jira Cloud and Jira Server or Data Center. The Import Summary records imported, skipped and errored items.
Issues
Become work items.
Sprints
Become Cycles.
Components
Become Modules.
Manual review or rebuild. Plane's guide treats dashboards, reports, Advanced Roadmaps, Marketplace app data, automation rules, permission schemes and outside integrations as manual-review or rebuild categories. The pilot establishes which items can move, which need rework and what the team must validate before cutover.
AI CONNECTIONS
Connect approved AI tools through Plane's MCP server.
Plane publishes an open-source MCP server under the MIT license. Compatible AI clients can create and update work items, plan cycles and query projects in natural language.
Plane documents connections for Claude, ChatGPT, Codex, Cursor and VS Code, with hosted OAuth, personal-access-token and self-hosted connection methods. The server acts as the authenticated user, with access governed by the selected workspace and Plane roles.
Check before you connect. Check the available tools, authentication method, workspace permissions and permitted changes before enabling a connection.
OPERATING RESPONSIBILITY
Who operates it.
Reign Ops manages and operates enterprise technology environments. For Plane, iTmethods deploys and runs the agreed self-hosted environment, with responsibility for upgrades, monitoring, backup and recovery, access and change stated in the written scope.
iTmethods holds a SOC 2 Type II attestation for Reign Ops; the report, scope and period are available under non-disclosure. The customer's risk, compliance and procurement experts assess the selected architecture, service scope and supporting evidence against the organization's requirements.
Stated in the written scope
- Plane edition and deployment target
- Deployment and upgrades
- Monitoring
- Backup and recovery
- Access
- Change approvals and customer owners
- Service levels
QUESTIONS
Questions we are asked.
What is Plane?
Plane is a work-management platform for planning, tracking and documenting work through projects, work items, cycles, modules, pages, views and integrations.
Which edition fits my deployment?
Plane Cloud is hosted by Plane. Community, Commercial and Airgapped are self-hosted editions with different source models, features and update paths. The right choice depends on where the system needs to run and the capabilities your teams require.
Can Plane connect to AI tools?
Yes. Plane publishes an MIT-licensed MCP server for compatible clients including Claude, ChatGPT, Codex, Cursor and VS Code. Access follows the selected connection method, workspace and Plane roles.
How does Jira migration work?
iTmethods uses a staged migration method built around inventory, preparation, a representative pilot, reconciliation and controlled rollout. Plane provides separate importer paths for Jira Cloud and Jira Server or Data Center, with an Import Summary recording imported, skipped and errored items.
What would Reign Ops cover?
The written scope sets the Plane edition, deployment target, operating duties, customer owners, service levels and change process. Reign Ops can cover deployment, upgrades, monitoring, backup and recovery, access and change for the agreed self-hosted environment.
STARTING POINT
Bring your requirements to the first conversation.
Bring the platform your teams use today, where the system needs to run, the integrations they depend on and the records you need to retain. We can discuss which Plane edition fits, how iTmethods would operate a dedicated environment, and what the move from your current platform involves.