MacroDream is where I build software the way modern teams actually work — open at the core, honest about what's commercial, and priced for value actually delivered.
Bloated platforms. Opaque pricing. Vendors who treat on-premise like a second-class deployment.
I started MacroDream to do it differently. The mission isn't tied to any single category. Wherever incumbents have grown complacent, extractive, or hostile to the way modern teams actually work, there's room to build something better.
The first projects set the tone — a Kanban platform built for the audit trails of customer-facing work, and a project portfolio platform built for the regulated, air-gapped environments the legacy P3M vendors quietly abandoned.
More is coming across infrastructure, delivery, and the connective tissue in between.
Apache 2.0 community tier with full feature parity for the core workflow — genuinely useful, not a nag-screen funnel.
Pricing pages with prices on them. The paid tier is for things teams actually pay for — SSO, audit, support — not artificial gatekeeping.
Air-gapped, regulated, sovereign. Where the incumbents quietly retreated, I treat as the primary deployment, not the exception.
Usage-based where it makes sense. Per-seat where it makes sense. Never a $40-a-seat tax to access the feature you already had.
Swimlanes, real-time collaboration, dwell-time analytics, and a full audit trail of every card movement. The first MacroDream project to ship — and the source of the governance system now used across the portfolio.
Built for support, success & ops teams running customer-facing work
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.
The 0.4 beta adds what makes it a first-class citizen of an AI-assisted stack: a read-only MCP server, so an agent can 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. 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.
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.
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 or 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 (0.4) is targeted for September 2026 — a two-week window, Aug 31 to Sep 14, after multiple rounds of hardening. Leaving beta is a quality judgment, not a date, so the number of beta tags is open-ended.
Built for teams who need real scheduling math on their own infrastructureTruePPM's scheduling core as a standalone Apache 2.0 Python library — all four dependency types, calendar-aware lag, multi-calendar composition, cycle detection that names the offending path, critical path, float, and Monte Carlo with per-task sensitivity. No server, no database, just the math the platform runs on, versioned in lockstep with it. A Rust/petgraph twin is held in CI conformance against it.
Publishing it separately is a positioning decision, not a packaging convenience. Every scheduling tool claims its math is real; this one can be checked in sixty seconds by someone who does not trust us, and diffed against MS Project. A falsifiable claim is the only kind worth making about scheduling.
Built for anyone who needs real CPM in Python — and anyone auditing TruePPM's claimsStack-agnostic project governance template for teams using GitLab and Claude Code. CI pipeline scaffolding, git hooks, changelog workflow, Claude Code agents and skills, and MR conventions — without opinionating on your programming language or framework. The one idea underneath it: a gate's only value is that its green is evidence, so every gate has to prove it still bites.
Built for teams using GitLab and Claude Code
I've spent a career inside enterprise software — shipping products, navigating acquisitions, watching the cycle of incumbent capture repeat itself. MacroDream is the studio where I build the alternatives, on my own terms.
Open-source by default. Audit trail as feature, not afterthought. Pricing pages with prices on them. And a quiet bet that small inputs and deliberate focus can still produce outsized outcomes.
Partnership, pilot deployments, regulated-environment requirements, or simply a thesis worth comparing notes on — the inbox is open.