The TruePPM core is open source and self-hostable. Bring your own Postgres, point it at your own identity provider, and keep every schedule, estimate and forecast inside your perimeter. One command to deploy.
The engine that matters — scheduling, forecasting, the agile↔waterfall bridge, the API — is Apache-2.0, and so is everything one team needs to run a program. Managed hosting and organization-wide governance are the only paid layers. If it isn't in the API, it doesn't exist.
The critical-path (CPM) and Monte Carlo engine that powers TruePPM ships as a separate Apache-2.0 Python package. Drop it into your own tooling — no platform required.
Late alpha · Apache-2.0 · trueppm-scheduler
Docker Compose for a laptop or a single VM, a production Helm 3 chart for Kubernetes — whatever your stack, there's a paved path.
Compose brings its own Postgres 16 and Valkey; migrations and admin bootstrap run themselves. Prefer your own Postgres? Point DATABASE_URL at it.
One command seeds sample projects with six persona logins — sign in as the Scrum Master, the PM, or the executive and see your role's view first.
Point it at your own OIDC/OAuth identity provider and invite your team. You're scheduling in minutes.
Everything the app can do, the API can do — schedules, dependencies, forecasts, webhooks. A typed OpenAPI schema (so you can generate a client in any language), predictable resources, and a webhook for every state change so you can wire TruePPM into CI, status pages and incident tooling.
Self-host and no schedule data ever leaves your network. Encrypt at rest with your own keys.
Basic OIDC/OAuth sign-in through your own identity provider is in the open core. SAML, SCIM provisioning, and directory-driven deprovisioning come with Enterprise.
An operational activity log ships in the core — who moved what, when, and why the date shifted. A tamper-evident, immutable audit trail comes with Enterprise.
Clone the repo, run one command, and you're forecasting in minutes — on your terms.