Maestro Mojo pricing

Free when you bring your own AI. Credits only apply when you use ours.

Credits exist to cap the models we pay for. They are not a meter on you driving your own AI tool through the tools to do your own work — that is the whole design, and it is why the list of things that cost anything is three items long.

01

One rule, and then the details

Read this and you can predict every number on the page.

Only operations that make Maestro's own AI do work cost anything. Everything else — filing, reading, moving, commenting, searching, deploying — is a database operation. It costs us nothing, so it costs you nothing.

02

What spending a credit looks like

Starting a build is the operation where an agent actually goes and thinks. It is also the only one in this session that costs anything.

Zed Session
you> Start the build for the tracing item
assistant> Build started — agents are planning it now.
Add request tracing to the gatewaybuilding
50 credits780 left · replenishes automatically
Filing the item, reading the board, checking the build and commenting on it were all free. The build itself is what costs.
03

What costs credits

Three operations. Each one of them puts a model to work on our bill.

Operation Credits Why it costs
start_build 50 An agent plans the work, writes the code, runs the tests and reviews it. That is a real agent run against a real model — the single most expensive thing Maestro does on your behalf.
file_request 5 Intake reads what you asked for, works out what kind of work it is, and routes it. One model pass before anything lands.
codegraph_index 10 Indexing a repository embeds every new or changed chunk of it — potentially thousands of embedding calls in one invocation. Re-indexing an unchanged repo is cheap for us and still costs the same flat 10.

Any tool that is not on this list costs 0. That is the default in the code, not a promise we maintain by hand.

04

Everything else is free

Not "free for now", and not a trial tier. These are database operations; metering them would cost more than running them.

Boards

Create, read, move, comment, archive, nest, milestone. Every board operation an agent or a person can make.

Reads of any kind

Your queue, an item's trail, a workspace's context, notifications, the digest — reading never costs.

Knowledge

Adding knowledge and searching it semantically. The embeddings behind a single call cost us a fraction of a cent.

Code graph queries

Search symbols, trace callers and callees, run impact analysis, read a file's graph. Only the initial indexing charges.

Sites & domains

Create a site, deploy it, roll it back, claim a subdomain, set DNS, mount a docs book. All free.

Workspace docs & skills

Docs, skills, files, members, forms and submissions — the whole workspace surface.

05

Where credits live

Workspace, not project

Charged to your key, not your board

Credits belong to the personal workspace your API key was issued against. A project's board never draws anything down — you can run as many projects as you like on one balance.

Replenishing

A rate limit, not a quota

Your balance replenishes automatically. Credits are there to stop runaway AI spend, not to ration how much work you get to do, so a quiet week is not credit you lose.

There are no paid tiers today and nothing to buy — there is no purchase path in the product at all. If that changes, this page changes with it.

06

Start with the free balance

Connect, file something real, watch it land on a board. None of that spends a credit.

Works with Claude Code · Claude Desktop · Cursor · Codex · Windsurf · Cline · Zed · any MCP client

Free when you bring your own AI — credits only apply when you use Maestro's AI