Conductor publishes four tiers as of August 2026: Free at 0 dollars, Pro at 50 dollars per month, Teams at 60 dollars per user per month, and custom Enterprise. Billing is monthly with no annual option shown, and Teams is invite-only rather than self-serve. Free is local-only but has no cap on parallel workspaces. Pro adds Conductor Cloud, multiplayer with up to five Pro collaborators, and the beta API. Teams adds unlimited collaborators, an admin portal, and centralized billing. Enterprise adds SAML single sign-on, SCIM, a data processing agreement, purchase-order billing, and support terms. No tier includes inference: Conductor bills no model usage, so the model subscription is a separate line item on every plan.
- Free is 0 dollars and is not concurrency-limited. Unlimited local workspaces; the paid axis is cloud, collaboration, and API.
- Pro is 50 dollars a month and unlocks Conductor Cloud, multiplayer for up to five Pro users, and the beta API.
- Teams is 60 dollars per user per month and is invite-only. The list price exists; the self-serve checkout does not.
- Single sign-on and SCIM are Enterprise only, and shipped in mid August 2026, so they are new.
- No tier includes model usage. Budget Conductor on top of Claude, ChatGPT, or Cursor, never instead of them.
- Two figures are unpublished: the cloud hours allowance on Pro, and any Teams seat minimum.
The four tiers
These figures are from conductor.build/pricing, read in August 2026. Prices are monthly; the page shows no annual toggle and no annual discount anywhere.
| Tier | Price | What it adds | How you buy it |
|---|---|---|---|
| Free | $0 | Unlimited parallel local workspaces on your Mac, all four harnesses, bring your own subscriptions and keys | Download |
| Pro | $50 / month | Conductor Cloud with a cloud workspace hours allowance, multiplayer, collaboration with up to five Pro users, the Conductor API | Self-serve |
| Teams | $60 / user / month | Live collaboration for teams of any size, admin portal, centralized billing | Invite-only, contact sales |
| Enterprise | Custom | Data processing agreement, purchase-order billing, SAML SSO, SCIM, custom security and privacy settings, SLA and dedicated support | Contact sales |
The bill Conductor does not send you
Conductor's harness documentation states it directly: Conductor does not bill or resell model usage, and harness usage is billed through the provider account or API key. Its pricing FAQ repeats the point for the cloud tier, confirming you bring your own subscriptions or keys there too. This is a deliberate product position, not an oversight, and it is the single most important thing to understand about the pricing.
Practically, it means the agent is paid for somewhere else. If you are signed into Claude Code with a Pro or Max subscription, Conductor uses that subscription. If you are signed in with an API key, Conductor uses the key and the usage lands on your Anthropic bill. The same holds for Codex against a ChatGPT plan or API key, for Cursor against a Cursor plan, and for OpenCode against whichever provider you configured.
| Setup | Conductor | Model plan | Monthly total |
|---|---|---|---|
| Conductor Free plus Claude Pro | $0 | $20 | $20 |
| Conductor Pro plus Claude Pro | $50 | $20 | $70 |
| Conductor Pro plus Claude Max 5x | $50 | $100 | $150 |
| Conductor Pro plus Claude Max 20x | $50 | $200 | $250 |
| Conductor Teams, per seat, plus Claude Max 5x | $60 | $100 | $160 per seat |
Two readings of that table are both correct. Fifty dollars is small next to two hundred, so the orchestrator looks cheap against heavy model spend. Fifty dollars is also two and a half times the entry Claude plan, so it looks expensive to a developer whose actual bottleneck was window management. Which reading applies depends entirely on whether cloud workspaces and multiplayer solve a problem you currently have. If you are sizing a whole team, the AI team cost calculator handles the seat arithmetic, and Claude Max pricing covers the larger half of the bill.
What the paid tiers actually unlock
It is worth being precise here, because comparison sites routinely get this backwards. Paying Conductor does not buy you more parallel agents. Parallelism is unlimited on the Free tier. The paid axis is where the work runs, who can see it, and what can drive it.
- Conductor Cloud. A workspace runs in a remote sandbox rather than on your Mac, so agents keep working after you close the laptop. This is the substantive upgrade and it has its own architecture, quotas, and privacy behavior, covered in Conductor Cloud.
- Multiplayer. Shared workspaces and chats with live presence, a follow mode, reassignment to a teammate, and shareable links. Pro caps collaboration at five Pro users; Teams removes the cap.
- The Conductor API. A beta HTTP API plus a hosted MCP server, so external systems can create workspaces and drive chats. This is what makes Conductor scriptable at all, since there is no installable CLI.
- Admin portal and centralized billing. Teams tier. One subscription for the organization and role management for its members.
- SAML SSO and SCIM. Enterprise only, and shipped in mid August 2026. If your evaluation predates that, re-check it: this is a genuinely new capability, not a long-standing one.
- Enterprise data privacy controls. An organization can force local-only operation by blocking new cloud workspaces and shared organizations.
What is missing from the ladder
For a team comparing Conductor against a workbench with governance features, these are the gaps that come up in procurement.
| Requirement | Conductor, August 2026 | Notes |
|---|---|---|
| Annual billing | Not shown on the pricing page | Monthly only in the published ladder |
| Free trial of a paid tier | Not advertised | No trial appears on the pricing page or FAQ |
| Teams seat minimum | Not stated | Teams is invite-only, so terms are likely negotiated |
| Audit log | Not documented | No mention in docs or changelog; ask before assuming |
| Spend caps | None, by construction | Conductor meters no usage, so there is nothing for it to cap |
| Self-hosted or bring-your-own-cloud | Not available yet | Conductor says it is building a self-hosted cloud offering |
| Windows or Linux seats | No build exists | Waitlist only, no announced date |
The spend cap line deserves a fair reading rather than a scoreline. Conductor has no spend controls because it sits outside the billing path entirely, which is a coherent design. But it does mean budget enforcement has to live somewhere else, in your provider console or in a tool that does sit in the path. If a weekly cap per member is a requirement rather than a preference, look at organization controls and model the shape first with the spend cap simulator.
Questions people ask
How much does Conductor cost?
Free is 0 dollars, Pro is 50 dollars per month, and Teams is 60 dollars per user per month, with a custom Enterprise tier. Those are the published list prices in August 2026, billed monthly. No tier includes model usage, so add your Claude, ChatGPT, or Cursor bill to any of them.
Does Conductor Pro include Claude credits?
No. Conductor resells no inference at any tier. Its harness documentation states that harness usage is billed through your own provider account or API key, and its pricing FAQ confirms the same applies to cloud workspaces. Pro is 50 dollars for orchestration only.
Is the Conductor free tier limited to a number of agents?
No, and this is the most commonly repeated error about Conductor. Parallel workspaces are unlimited on Free. What Free lacks is Conductor Cloud, multiplayer, and the API, so the constraint is where work runs and who can see it, not how much runs at once.
Can I buy Conductor Teams directly?
Not as of August 2026. Conductor's FAQ states that Team plans are invite-only and directs interested companies to a contact form. The 60 dollars per user figure is published, but the purchase is a sales conversation rather than a checkout.
Is there annual billing or a discount?
The pricing page shows monthly prices with no annual toggle and no billed-annually text. That is what is published; it does not rule out annual terms being available on an Enterprise contract, which is negotiated rather than listed.
Does Conductor have per-user spend caps?
No, and it could not have them in the usual sense: Conductor never sees a token bill, so there is no usage for it to limit. Caps have to be set in your provider console instead, or in a workbench that sits in the inference path and can enforce a weekly budget per member.
Sources
Every figure above was read from these pages on August 2026. Vendors reprice without notice; if you find a stale number, tell us.