Cirrus CI
- Free allowance
- The allowance was real and is now gone.
- Verdict
- deadthe offer or the service no longer exists
- Cost
- no price stated
- Identity
- emailno card, no phone
- Binding limit
- request-rateThe 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.
- Evidence
- documented14 sources; a first-party page was read and the sentence quoted
- Freshness
- checked 2026-11-03checked 2026-11-03 (live)
| 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 |
| Limits |
|
| Identity | email not published |
| Egress | not stated |
| Interface | unknown inferred from the tooling the provider documents; not probed |
| Tooling | not stated |
| Composes with | None. |
| Reliability | on 2026-10-30 cirrus-ci.org did not resolve and cirrus-ci.com failed the TLS handshake, after the shutdown the vendor announced for June 1, 2026 |
| Notes | Duplicate of ci-cd-runners/cirrus-ci. Cirrus CI has shut down; before then the free allowance was 50 compute credits a month, equal to 10,000 CPU-minutes for Linux tasks or 500 minutes for macOS tasks. Cirrus Runners is a separate paid product of the same vendor, recorded as compute/cirrus-runners. |
| Parsed numbers |
|
Evidence 14
| 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/ | not published |
| 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/ | not published |
| 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' |
| 2026-10-22 | cirrus-ci.org/blog/2023/07/17/limiting-free-usage-of-cirrus- | read 2026-10-22: the origin refused or dropped the request. This read confirms the shutdown; it is not the shutdown notice itself. |
| 2026-10-30 | cirruslabs.org/ | the vendor shut Cirrus CI down effective 1 June 2026 |
| 2026-10-30 | probe: https://cirrus-ci.org/faq/ | on 2026-10-30 a GET to cirrus-ci.org/faq/ failed at DNS resolution |
| 2026-10-30 | probe: https://cirrus-ci.com/ | on 2026-10-30 a GET to cirrus-ci.com failed the TLS handshake |
| 2026-11-03 | web.archive.org/web/20260419203508/https://cirrus-ci.org/faq | before the shutdown the free usage of Cirrus CI was capped at 50 compute credits a month, equal to 10,000 Linux CPU-minutes or 500 macOS minutes (archived copy of 2026-04-19) |
| 2026-11-03 | cirruslabs.org/ | the vendor shut Cirrus CI down effective 1 June 2026 |
More fields 2
| facets | {"class": "ci-runner-capacity","free_tier_kind": "monthly-credit-cap","shape": {"vcpu": 2,"ram_gib": 4,"gpu_class": null,"gpu_count": 0}} |
|---|---|
| death | {"on": "2026-06-01","cause": "dead-service"} |
Unknown values 6
- egress metered: egress metering was not published
- egress terms: a source was read and is silent on this field
- interface: the access interface was not established
- per object cap stated: the field does not apply to this kind of offer
- retention stated: the field does not apply to this kind of offer
- tooling: a source was read and is silent on this field