Every project tool claims its scheduling is real. TruePPM's engine is a separate Apache-2.0 Python package — the same code the platform runs on, versioned in lockstep. No server, no database, no account. As far as we know, no other PPM tool, open or commercial, lets you audit its scheduling engine on its own.
Diff it against MS Project if you like. That is the point of shipping it separately — the claim is falsifiable, which is the only kind worth making about scheduling math.
Most tools force the call. TruePPM keeps one underlying model — tasks, dependencies, dates — and lets each team work the way it works. Plan a board, derive a schedule. Move a bar, the backlog updates. Same truth, two surfaces.
Cards and bars are the same task. Estimate in points, schedule in days — TruePPM keeps both in step.
Close a sprint and the schedule advances. Push a bar and the backlog reorders. No copy-paste status meetings.
Software runs the board, hardware runs the Gantt, the PMO reads the rollup. Nobody is forced off their method.
Single-point dates lie. Monte Carlo simulation samples thousands of possible runs across your estimates, dependencies, and risk ranges and hands you a distribution — so you commit to a date you're 80% likely to hit instead of a hope.
Across the commercial field that capability is licensed separately and operates on a schedule exported out of your scheduling tool: Deltek Acumen Risk, Barbecana Full Monte, Safran Risk, Oracle Primavera Risk Analysis. In open source it is simply absent — we are not aware of another OSS project-management platform that ships it at all.
TruePPM computes it in the same engine that computes the dates. No export step, no second license, no add-on tier.
A real Critical Path Method (CPM) engine computes the longest path, the slack (its formal name is float) on every task, and the knock-on effect of any change — in milliseconds, as you type. Slip a critical task and the whole network recomputes. Tasks with slack stay quiet.
Resource leveling — automatically resolving an over-allocation — is a different thing, and TruePPM does not do it yet. What it doesn't do →
Point any AI client that speaks MCP — Claude Desktop, Cursor, Zed — at your self-hosted instance and ask the live schedule real questions: the critical path, sprint status, or a what-if like "slip this task three days — when do we ship?" Every answer is computed server-side by the same CPM and Monte Carlo engine the UI uses — never a language model's guess, and it never leaves your box. That's one principle with four parts: an agent can compute an answer, cite its derivation, be refused when a change would break the plan, and reproduce any answer later — the same rules for a human and an agent, so the schedule an agent can read and act on is one it can't corrupt.
The read surface and the agent-action audit log land in the 0.4 beta; safe agent writes follow in 0.6. How grounding works →
Every task feeds its program — health, variance, and forecast aggregate automatically, so the program manager and the team read the same truth at different altitudes. Program rollup is part of the free, open-source core. Roll many programs into a governed portfolio with the Enterprise edition.
The core is Apache-2.0 and runs anywhere — your private cloud, your cluster, your laptop. Bring your own Postgres, point it at your own identity provider, keep your schedule data inside your perimeter. API-first: if it isn't in the API, it doesn't exist.
Single sign-on ships in the open core, at the 0.4 beta. OpenProject gates OIDC and SAML behind its Enterprise tier; Plane gates SSO behind its Commercial editions. Letting your own team log in with your own identity provider is not an enterprise feature — the enterprise line is identity governance (SAML, SCIM, LDAP sync), not the login screen.
Schedules don't live in a vacuum. TruePPM round-trips MS Project files, links commits to tasks, fires webhooks on state changes, and sends the digest your stakeholders actually read.
Import and export MS Project schedules — full round trip, in the UI or over the API. A personal, read-only Jira sync into My Work arrives with the 0.4 beta, so a team can adopt TruePPM without switching first.
Reference a task in a branch or PR and TruePPM moves the card, logs effort, and updates the schedule on merge.
Daily and weekly rollups per audience — the contributor sees their tasks, the executive sees variance and the forecast date.
Subscribe to any state change. Real-time webhooks (automated callbacks) drive your CI, status pages, and incident tooling.
Most tool sites make you find this out forty minutes into an evaluation. Here it is up front, so you can disqualify us in five. This list is maintained — every gap names the release it's planned for, or says plainly that it isn't.
The engine computes the schedule; it will not resolve an over-allocation for you. Allocation with over-allocation warnings lands in 0.5. If you need automatic leveling today, use P6 or MS Project. This is the largest gap between TruePPM and the traditional schedulers.
Start-no-earlier-than, and that's it. No must-finish-on, no deadlines. MS Project ships eight constraint types. If your schedules are contractual, TruePPM can't express them yet.
No rates, no budgets, no EVM. Resource costs and EV-lite (SPI/CPI) are planned for 0.8. If the first question your PMO asks is "what's the CPI?", we're not ready for you.
Roughly 1,000 tasks stays comfortable in the Schedule view — bounded by the browser, not the engine. Measured on documented hardware, published with what we didn't test. P6 handles two orders of magnitude more.
The web UI is responsive, but there's no installable app yet. A PWA with an offline shell lands in 0.5, native Android in 0.6, iOS at 1.0.
First release May 2026. The current line is alpha; 0.4 is the first beta. OpenProject has fifteen years and a support contract. What we offer against that is a 3–4 week cadence that has held, a public commit history, and this page.
The full maintained gap list → · Named comparisons, with citations →
Verify the engine, then decide whether to run the platform. Apache 2.0, no seat count, no feature flags, no telemetry — on your infrastructure, with your data.