Cirrus CI

cirruslabs.org · Compute · 1 record · JSON

Cirrus CI Compute

deademailno cardDrequest-rate

cirruslabs.org/ · CI runner · compute/cirrus-ci · JSON · compare

Free tier	The allowance was real and is now gone. Quoted from the Cirrus Labs announcement dated 7 April 2026: 'Cirrus CI will shut down effective Monday, June 1, 2026.' Quoted from the docs before the shutdown: free for OSS up to 'a cap of 50 compute credits a month', equal to '10,000 CPU-minutes for Linux tasks or 500 minutes for macOS tasks which always use 4 CPUs', with per-platform concurrency of 16 CPUs Linux, 16 CPUs Arm Linux, 8 CPUs Windows, 8 CPUs FreeBSD and 4 CPUs with 1 VM on macOS, and a single task capped at 8 CPUs on Linux. Cutoff 'for a job that has a full runtime' was 2 hours per task. unit hours; metered on wall-clock; monthly-credit-cap
Price	none stated
Per-object cap	not applicable
Retention	not applicable
Egress	not stated
Identity	email not published
Limits	request-rate The service itself failed first: the shutdown date is 1 June 2026 and today is 2026-10-22, so the binding constraint is that the provider no longer exists and the allowance is zero, whatever the pages still cached in search indexes say. source The service itself failed first: the shutdown date is 1 June 2026 and today is 2026-10-22, so the binding constraint is that the provider no longer exists and the allowance is zero, whatever the pages still cached in search indexes say.
Binding	request-rate The service itself failed first: the shutdown date is 1 June 2026 and today is 2026-10-22, so the binding constraint is that the provider no longer exists and the allowance is zero, whatever the pages still cached in search indexes say.
Interface	unknown inferred from the tooling the provider documents; not probed
Tooling	not stated
Composes with	None. This is the row that stops the next session from spending a wave on it.
Reliability	no reliability event recorded
Notes	A correction to the corpus's own dossier, not to batch 1: dossier/ci-cd-runners/cirrus-ci.json records the 50-credit allowance as live, sourced from cirrus-ci.org/faq, and that page now returns 530. The one lesson worth carrying: the 530 that every fetch path returned was the target's real state, not a broker fault, and the exit-code table's rule that a 4 establishes nothing about the target is what kept this open long enough to find the announcement. Scipy's inability to get an email about the date is the reliability note.
Evidence rung	documented
Checked	2026-10-22 (live); stale on 2026-11-21

Evidence (9)

date	source	what it proved
2026-10-22	cirruslabs.org/	announcement dated April 7th 2026: 'We are no longer accepting new customers for Cirrus Runners but will continue supporting the service for existing customers through their existing contract periods. Cirrus CI will shut down effective Monday, June 1, 2026.'
2026-10-22	cirrus-ci.org/	the site itself returns HTTP 530 through every broker route (read, fetch, crawl, archive), which is consistent with a decommissioned origin and is the evidence of death
2026-10-22	raw.githubusercontent.com/cirruslabs/cirrus-ci-docs/master/d	'an upper monthly limit on free usage equal to 50 compute credits (which is equal to 10,000 CPU-minutes for Linux tasks or 500 minutes for macOS tasks which always use 4 CPUs)'; concurrency 16 CPUs Linux, 16 Arm, 8 Windows, 8 FreeBSD, 4 macOS 1 VM; 'a single task can't request more than 8 CPUs'
2026-10-22	raw.githubusercontent.com/cirruslabs/cirrus-ci-docs/master/d	'1000 minutes of 1 virtual CPU for Linux platform for 3 compute credits'; '2 CPU Linux task takes 5 minutes? Pay 3 cents'
2026-10-22	raw.githubusercontent.com/cirruslabs/cirrus-ci-docs/master/d	'By default, a container is given 2 CPUs and 4 GB of memory'; 'Containers on Cirrus Cloud Cluster can use maximum 8.0 CPUs and up to 32 GB of memory', with memory tied to CPUs at 4 GB per CPU
2026-10-22	github.com/scipy/scipy/issues/24990	reported consequence: scipy's GPU runner job stopped working at the end of April 2026, and the project recorded that it had no email announcement of the timing
2026-10-22	cirruslabs.org/	first-party announcement: 'Cirrus Labs to join OpenAI', part of the Agent Infrastructure team [re-read 2026-10-22]
2026-10-22	github.com/scipy/scipy/issues/24990	quoted vendor statement: 'We are no longer accepting new customers for Cirrus Runners but will continue supporting the service for existing customers'; 'Cirrus CI is shutting down on June 1, 2026' [re-read 2026-10-22]
2026-10-22	cirrus-ci.org/blog/2023/07/17/limiting-free-usage-of-cirrus-	re-read 2026-10-22: the origin refused or dropped the request (broker exit 4). This is the check that confirms the shutdown recorded here, not the notice itself

More fields (1)

{
 "wave2": {
  "class": "ci-runner-capacity",
  "free_tier_kind": "monthly-credit-cap",
  "shape": {
   "vcpu": 2,
   "ram_gib": 4,
   "gpu_class": null,
   "gpu_count": 0
  }
 }
}

Unknown or withheld values (10)

$.egress.metered egress-unknown
$.egress.terms not-stated
$.identity_cost.detail process
$.interface interface-unknown
$.per_object_cap.notes process
$.per_object_cap.stated not-applicable
$.reliability_note none-observed
$.retention.notes process
$.retention.stated not-applicable
$.tooling not-stated