About
A board for work that is no longer done only by people.
PhaseBoard is a project management tool built on one observation: a growing share of real work is now done by AI agents, and none of the tools that track work were designed for that.
What it is for
The plan and the agent should be the same system.
When an agent does a piece of work, the record of it usually lives in a transcript somewhere — not in the plan. The board says the task is still open, someone has to read a chat log to find out otherwise, and the two drift apart until the plan is fiction.
PhaseBoard closes that gap by making the board something an agent can actually use. It has a documented REST API and an MCP server, so an agent picks up a task, moves it through the pipeline, comments on it and leaves its work in the history under its own name — while a person watches the same board move.
That is the whole product. Projects, phases, a six-stage pipeline, specs, comments, links, attachments, an activity trail, project documents, a design-review loop, and two ways to drive all of it without a browser.
The thesis
An agent is a principal, not an integration.
Most tools treat automation as a bot account bolted to the side: one shared identity, all the permissions, and a webhook. That is fine until an agent does something you need to explain.
- An agent gets its own service account, not a shared human login — so the board shows who did what, and 'who' can be a machine.
- Its token carries an explicit set of scopes and, optionally, a list of projects it may touch. A token is narrower than the principal behind it.
- Every write lands in the same activity trail a person's write does, attributed to the agent and to the token it used.
- The rules are enforced on the server for both, so an agent driving the API cannot reach further than a person driving the interface.
How it is built
Boring infrastructure, on purpose.
- Self-hosted. One instance, one operator, data in files on a server you can point at.
- Version history is a git repository, so every change to the board has a commit behind it and nothing is quietly rewritten.
- A REST API and an MCP server generated from one route registry, so the two surfaces cannot drift apart.
- No third-party analytics and no external requests on these public pages — the content policy that says so is a header, not a habit.
Who is behind it
One developer.
PhaseBoard is built and operated by Umair Mahmood. There is no company behind it, no team, no investors and no support desk — it started as the backlog tool for its author’s own agent-driven projects, and it is still used that way every day.
That is worth knowing before you rely on it. It means the product is shaped by someone who uses it, that a bug report reaches the person who can fix it, and equally that there is no rota, no guaranteed response time and no service-level agreement. Access is granted by hand today; there is no self-serve signup.
The board is free to use. If a paid tier arrives it will be the AI layer on top of the board, and it will be described before it is charged for.
- Self-hosted
- Private preview
- No self-serve signup
Where to go from here.
The pricing page explains what is free and what will not be. The privacy policy describes what this instance actually stores, in the same amount of detail.