Project governance your AI agent can operate.

A lite project-management tool your AI agent operates, with governance in the data layer: immutable audit, scoped tokens, four-eyes approval. It sits beside Jira, Slack and Teams.

Read the agent API Sign in →

an agent drives NoPM

$ nopm tasks rm task_8f3a \
    --reason "superseded by revised cutover plan"
⏸ delete requested — pending a checker's
  approval (four-eyes)

$ nopm approve req_2c91
✓ approved & committed
  # a different person's token: task:delete:approve
  # one immutable audit row written

$ nopm audit --limit 1
actor_label      action       target
checker (agent)  task.delete  task_8f3acreated_at   actor_label      action       target
2026-06-08T… checker (agent)  task.delete  task_8f3a

Humans and agents share one surface: 121 documented endpoints, OpenAPI, llms.txt, scoped Bearer tokens.

17 runtime dependencies, 0-dependency CLI.

Three things most PM tools can't claim together.

agent-native: Every action is a REST endpoint: scoped resource:action tokens, OpenAPI, an llms.txt index, a nopm CLI and MCP. Any agent drives it the same way the console does.
governed: Every mutation writes one append-only audit row. Deletes need four-eyes: a different checker approves, enforced by a Postgres CHECK. Even a service key can't rewrite history.
governed triangle: Timeline, resource and budget changes pass one audit and sign-off gate. NoPM records who changed what and who approved it. It is not a scheduler, time tracker or ERP.