For the project managers and program managers who've outgrown the legacy P3M stack.
Scheduling-first, not agile-first — critical path, float, and Monte Carlo risk bands
are computed by a real engine, not guessed by a chatbot — but not
agile-hostile either: Kanban, sprints, velocity, and retros layer on top of the
schedule, not beside it. MS Project import/export means switching costs an
afternoon, not a quarter.
The Apache 2.0 community tier is a complete P3M practice for a self-hosted team: the
full CPM engine, Monte Carlo simulation, projects grouped into programs with their
own backlogs, mobile offline, real-time collaboration, time tracking, baselines,
single sign-on against your own identity provider, and a production Helm chart for
Kubernetes. An MCP server lets AI agents read those computed schedules as
first-class facts, and contributors can mirror their own assigned items from an
external issue tracker, read-only, into one view.
When an organization outgrows a single team, the Enterprise tier adds the governance
layer on top: portfolio dashboards, cross-program resource leveling, org identity
governance (SAML, SCIM, directory sync), and approval workflows.
Next: the first beta (0.4) launches July 2026, after multiple
rounds of hardening, extending the MCP server to what-if scheduling — an
agent proposes a scenario, the engine recomputes it, and the answer comes back
computed, not guessed.
Built for PMs & program managers who've outgrown the legacy P3M stack