We deploy five open-source platforms for managing work. They are not five competing project-management products — they answer different questions, and most clients need one or two of them rather than all five.
What are you trying to manage?
Why five products rather than one
That question is the whole conversation. Five products, five distinct problems — which is a great deal clearer than five platforms competing for the same buyer.
The portfolio at a glance
| Product | Primary positioning | Best customer need | Where it stops |
|---|---|---|---|
| MantisBT | Software issue and bug management | Development and QA teams needing serious defect tracking | Not a project-planning system. Deliberately. |
| GLPI | ITSM and asset management | IT departments, help desks, inventory and licence control | Not built for agile software delivery. |
| ZenTao | Product, project and quality management | Software organisations needing traceability and complex workflows | More structure than a non-technical department will sustain. |
| ProjeQtOr | Project, portfolio and risk management | PMOs accountable for plan, cost, resource and risk | Not an engineering traceability chain. ZenTao is, if that is the need. |
| Leantime | Project and work management | SMEs and teams wanting project planning without heavyweight ALM | No requirement-to-test traceability chain. |
The fourth column matters as much as the second. A product recommended without a stated limit is a product being oversold.
Why we selected these
Every platform here had to clear the same four tests. They are stated as things these products have, because that is what you are buying — not a list of what other software lacks.
Criterion 01
A transparent open-source licence
You can read the licence, read the source, and see the roadmap being decided in public. There is no licence that can be withdrawn, no price that can be raised on renewal, and no feature that can be moved into a tier you do not have. Ten years from now the software still belongs to you.
Criterion 02
Excellent capability in its own right
Each of these is a mature, actively maintained platform that would hold its own on capability alone. We are not asking you to accept a weaker tool as the price of keeping your data. Sovereignty and quality are not a trade here — that is precisely why these made the list.
Criterion 03
One clear business need each
Defects. Assets and service. Engineering lifecycle. Plan, cost and risk. Project and team work. Five distinct problems, five products, no internal competition. You buy the ones that match the questions you actually have, and we will tell you when that is one rather than five.
Criterion 04
Designed to work as one estate
They share a directory, an authentication model and a deployment discipline, and their records link to each other. A defect can trace to a requirement; a ticket can trace to an asset. The portfolio behaves as one integrated system rather than separate installations that happen to sit on the same network.
What integration actually means here
The fourth criterion is the one that pays for itself, and it is worth being concrete about. These share a common technical foundation, which means one hardening standard, one backup approach, one monitoring pattern and one upgrade rhythm across everything you run:
- PHP
- Linux
- Nginx / Apache
- MySQL / PostgreSQL
- Redis
- Docker
What one stack buys you
The runbooks we hand over are the same shape whichever platforms you run, your staff learn one operating model rather than several, and adding a second product later is an extension of what you already know rather than a new discipline. It is also why we can support all of them properly instead of spreading a team thin across unrelated technologies.
- One authentication source — LDAP or Active Directory across every platform, so joiners and leavers are handled once.
- Linked records — a monitoring alert becomes a ticket, a ticket links to an asset, a defect links to the requirement it violates.
- One backup and recovery regime — the same engines underneath, so restore testing covers the estate rather than one system at a time.
- One upgrade cycle — planned together, tested together, with the same rollback approach.
Governance, delivery and tooling
PRINCE2 is a governance framework, not a work-management tool. You do not replace PRINCE2 with any of these products — you use the product to operationalise the controls PRINCE2 defines. Three layers, and the tool is only ever the third.
Each platform carries that third layer differently, and each product page sets out its own PRINCE2 mapping: GLPI, MantisBT, ProjeQtOr, ZenTao and Leantime.
The two arguments underneath all of this
Where the estate lives. Every platform here runs entirely on your infrastructure, and what these systems hold — requirements, defect history, asset registers, ticket history — describes your organisation more completely than almost anything else you own. Where the work-management estate lives →
Which management product lives where. Thirteen PRINCE2 management products mapped against ZenTao and against ProjeQtOr, with the traceability chain that separates them. Where each PRINCE2 management product lives →