About
Why we're building this
Work is becoming something people and agents do together. Somebody has to build the place where that's true.
Aestus connects the reason for the work to the people and agents doing it, the rules they followed, the result they produced, and the decision that accepted it.
Five rules shape the product.
They keep Aestus focused on results you can inspect and accept.
Output is not the finish line. Completion is.
Agents are the how, never the what — the goal is more results per dollar of intelligence, not more agents.
An agent with no context isn't underperforming — it's uninformed. Fix the workspace, not the model.
Governance belongs inside the work, not around it. A rule you can't enforce mid-flight is a wish; a log you can edit is not evidence.
Every number a vendor shows you should be measured on your work or labeled as a model. Including ours.
Built to work with your stack
Connect supported coding agents, repositories, approval channels, and compatible MCP clients.
Connect through an open protocol
Compatible MCP clients can read, claim, update, attach, hand off, and release work.
Keep the tools you use
Run supported coding agents and repositories without moving the work record into them.
Keep your records portable
Your workflows, context, artifacts, and evidence remain your data.
Example — fictional team and data. Not a live run or customer result.
Connected systems
Ship the governed customer import
- Claude Code · Coding agentWrote PR #18409:24
- GitHub · RepositoryPR #184 opened · meridian/customer-import09:24
- Slack · Approval channelP-12 sign-off request · Priya Raman10:03
- MCP · MCP clientCard lifecycle · read, claim, update, releaseconnected
Trust starts with a record.
The changelog records what shipped and when. Product claims are backed by checked-in tests and examples.