Customer stories.
Teams that moved their GitHub Actions to RunsOn, in their own numbers: what CI cost before and after, how long builds took, and how they switched over.
- 3.3 → 1.5 min typical PR check
How Coveo halved its PR check times with RunsOn
Coveo's Dev Tooling team on replacing its in-house GitHub Actions runner orchestrator with RunsOn, in its own words.
- ~6 s runner start on a warm instance
- ~500 h fewer hours of PR checks every month
- 100,000+ workflow runs a month
- $5.7k CI cost in September, from $18.2k in August
Pydantic: a CI bill two-thirds lower, with five times the pull requests
AI agents pushed Pydantic's Logfire repository from 365 to 2,032 merged PRs a month. On RunsOn, CI cost $5,700 in September, down from $18,200 in August.
- 365 → 2,032 PRs merged in 30 days, a year apart
- +31% runner minutes, August to September
- 20,659 main workflow runs in August
- −75% monthly CI cost
Alan: off CircleCI and onto GitHub Actions, with a CI bill 75% lower
Alan moved its monorepo CI from CircleCI to GitHub Actions on RunsOn, in its own AWS account. CI costs fell 75%; PR checks went from 15 to under 10 minutes.
- 15 → <10 min PR checks
- 6% → 4% failure rate on main
- a few weeks to migrate every job
- ~$563 → ~$136 monthly CI compute Wikando
Wikando: ~$563 to ~$136 in CI compute, builds 23 to 15 minutes
Wikando, the company behind FundraisingBox, moved off GitHub-hosted runners to RunsOn in its own AWS account: CI compute down ~75%, main CI 23 to 15 minutes.
- 23 → 15 min main repository CI
- 20 → 5 min heavy analysis on 16 threads