Pricing
Free where you run it. Paid where we run it.
Conductor Cloud does not supply Macs — you bring your own fleet either way. That one fact removes the entire model the incumbents use, and it is why the price here is per project rather than per minute.
Self-host
Free
forever
Every feature. Your infrastructure, your Macs, your database, your keys.
- Unlimited projects and runners
- Full audit trail, hash-chained per organisation
- SSO, passkeys and role-based access
- Row-level security forced on every tenant table
- Upgrade when you choose to
Cloud Starter
$—
per project / month
We run the control plane. You still run the Macs, because nobody else can.
- Up to 3 connected runners
- 90 days of run and log retention
- Everything in Self-host
- Email support
Cloud Team
$—
per project / month
For a fleet, and for more than one team shipping through it.
- Up to 12 connected runners
- 1 year of retention
- Priority scheduling support
- Shared audiences and cross-project reporting
Enterprise
Talk to us
Procurement, a security review, and a number that survives both.
- Unlimited runners
- Custom retention
- Private security-advisory feed
- A named contact
Nothing in the security posture is tier-gated.
Not the audit trail, not SSO, not row-level security, not fork safety, not credential scoping — including on free self-host. Two reasons, and both of them are ours rather than yours: a release pipeline with a downgraded security posture is not a product worth shipping, and charging for SSO is precisely the move that would make every other sentence on this site less believable.
What we refuse to charge for
Three meters the industry uses that would be dishonest here, and why.
- Build minutes
- We do not supply the compute. Metering it would mean earning more when our own scheduler is slower, which is a business we decline to be in.
- Concurrency
- Your concurrency is how many slots your Macs have. Charging for it would be charging you for hardware you already bought.
- Seats
- Charging per developer taxes exactly the behaviour this product exists to create. A release pipeline that fewer people can see is a worse release pipeline.
What is left is what actually costs us something and maps to what you get: a project is an onboarding, a credential set, a store-account relationship and a reconcile loop; a connected runner is a persistent mTLS stream and log fan-out. Retention differentiates the tiers rather than metering them — and the audit chain never truncates, because a hash chain with a hole in it is not a hash chain.
Self-host, supported
For the team that will never put its control plane in somebody else's cloud.
An annual support contract against your own deployment: a private security-advisory feed ahead of public disclosure, upgrade review, and help when a restore drill goes sideways at the wrong moment. No feature gate — the software is the same software.
It exists because the alternative is pretending self-hosting is a lesser choice in order to sell Cloud, and it is not. It is the right choice for a lot of teams, and those teams should still have something to buy.