Alternatives to CircleCI

BuildPulse

BuildPulse suits engineering teams that want to monitor flaky tests, coverage, and CI activity across repositories.

Captain

Captain suits development teams that want to detect flaky tests, retry or quarantine failures, and distribute test files across parallel jobs.

Cypress

Cypress suits developers testing web applications with code, and teams that want to record and analyze CI test runs.

HyperExecute

It suits teams that want to run existing Selenium, Playwright or Cypress suites from CI using YAML, without maintaining a grid or rewriting test code.

Qualflare

Qualflare suits software teams managing manual and automated test results across supported frameworks and CI/CD workflows.

Buildkite

Buildkite suits teams that need CI/CD workflows dispatched to hosted or self-managed agents.

TeamCity

TeamCity suits software teams that need automated build and test pipelines with options to host on-premises or use a cloud plan.

Hawzu is aimed at QA and engineering teams wanting a system of record for manual testing, automation, or both.

Mergify

Mergify suits engineering and platform teams managing shared branches, monorepos, or long and costly CI pipelines.

FlakyWatch

FlakyWatch suits development teams using GitHub Actions that want classification, cost visibility, and issue workflows for unstable tests.

Testery

Testery suits teams coordinating automated test suites with CI/CD, especially those that need parallel runs, test artifacts, or deployment gates.

Tesbo is intended for QA engineers and QA managers focused on test design, coverage, and release evidence.

Flakiness.io

It suits development teams using GitHub or GitLab and the listed test runners.

It suits Python teams dealing with unreliable test suites, especially those using pytest and GitHub Actions.