fshy

Home / Compute

Cirun

cirun.io/pricing/CI runnercompute/cirunJSONcomparereport an errorprovider JSON

Free allowance
Quoted from the Open Source plan: 'Always free for open source', USD 0 forever, with 'Install cirun on unlimited public repositories', 'Unlimited runners', 'ARM-based runners', 'GPU runners' and 'All supported cloud providers'.
Verdict
paidno free allowance; listed for its price
Cost
no price stated
Identity
cardcard required, no phone
Binding limit
request-rateThe cloud account fails first: Cirun gives away the scheduler and the runner definition, and every vCPU-hour it orchestrates is billed by AWS, GCP, Hetzner or Vast.ai to the caller, so what the free plan removes is a management fee and...
Evidence
documented3 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-11-22checked 2026-10-22 (live); stale on 2026-11-22
Free tierQuoted from the Open Source plan: 'Always free for open source', USD 0 forever, with 'Install cirun on unlimited public repositories', 'Unlimited runners', 'ARM-based runners', 'GPU runners' and 'All supported cloud providers'. Quoted from the docs introduction: 'Run jobs on your own cloud - bring AWS, GCP, Azure, Hetzner, DigitalOcean, Oracle, OpenStack, or Vast.ai credentials' and 'Pay your cloud, not the runner provider'.
unit unlimited; metered on wall-clock; free-orchestration-only
Pricenone stated
Limits
  • request-rate (binding) The cloud account fails first: Cirun gives away the scheduler and the runner definition, and every vCPU-hour it orchestrates is billed by AWS, GCP, Hetzner or Vast.ai to the caller, so what the free plan removes is a management fee and not a compute cost. source
Identitycard no payment instrument to Cirun: the Open Source plan is 'Always free for open source' at USD 0. The card sits one layer down, because the runners execute in a cloud account the caller already holds: the setup docs require 'a Service Account with Compute Engine Admin Permissions' and a downloaded JSON key pair, i.e. an existing billed AWS, GCP, Azure, Hetzner, DigitalOcean, Oracle, OpenStack or Vast.ai identity. The authorisation amount is not stated, and whether those clouds accept debit or prepaid is not stated
Egressnot stated
Interfaceunknown inferred from the tooling the provider documents; not probed
Toolingnot stated
Composes withThe composition it enables is real and is the reason to keep the row: Cirun plus an Oracle Always Free Ampere instance would put that instance's cores behind a GitHub Actions label, so a free cloud can be addressed as a CI runner. The constraint is that the free tier it composes with must already exist.
Reliabilityno reliability event recorded
NotesVerdict is paid-only rather than qualifies, and the distinction matters: 'free for open source' here means free to schedule, and a reader who takes it for free GPU capacity will find a Vast.ai invoice. It is a strong chain member and a zero on its own. The docs FAQ and getting-started paths both 404, so the pricing page and the docs index are the evidence; docs.cirun.io returned 200 for both.
Parsed numbers
  • has-free-tier 0
Evidence 3
datesourcewhat it proved
2026-10-22cirun.io/pricing/'Always free for open source', USD 0 forever, unlimited public repositories, unlimited runners, ARM-based runners, GPU runners, all supported cloud providers
2026-10-22docs.cirun.io/'Run jobs on your own cloud - bring AWS, GCP, Azure, Hetzner, DigitalOcean, Oracle, OpenStack, or Vast.ai credentials'; 'Pay your cloud, not the runner provider'; 'runners are cheaper than GitHub-hosted'
2026-10-22docs.cirun.io/cloud/gcpthe setup requires 'a Service Account with Compute Engine Admin Permissions' and a downloaded JSON key pair, i.e. an existing billed cloud identity
More fields 1
facets{"class": "ci-runner-capacity","free_tier_kind": "free-orchestration-only","shape": {"vcpu": null,"ram_gib": null,"gpu_class": null,"gpu_count": 0}}
Unknown values 7
  • 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
  • reliability note: nothing of this kind was observed
  • retention stated: the field does not apply to this kind of offer
  • tooling: a source was read and is silent on this field