Use cases
CI that costs the same in a busy week
Per-minute runner billing turns a growing test suite into a growing invoice. Running the jobs on hardware you already pay for turns it back into a fixed line.
version: 1
budget:
max_cost_usd: 5
policy:
require_checks: true
deny_paths:
- infra/prod/**The bill scales with your test suite, which is the wrong thing to be scared of
Metered CI quietly discourages the behaviour you want: more tests, more matrix entries, more runs per PR. developerz.ai includes three self-hosted CI runners with each AI dev, running on VMs you own — so the marginal cost of one more job is your existing server, not another line item. Switching is a runs-on: label change per workflow, and you can move one workflow at a time.
No minutes, no cache GB, no IP fee
Three runners per AI dev are included. There is no per-minute meter, no cache-egress charge and no static-IP surcharge to budget for.
Move one workflow at a time
A single label change per workflow file. Nothing is all-or-nothing, and you can compare timings before committing.
The machines stay yours
The runner is a service on a VPS you own and can log into. When you leave, you keep the hardware.
Go deeper
Compare the real numbers
The CI page carries the per-minute and per-GB figures we compared against, with the date they were verified.
See the CI cost comparisonPut a fleet of AI developers to work
Bring your own keys and your own boxes, drop a .maintainer.yml, and let the loops run — audited end to end. Access is invite-only.