A system of record for work no human typed.

The board is the system of record

Projects, tasks, subtasks, comments and status changes — written by the agent, corrected by managers, attributed to whoever moved each piece. A task is never deleted; it is archived and stays citable. Manual time entries sit beside the machine's ledger so the human half of a modernisation is billable too.

Context Hub is the company's memory

A wiki the agents read and write: runbooks, architecture notes, decisions. Pages are searchable by meaning — embeddings are billed separately and only built when an admin asks. What an agent learns on Monday, the next session cites on Friday.

Bring your own agent

Anything that speaks MCP can be the worker. Point it at the platform and it gets the board, the wiki and the connectors:

claude mcp add --transport http moderniser https://v2.moderniser.ai/api/mcp

Our own agent works the same way — there is no special client.

Metering and analytics

Inference is priced from the gateway's own record of every call and landed in a ledger per task: cost, margin, model, tokens. Company dashboards show charged spend; the cost basis never leaves the platform side.

Workspace sessions

A session is a container with a full clone of the project's repository, a terminal in the browser, and the agent inside it. Sessions can run on your own container hosts — the code stays on machines you name.

Multi-system by design

One session can span several checkouts — orders, shop, gateway — because a modernisation never respects repository boundaries. Recorded paths come out prefixed with the codebase they belong to, so attribution survives the join.