Most project tools store dates. TruePPM computes them. At the center is a real
Critical Path Method engine with Monte Carlo risk analysis — and the reason to
believe that claim is that the engine ships as its own
library. pip install trueppm-scheduler and check the math against
MS Project in sixty seconds: no server, no account, no trust required. No other PPM
tool, open or commercial, makes its scheduling engine auditable in isolation.
Around that engine sits a platform where the Kanban card and the Gantt bar are the
same object — not two records kept in sync. Close a sprint and the master
schedule reforecasts from measured velocity. MS Project has no agile surface; Jira
has no critical path; the open-source field has neither Monte Carlo nor a separable
engine. That gap is the thesis.
The Apache 2.0 community tier is a complete P3M practice for a self-hosted team —
full CPM engine, Monte Carlo, programs with their own backlogs, offline-first sync,
real-time collaboration, time tracking, baselines, and a production Helm chart. No
seat count, no feature flags, no SSO tax. MS Project import/export means switching
costs an afternoon, not a quarter.
0.4, the first beta, adds what makes it a first-class citizen of an AI-assisted
stack: trueppm-mcp,
a read-only MCP server published alongside the platform. Point Claude Desktop or any
MCP client at your own instance with a personal, expiring, read-only token, and
nineteen tools read those computed schedules as first-class facts rather than
guessing at them — including a non-mutating what-if, where an agent
proposes a scenario, the engine recomputes it, and the answer comes back computed
with the real plan untouched. Unlike the engine, it is not a standalone tool: it is a
thin adapter over the TruePPM API, and it can see nothing its token's owner could not
already see.
Alongside it: single sign-on against your own identity provider, read-only share
links so a schedule can travel beyond its own instance, and a read-only mirror of a
contributor's own assigned Jira items into one view.
Every user of the open tier already gets Cosign-signed, Trivy-scanned release images
with a CycloneDX SBOM, the response timeline in the public
security policy,
and — once 1.0 ships — security backports for the two most recent minors.
The Enterprise tier is being built around putting commitments like those under
contract: a response SLA an organization can hold me to, a supported release line
that runs past the open two-minor window, and an evidence pack for its auditors. None
of that exists yet; the terms, and the price, will be published before the tier is
sold. Org identity governance (SAML, SCIM, directory sync), portfolio dashboards, and
approval workflows are planned for the same tier after 1.0 — useful, but not
the reason to pay.
And what it is not, stated plainly because a product that only lists its
wins isn't being evaluated honestly: there is no resource leveling, one constraint
type where MS Project has eight, no cost model before 0.5 and no earned value before
0.8, and a measured
ceiling of roughly a thousand tasks in the schedule view. It is not a Primavera P6
replacement and does not claim to be. The
gap list is
published and maintained.
Next: the first beta was tagged September 15, 2026 (latest: 0.4.0-beta.6, September 30),
and the 0.4
line hardens under further
beta tags — leaving beta is a quality judgment, not a date. 0.5 is targeted
for Jan 4–18, 2027, counted from the close of the beta period: resource
allocation that warns about an over-allocation before you save it, a project status
update built from numbers the engine already computes, a labor cost model with a P80
cost beside the P80 date, an installable PWA, and MCP plan mode, where an agent's
proposed change comes back with a verdict and its impact and nothing commits.
To see it before installing anything, there is a
hosted read-only demo
on the bundled sample program. It is a live instance, not a screenshot tour, and
nothing you do there is saved.
Built for teams who need real scheduling math on their own infrastructure 