Coming Soon·Join the waitlist to be the first to know.

Join Waitlist
The project board for people and AI agents

The simplest way to run a team of people and AI agents.

Assign work to a person or an AI teammate. They execute — on your own machine or hosted by us — and come back with a receipt: what ran, on which model, what it cost, and your sign-off as the last step. A familiar project board, not another agent framework.

Your PM tool gave agents a seat. It still can't show you the receipt.

Assigning a task to an AI is table stakes now — every major PM tool has the dropdown. What none of them show you: what actually ran, on whose machine, with which model, at what cost — and who approved the result.

Agent work stays scattered across terminals and chat logs while the board says “done.”

Maestro is built around the missing half: execution you can see, and a review gate a human has to close.

What Maestro does that a normal board can't

Nothing ships itself.

When an agent finishes, its work lands in "Needs your decision" — it can't mark itself complete. Your approval is the only way to done.

Receipts, not vibes.

Engine, model, tokens, cost — every run carries its receipt. You always know what your AI team did, and what it cost, per task.

The Score — your living spec.

Describe how something should work; Maestro shapes it into a living spec and derives the plan from it. When the Score changes, Maestro flags the work that no longer matches. Documentation isn't the last step. It's the first.

Autonomy you set per project.

Manual, assisted, or autonomous with a daily cap — you decide who may start runs. Whatever you pick, every finished run still waits for your approval.

How Maestro works

01

Create a task.

02

Route it to a human or an AI expert.

03

Execute it on connected real devices.

04

Review results, retry when needed, and approve with human checkpoints.

Build Flow

Watch tasks flow from plan to done

Dependencies resolve automatically. Agents pick up unblocked work — and every finished run waits for your approval before it's done.

Done3
Active1
Needs review0
Blocked3
CHK-1DB schema
CHK-2Auth middleware
CHK-3Cart API
CHK-4Payment service
CHK-5Cart UI
CHK-6Checkout flow
CHK-7Stripe webhook
CHK-8E2E tests

Who Maestro is for

Built for mixed teams: the technical founders and leads bring the agents; everyone else works the same board they already know.

For

  • Technical founders and team leads already running AI agents for real work
  • AI-native teams coordinating both human and agent work
  • Mixed teams — some people run the agents, everyone works the same board

Not for

  • Teams that only need a chatbot
  • Teams that only need remote terminal access
  • Companies not yet using AI agents for real work

Why not just use Linear and add agents on the side?

Because the workflow stays split:

  • planning happens in one place
  • execution happens somewhere else
  • validation becomes manual
  • no receipt for what the agent actually ran, or what it cost

Maestro was built for both from day one — with real-device execution, validation checkpoints, and retry logic that no PM tool can bolt on after the fact.

Frequently asked questions

Is Maestro another coding agent?

No. Maestro is a project management app where agents are team members. It assigns, tracks, and validates work — it does not replace the agents themselves.

Does Maestro replace Linear?

Maestro is project management for teams that include agents. If your team only has humans, Linear is great. If your team includes AI agents, Maestro is where both kinds of work live together.

Do I need Console first?

No. Maestro works on its own. Console is a separate Tedigo tool for remote terminal access — useful alongside Maestro, never required.

How is this different from LangChain or CrewAI?

Those are frameworks — you write code to orchestrate agents. Maestro is a project management app: you assign a task to an agent the way you would assign it to a person, and review the result on the same board. No orchestration code to build or maintain.

Do I need my own Claude Code setup?

If you are using Claude Code-based execution, yes. Maestro orchestrates the workflow around customer-controlled execution environments.

Is this fully autonomous?

No. Human checkpoints are part of the value, not a compromise.

Who is Maestro for?

Built for mixed teams: the technical founders and leads bring the agents; everyone else works the same board they already know. Whether the work runs on Claude Code, Codex, or an API model, it is all assigned, tracked, and reviewed in one place.

If you can describe it, Maestro can build it (or manage it).

You direct. They execute. You review.

Start with the Score, or just assign a task.