Stop guessing whether the project is on track.

The problem

Teams still guess whether delivery is on track. Status lives in Kanban boards, Slack threads, and standup meetings — none of which can answer "are we on track?" from evidence. Most project tools are adapters on top of GitHub, Jira, and Slack, which means the plan and the delivery evidence live in different systems that drift apart.

The product

PAWMOS is native planning above GitHub, not another Kanban board: projects, features, milestones, and sprints are planned directly in the product, and a deterministic Health engine reads delivery evidence — open critical issues, stale pull requests, CI status, resource over-allocation, and budget signals — to produce a cited verdict instead of a guess.

Available today

A real NestJS backend with tested domain logic runs behind the product, not a UI shell over mock data:

• A pure, deterministic Health-computation function — no I/O, unit-tested — that assembles an evidence snapshot and returns a verdict, short-circuiting to a "Planning" state before there's anything to evaluate rather than faking a score.
• Real GitHub webhook security — HMAC-SHA256 signature verification using constant-time comparison, with deliberately tolerant error handling so GitHub doesn't disable the integration on an edge case.
• GitHub sync logic linking issues to work items and pull requests to features, self-documented in code as intentionally simple MVP linking rules rather than an overclaimed AI matcher.
• A tested resource-planning domain — allocation, capacity, costing, billing, and overtime — each with its own dedicated test suite, not just UI forms.
• Native planning across projects, features, milestones, sprints, and a dependency graph, plus multi-tenant organizations, RBAC guards, an audit-log interceptor, and platform-admin impersonation.

Upcoming features

Planned next, in the order the product's own architecture notes prioritize them:

• A GitHub App with bulk repository import, replacing today's manual connector-plus-webhook setup.
• Health progress bars, forecasting, and a Releases view.
• Portfolio, risk, decision-log, and strategy modules — currently reserved as empty schema for future stability, not yet functioning features.
• SSO and broader collaboration (comments, notifications).

Who it's for

• Founders and CTOs who need a real answer to "are we on track?"
• Engineering managers and PMO leads tired of status meetings substituting for evidence.
• Product managers who want delivery health tied to GitHub activity, not self-reported updates.

Platform and stage

Next.js 14 web app, NestJS 10 API, Supabase Postgres, Turborepo monorepo. Stage: Private Early Access — the planning core, Health engine, and GitHub evidence sync are real and tested; broader collaboration and portfolio-level modules are the roadmap.