Visit the ProjeQtOr website
The official site of ProjeQtOr, developed in France by ProjeQtOr SAS. Opens in a new tab — hold Ctrl (⌘ on a Mac) or middle-click to keep it in the background.
www.projeqtor.comProjeQtOr manages the project rather than the code: plans and milestones, resources and workload, risks and issues, budgets and actual costs, tickets, requirements and quality records — held together in one system with a Gantt view over the top.
The reason to choose it over a lighter planner is control. It answers the questions a steering committee actually asks — where is the plan against baseline, who is over-committed, what is the cost to date against budget, which risks are open and who owns them — from records kept as the work happens rather than assembled the week before the meeting.
Who it’s for
Organisations that must steer projects on plan, cost and risk, not just track tasks.
- PMOs reporting portfolio status to a board or a steering committee
- Banks and institutions where project cost and risk must be evidenced, not estimated
- Departments running waterfall, agile and hybrid projects side by side in one portfolio
- Teams consolidating plans, risk registers, budgets and timesheets off separate spreadsheets
What we deliver
A configured portfolio with your plan, cost and risk model built in, not bolted on afterwards.
Installation and hardening
Deployment on your servers or VMs — PHP with MySQL or PostgreSQL, the stack your team most likely already runs.
Directory integration
LDAP or Active Directory authentication with project and role mapping.
Portfolio structure
Projects, programmes and portfolios arranged to match how your organisation actually governs and reports.
Planning and baselines
Work breakdown, milestones and dependencies, with baselines kept so progress is measured against the plan you committed to.
Risk and issue registers
Risks and issues as tracked records with owners, mitigation and review dates — not a spreadsheet nobody reopens.
Cost and resource control
Budgets, actual costs and workload per resource, so over-commitment shows up before it becomes a slipped date.
Reporting and handover
Steering-committee views built from live data, and training for the people who will run it after we leave.
On-premises versus cloud
Every criterion below is one your auditors will ask about. This is why we deploy inside your network by default.
| Criterion | On-premises, on your infrastructure | Public cloud / SaaS |
|---|---|---|
| Security | You control the firewall, the encryption keys, the access policy and the audit trail. | Shared infrastructure and a provider-defined security boundary. |
| Privacy | Data never leaves your network perimeter. | Data is stored and processed on third-party systems under their terms. |
| Autonomy | Full customisation, your upgrade schedule, no vendor lock-in. | Provider-driven roadmap and forced upgrade windows. |
| Integrity | You define backup, retention and recovery, and you test them. | You inherit the provider’s backup policy and their definition of acceptable loss. |
| Continuity | Service survives loss of internet connectivity; it runs on your intranet. | An outage or a commercial dispute at the provider becomes your outage. |
| Cost | Capital cost plus support; no per-seat escalation as headcount grows. | Per-user subscription that grows with your organisation. |
Project cost, resourcing and risk registers are commercially sensitive. Where they are stored is a question worth answering deliberately.
How it connects to the rest of your stack
Nothing we deploy is meant to stand alone. These are the joins we build as part of the same engagement.
- Governance — Where we tailor PRINCE2 Agile for you, stage boundaries, tolerances and management products map directly onto the plan, risk and issue records rather than sitting in a separate document.
- Service desk — Changes raised through the service desk can be promoted into planned, costed work with the original request preserved.
- Monitoring — Infrastructure incidents needing project work enter the same plan as everything else rather than being absorbed invisibly.
Engagement summary
Questions we’re usually asked
ProjeQtOr or ZenTao?
They sit at the same level and we will not pretend one is simply better. ProjeQtOr is stronger where the accountability is plan, cost, resource and risk — the questions a steering committee asks. ZenTao is stronger where the accountability is requirement-to-test evidence — the questions an auditor asks about a release. Which matters more to you is the first thing we establish, and some organisations run both.
What is paid, exactly?
The application is AGPL-3.0 in full — the publisher monetises hosting, support, training and optional plugins rather than holding features back. That is a cleaner arrangement than most, and we will still tell you at scoping if anything in your scope needs a paid plugin.
Under PRINCE2 governance
Where the accountability is what was committed, what it cost and what is exposed, ProjeQtOr is the better fit. It answers the questions a steering committee asks rather than the ones an auditor asks about a release.
| PRINCE2 | ProjeQtOr |
|---|---|
| Project Initiation Documentation | Document with versioned approver workflow |
| Business Case | Objectives, budget against actual cost |
| Project and Stage Plans | Work breakdown, milestones, Gantt and critical path |
| Work Packages | Activities assigned to a resource |
| Risk and Issue Registers | Risks, opportunities, issues and change requests |
| Progress control | Timesheets feeding the reporting engine |
Tolerance is the part that matters: plan, cost and workload are all measured against what was agreed. The full mapping, and where it falls short, is in Where each PRINCE2 management product lives.
How this compares with the other platforms we deploy, and which one fits which obligation, is on Choosing Between Our Platforms.