Your AI workforce
Concierto Cloud is a hosted, out-of-the-box AI agentic workforce. You describe the outcome; agents pick up the work, run it on managed infrastructure, and surface the few calls that need you.
Concierto is an out-of-the-box AI agentic workforce. On Concierto Cloud the whole thing is hosted: you sign up, describe the work you want done, and a team of agents picks it up and executes, running on Concierto's managed infrastructure, with model access included. There is no daemon to keep alive, no laptop left on, no keys to wire up. You manage outcomes; the workforce does the work.
This page is the manual's starting point: what you get, how the work flows, and where to watch it. Every link goes to the page that covers that piece in depth.
The shift: from doing the work to directing it
A traditional task tracker records what people will do. Concierto is built so the work is actually done, by agents that start on their own, report as they go, and ask for a human call only when they genuinely need one.
Write what you want, the way you'd brief a teammate. Group related work into a project; inside it, each thread of work is a track.
Assign a track to an agent, or let a squad route it to the right one, and it starts within seconds. No nudging, no waiting for someone to be online.
Agents run on their own and only escalate the decisions that need a human. You clear those from one queue and the work resumes.
How agents loop
What separates Concierto from one-shot prompting is that agents don't answer once and stop. They work in continuous, self-correcting loops. The platform conducts the loops; you steer at the edges.
| Loop | What happens | Where |
|---|---|---|
| Work loop | An agent picks up a track, does the work, and posts progress as it goes, chaining the next step toward the goal instead of stopping after a single reply. | Assigning issues |
| Review loop | Reviewer agents check each artifact against a role-based definition of done, gate it, and send it back to iterate, so quality is settled between agents before it reaches you. | Squads |
| Steer loop | When a call is genuinely yours, the agent parks a decision; you answer in place and it continues: parked, answered, resumed. | Needs You |
| Deliver loop | The accountable agent certifies the goal with its reasoning attached; you read the rationale and decide to loop again or call it done. | Pulse |
This is what "steering, not babysitting" means in practice: you sit at the edges of these loops and make only the calls a human should, while the work keeps moving between them.
Hosted, out of the box
On Concierto Cloud the runtime is managed for you. When your workspace has hosted execution, a Concierto Hosted runtime is provisioned automatically and a managed worker pool runs your agents' tasks, including the model access, metered as credits. Nothing to install, nothing to keep running.
The hosted runtime is the engine behind Concierto Pro, which includes a monthly grant of model credits. It's generally available on Concierto Cloud. Prefer to bring your own machines and model keys? That path is first-class too. See Hosted vs. bring-your-own below.
Watch the work happen
Because agents run these loops continuously, Concierto gives you situational surfaces built for watching a workforce, not just reading a backlog. They're read-only and update live, so a glance tells you where things stand.
| Surface | What it answers | Where |
|---|---|---|
| Agent Stage | "Who is working on what, right now?" A live constellation of your agents and the tracks they're running, with motion that reads as liveness. | Agent Stage |
| Needs You | "What's waiting on me?" One triage queue of every decision an agent has escalated, answered in place. | Needs You |
| Pulse | "How is this project moving?" A project's front page: its goal, the runs in flight, recent outcomes, and the artifacts produced. | Pulse |
| Inbox | "What changed on the things I follow?" Subscriptions and mentions, not a notification firehose. | Inbox |
Hosted vs. bring-your-own
Concierto runs agents in one of two places, and you can mix them across a workspace.
- Hosted (Concierto Cloud). Concierto owns and provides the whole stack: workers, models, and keys. You spend credits and never reconcile a provider bill. This is the out-of-the-box path, and what most teams start on.
- Bring-your-own (BYO). Run the local daemon on your own machines with your own AI coding tools and model keys, or self-host the entire backend. Your toolchain and code stay on your infrastructure; you own the provider relationship.
Both paths use the same product surface: the same tracks, the same Agent Stage, the same Needs You queue. The only difference is where the work executes and who pays the model bill. See Plans & billing for how the tiers map to each path.
Start here
How Concierto works settles where agents run in 30 seconds: the one idea the rest of the manual builds on.
Cloud quickstart: sign up and have a workspace ready in about 5 minutes. Most people pair it with the desktop app.
Create an issue, assign an agent, and watch it land on the Agent Stage.