$ ~/cicdcalculator
# Independent CI/CD-cost research, read by platform and DevOps teams.Sponsor this site →
Reference / Trust surface

How we source CI/CD pricing figures

Each provider's data on this site is taken from that provider's own published source. This page describes the source per provider, the refresh discipline, and what we do not publish.

Sources, by provider

  • GitHub: github.com/pricing GitHub Actions per-minute rates and OS multipliers (Linux 1x, Windows 2x, macOS 10x for hosted runners) are taken from github.com/pricing and the per-OS minute schedule on docs.github.com.
  • GitLab: gitlab.com/pricing GitLab CI shared-runner minutes per tier, plus the over-tier per-minute rate, are taken from gitlab.com/pricing and the shared-runners documentation.
  • CircleCI: circleci.com/pricing CircleCI credit-based pricing, class-multipliers for resource_class (small / medium / large / xlarge / 2xlarge), and the dollar-per-credit conversion are taken from circleci.com/pricing.
  • Buildkite: buildkite.com/pricing Buildkite per-seat pricing, the per-vCPU-minute rates for hosted agents, plus the self-hosted vs hosted differential, are taken from buildkite.com/pricing.
  • Vercel: vercel.com/pricing Vercel build-duration pricing and the included minutes per Pro / Enterprise tier are taken from vercel.com/pricing.
  • Other providers. Travis CI, Jenkins (self-hosted cost model), AWS CodeBuild, Google Cloud Build and Azure Pipelines are sourced from their respective published pricing pages.

What we deliberately do not publish

  • Vendor-private enterprise pricing. Large customers negotiate custom rates with each provider. We do not publish customer-named pricing.
  • Self-hosted runner total-cost-of-ownership. Self-hosted runner economics involve infrastructure cost that depends entirely on customer cloud setup. We describe the trade-off qualitatively but do not publish a single TCO number.
  • Personal pipeline data. Calculators run entirely in your browser. Your build-minute / OS / concurrency inputs are not transmitted, logged, or stored.

Update cadence

Site values update only when the underlying reality changes. Triggers:

  • GitHub announces a change to Actions per-minute rates or OS multipliers
  • Material pricing change at any tracked CI provider
  • New CI provider with publicly-disclosed pricing reaches material market share
  • OS-multiplier or resource-class structure change

Cosmetic date bumps are not made.

Vendor verification

Some vendor pages carry a "Confirmed with vendor" note and a date. It means the vendor reviewed the figures on that page against their own rate card and confirmed them accurate as of that date. The protocol behind it:

  • The confirmation covers factual accuracy only. Framing, comparisons and conclusions stay ours.
  • Corrections are accepted only against the vendor's own published source, which we then cite. A vendor's claims about a competitor carry no weight and are re-derived from the competitor's published rates before anything changes.
  • Vendors have no publication veto. The page publishes either way. Only the note is theirs to give, withhold or withdraw.
  • Verification never rewrites independently sourced figures. It confirms and dates them.
  • Verification is free and cannot be bought. A paid note would be an advert, so there is no paid note.

The same protocol applies to every vendor on the site.

Editorial position

This site is operated by Digital Signet, an independent AI-development studio. Digital Signet does not sell CI/CD products, does not run a build-pipeline consultancy, does not act as a reseller, and does not accept paid placements from any CI/CD provider. See /about for the operator and the wider network.

Editorial direction is set by Digital Signet's editor. Drafts are produced via Digital Signet's autonomous AI development methodology and reviewed against the editorial framework before publication.

Contact

For methodology questions, corrections, or scenarios that don't fit cleanly: [email protected].