Limits
A concurrency limit counts jobs of one installation. The monthly cap counts
settled charges and open holds this UTC month; the console’s card shows spend
this month against the cap.
Pricing
Rates are per minute of each runner class and billed per second. See CI pricing for the runner classes, their rates and worked examples; the live rates are in the sandbox console under Billing → Rates. The Mac’s owner earns 90% of each charge. A job holds funds when it starts and settles to its billable time at the rate in effect when it started; the rest of the hold is released. The Runs page shows each job’s charge (held, settled or released, with the reason), and Billing shows the rate, hold, billable seconds and cost.Failed and lost jobs
A job that runs to its own end is billed for its time, whether it passes or fails: a failing test is the job’s own outcome. A job lost on Darkbloom’s side is not charged. If its Mac drops off the network or its VM is lost, the whole hold is released. Two cases are billed anyway:- A job that had already finished by itself, and that GitHub had concluded, before the loss is billed for the time it used.
- A job that reports success only after its Mac is lost is billed only if GitHub concluded it a success. If GitHub failed it instead, the charge is released and the job runs again, so you pay for it once.
Spend controls
- Concurrent jobs and the monthly cap are set per installation with Edit limits in the console. Limits apply to every repository in the installation; new jobs are not admitted past a limit, and running jobs finish.
- Disconnect stops new jobs and revokes your billing consent. Jobs already running finish and are charged.
- To stop routing without disconnecting, set
DARKBLOOM_ROUTINGto anything buton, or remove the route job.

