Project platform
Plane, its database and configuration are provisioned reproducibly and updated through a controlled process.
We implement and operate Plane as an integrated project management platform - including database, object storage, identity, email delivery, migration, backups and documented operating processes.
The following are trademarks of their respective owners: Plane (Plane Software, Inc.). WZ-IT is an independent service provider and has no business, partnership, or contractual relationship with these companies. We offer independent migration, installation, hosting, and operations services.
Plane organises projects, work items, cycles, modules, pages and intake in one workspace. Different views, estimates, dashboards, the API and webhooks support day-to-day project work and integrations.
WZ-IT designs not only the web application but also PostgreSQL, cache and queue services, object storage, TLS, email delivery, identity, monitoring and recovery. We size the target system around user count, attachments, integrations and availability requirements.
Plane Community Edition is licensed under AGPLv3. The vendor also provides licensed Commercial and Air-gapped editions with additional governance, integration and operating capabilities. We verify required features and licensing terms before implementation.
When replacing an existing project management system, we inventory projects, workflow states, users, work items, comments, attachments and integrations. Migration depends on the exports and APIs actually available and is planned with a test migration, acceptance, cutover and retained raw exports.
Production Plane operations cover the application, PostgreSQL, cache and queue services, object storage, email delivery, identity and integrations. We run these components as one system while accounting for the selected edition.
Plane, its database and configuration are provisioned reproducibly and updated through a controlled process.
Projects, workflows, cycles, modules, views and intake are structured to fit how teams work.
Email, API, webhooks and edition-dependent identity or vendor integrations are connected in a controlled way.
Monitoring, updates, backups and restore tests include the application and all stateful services.
We separate technical platform operations, the working model and business project ownership.
| Area | Responsibility | Scope and boundaries |
|---|---|---|
| Architecture and provisioning | WZ-IT | Plane, PostgreSQL, cache, queue, object storage, TLS, email and reproducible deployment. |
| Plane runtime and updates | WZ-IT | Maintenance of the agreed edition with release assessment, backup and controlled updates. |
| Monitoring and backups | WZ-IT | Monitoring and consistent protection of database, uploads, configuration and other agreed services. |
| Working model and migration | Shared | WZ-IT maps projects and workflows; the customer confirms states, roles, priorities and data to be migrated. |
| Edition, identity and integrations | Shared | We verify technical dependencies; the customer procures required Commercial licences and approves systems and permissions. |
| Project content and business approvals | Customer | Content, project decisions, permission approvals, retention and data quality remain with the responsible team. |
| Custom automation and migration | Optional WZ-IT service | Interfaces, import tooling, reporting and workflow automation are implemented as a separate project module. |
Structure tasks and other work items with owners, states, priorities, dates, relationships and project-specific properties.
Plan work in time-boxed cycles and group larger initiatives into modules without separating them from projects and team context.
Review project work in list, board, calendar, spreadsheet and Gantt views and use dashboards to understand progress.
Document team knowledge in Pages and collect new requests through Intake for review before moving them into project delivery.
Connect Plane to development, support or automation workflows through the documented REST API and webhooks; individual integrations may depend on the selected edition.
Run Plane using Docker or Kubernetes and monitor, back up and update the application, PostgreSQL, cache, queue and object storage together.
A clearly defined operating scope instead of an opaque hosting flat fee.
Compute, applications, storage and response are shown separately. You can see what ongoing operations include and which requirements need a technical assessment.
We also design custom Plane architectures, integrations and migrations. Contact us for a technical assessment.
One managed standard Plane application is included in the Starter workload. Every service level also includes flexible expert time for planned work during regular service hours. Select compute, additional applications, storage and the appropriate service level.
A workload is one compute instance with the applications agreed for it.
One standard app per workload is already included. Additional dedicated servers count as separate workloads.
€79.90 per started TB and month, including daily encrypted offsite backup with 7-day retention.
User count is not the only factor. Active projects, work items, attachments, notifications, concurrent access and integrations determine compute, database and storage.
| Usage scenario | Technical starting point | Key factors |
|---|---|---|
| Small team with a few active projects | S or M, PostgreSQL | A useful starting point for Community Edition with moderate attachments and integrations. |
| Several teams using cycles, pages and dashboards | M or L, separate database and upload backups | Concurrent usage, notifications and file volume are assessed in advance. |
| Many integrations, automation or a large migration | L or custom sizing | API load, webhooks, import volume, edition and connected systems shape the architecture. |
| Business-critical or isolated environment | Custom architecture | Redundancy, recovery objectives, Kubernetes and, where required, Commercial or Air-gapped licensing are designed separately. |
Data migration, Commercial or Air-gapped licences, the Kubernetes platform and custom integrations are not included in the generic workload price.
Community Edition is available under AGPLv3. Commercial and Air-gapped are separate vendor offerings; required capabilities and licences are verified in advance.
Dedicated workload with agreed compute, backup, monitoring and service level for the selected edition.
Operation in the customer's account with existing network, identity and operating services integrated.
Self-hosting on customer virtualisation or servers with controlled access and backup.
Deployment through the documented Helm charts with aligned database, storage, ingress and recovery services.
Plane connects internal project content with notifications and external integrations. Access, data storage, attachments, events and recovery are therefore documented together.
Project members, external participants, existing project platforms, API clients and integrations.
TLS, reverse proxy or ingress, network rules and optional private access through NetBird or VPN.
Local accounts and workspace roles; additional authentication and governance capabilities are verified by edition.
Projects, work items, cycles, modules, views, pages, intake and dashboards.
Projects, work items, users, configuration and other structured platform data.
Version- and deployment-dependent services such as Redis or Valkey and RabbitMQ are included in monitoring and recovery.
Attachments and other uploads on local or S3-compatible storage with aligned protection.
Before production launch, we document edition, roles, data paths, backup scope and recovery of the complete service chain.
Answers about editions, licensing, migration, self-hosting, identity and operations.
Plane Community Edition is released under AGPLv3. The vendor also offers separate Commercial and Air-gapped editions. The current distinction is documented in the official edition overview.
That depends on the required capabilities. Community Edition can be suitable for core functions. Governance, integration, support or air-gapped requirements may require a Commercial vendor licence, which we verify in advance.
Yes, where the source system, exports and API provide the required data. We inventory projects, work items, states, users, comments, attachments and relationships and test mapping and migration before cutover.
Yes. The official self-hosting documentation describes Docker and Kubernetes deployment. We select the model according to scope, existing platform, operating effort and recovery objectives.
The database, uploads or object storage, configuration and the stateful cache and queue services of the actual deployment must be considered. We align scope with the deployed edition and version and test recovery.
Plane provides an API and webhooks; additional authentication, governance and vendor integrations can depend on edition and plan. We verify current availability and licensing before implementation.
A redundant architecture can be designed when database, cache, queue, storage, ingress and recovery are considered together. The vendor provides a separately licensed Air-gapped edition for fully isolated operation; we do not make a blanket HA or compliance guarantee.
Whether you run Plane in-house or need to host confidentiality-professional data §203-ready - we build, operate and maintain Plane on an encrypted on-site server. Data never leaves the building in cleartext.
See Plane on-premise
These solutions are often used together with Plane
These solutions offer similar functionalities and can be evaluated together
These solutions are direct alternatives with similar use cases
No risk: worst case, you leave with a clearer understanding of your project than before.


“WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.”
Whether a specific IT challenge or just an idea - we look forward to the exchange. In a brief conversation, we'll evaluate together if and how your project fits with WZ-IT.
Timo Wevelsiep & Robin Zins
Managing Directors of WZ-IT
