Reserved Mac minis
The machines run only your Pods. Capacity is set in the contract and does not compete with other tenants.
Macs reserved for you.
A pool of Apple silicon Mac minis that only your Pods run on, in the EU or the US. Adds SSO/SAML, an exportable audit log, invoice billing and a private link to your git host to everything in Team.
From $3,000 a month. The price covers the Macs reserved for you, the regions you choose and a named engineer; the proposal lists it line by line.
Team or Enterprise?
Choose Enterprise when you need Macs reserved for your organization, SSO/SAML, a private git-host link, residency written into the contract or invoice billing. Compare Team's capacity and billing below.
| Team | Enterprise | |
|---|---|---|
| Hardware | Shared pool of dedicated Apple silicon | Mac minis reserved for your organization |
| Pods at a time | 10 | Set in the contract |
| Region | EU or US, chosen per environment | EU or US, with a residency commitment in the contract |
| Sign-in | Email link | SSO/SAML through your identity provider |
| Audit log | In the dashboard | In the dashboard and exportable |
| Network | Outbound only, to your model provider, git host and registries | The same, plus a private link to a self-hosted git server |
| Billing | $399 a month plus extra Pod-hours, by card through Paddle | From $3,000 a month, by invoice |
| Support | A named engineer in a shared Slack channel, response times in the contract |
The table scrolls sideways; the first column stays in place.
What the pool gives you
All plans use the same Pod isolation model: Pods make outbound connections only and accept no SSH; the Security page in the docs has the detail. Enterprise adds the hardware and the commitments.
Residency you can cite
Pods, logs and screenshots are processed and stored in the region you chose. The contract says so, not just the dashboard.
A private link to your git host
Connects the pool to a self-hosted GitHub or GitLab, so repositories need no public endpoint.
A named engineer
One person who knows your setup, in a shared Slack channel, with response times written into the contract.
Questions from procurement
How is the final price set?
By the number of Macs reserved and the region. The proposal lists the Macs, the regions, SSO, the audit log, invoice billing and support as separate lines.
Can we use our own git server?
Yes. A private network link connects the pool to your self-hosted GitHub or GitLab, so your git server does not need a public endpoint.
What does the contract commit to?
Pool size, monthly billing, data-processing terms, the region, and response times for the named engineer.
Do you sign a data-processing agreement?
Yes. It names the processors listed on the privacy page in the footer and the region you chose.
Can we start on Team first?
Yes. You can use Team while the pool is provisioned; environments move over without changing how developers start sessions.
How a rollout goes
Four steps. You keep working on Pro or Team while the pool is prepared.
- 1
Scoping call
Team size, regions, git host, identity provider and what your security review needs. You get a written proposal afterwards.
- 2
Contract
Pool size, region, data-processing terms, response times and the monthly invoice, agreed before any Mac is reserved.
- 3
Provisioning
Macs are reserved and imaged, SSO is connected, and the private network is set up with your network team.
- 4
Pilot and handover
One team runs its real work on the pool first. You get usage by developer and a review of what queued before the rest move over.
Talk to us about a pool.
Email your team size, regions and git host to discuss a reserved pool.