Why developers leave CircleCI: GitHub Actions closed the feature gap, the integration tax (separate vendor, separate UI, separate auth) wasn't worth it for most teams, and CircleCI's credit pricing model felt less intuitive than per-minute. Teams already on GitHub increasingly migrated through 2024-2025.
GitHub Actions wins on default-by-locality — lives next to the code. Larger runners (released 2024) closed the performance gap. Marketplace covers 90% of common workflows. For most teams already on GitHub the integration friction savings outweigh CircleCI's sharper test-parallelism primitives.
Buildkite for teams whose CircleCI choice was actually about the test parallelism — Buildkite's BYO runners enable unlimited parallelism on your hardware. Pipeline-as-code with dynamic generation handles complex monorepos. Higher ops investment than CircleCI managed.
For most cases yes. Larger runners + matrix builds + third-party split-test actions cover most parallelism patterns. CircleCI's native split-by-timing is still slightly more polished but the gap is smaller than it was in 2022.
Most reviewers report 2-4 weeks. Workflow YAML translation is mechanical (config.yml → workflows/*.yml). Reusable workflows mitigate scale issues. The harder work is rewriting custom Orbs as composite actions or reusable workflows.
CircleCI's M1 macOS runners are price-competitive for iOS shops. GitHub macOS runners cost more. For pure iOS pipelines CircleCI stays competitive. For teams with mixed iOS + backend pipelines, consolidating on GitHub Actions usually wins on integration savings.
