Self-hosted Plane, operated for you.
Reign Ops deploys and runs a dedicated, single-tenant Plane environment for your planning, delivery work and project knowledge. iTmethods takes the upgrades, monitoring, backup and recovery, access and change work, under your identity and change rules, from the team that has operated engineering platforms for two decades.
Delivered as a single-tenant dedicated instance, in your own AWS or Azure cloud account or in infrastructure iTmethods operates. Both are available today. Google Cloud is planned for 2027. Air-gapped and sovereign deployment are supported.
Your teams plan in Plane. We run it.
Plane brings projects, work items, cycles, modules, pages and views into one workspace. Reign Ops carries the work of keeping that workspace running, so your engineers spend their time on delivery.
The work sits with named iTmethods operators instead of returning to your product backlog.
Responsibilities are written down before anything is deployed, so the boundary is a document rather than a discovery.
Plane’s Import Summary shows what was imported, skipped or errored, and the pilot shows what needs review or rebuilding before rollout.
Check the available tools, authentication method, workspace permissions and permitted changes before enabling a connection.
Which Plane we operate.
Plane comes in one hosted edition and three self-hosted editions. Reign Ops operates the three self-hosted editions; the edition sets the source model, feature set and update path.
| Edition | Who hosts it | Source model |
|---|---|---|
| Community | Self-hosted, operated by Reign Ops | Open source under AGPL-3.0. |
| Commercial | Self-hosted, operated by Reign Ops | Plane describes it as closed source. |
| Airgapped | Self-hosted, operated by Reign Ops | A Commercial Edition built for isolated environments. |
| Plane Cloud | Hosted by Plane | Plane’s hosted edition. Not operated by Reign Ops. |
Move from Jira with a tested path to cutover.
Inventory the current Jira environment, prepare Plane, run a representative pilot, reconcile the results, then move the remaining projects in controlled waves. Plane provides importer paths for Jira Cloud and Jira Server or Data Center.
| In Jira | In Plane |
|---|---|
| Issues | Work items |
| Sprints | Cycles |
| Components | Modules |
| Epics | A work item type, not Plane’s dedicated Epics feature |
| Statuses | States |
| Fix and affected versions | Custom properties |
| Sub-tasks | Work items linked to their parent |
Source: Plane’s Jira importer guide, read on 27 October 2026. It does not describe boards or saved filters as imported, and only statuses map to states.
Written down before anything is deployed.
Reign Ops holds a SOC 2 Type II attestation. 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.
Which self-hosted edition, and whether it runs in your AWS or Azure account or in infrastructure iTmethods operates.
Installed, kept current and moved through your change process at a time you agree.
Watched, backed up and recoverable against the service levels written into the scope.
Administrative access, change approvals and the customer owners for each.
Questions buyers ask
Which edition fits my deployment?
How does Jira migration work?
Can Plane connect to AI tools?
What would Reign Ops cover?
Scope your Plane environment on Reign Ops.
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 will come back with which edition fits, how we would operate it, and what the move from your current platform involves.