CI/CD & Deployment Automation lists 64 providers. GitHub Actions is first at 82.8 and GitLab second at 82.6, which is right. Salesforce is third at 82.3, ahead of Harness at 79.3. CircleCI, Jenkins, Buildkite and LaunchDarkly are not on the page at all, even though all are in the catalog. This is a defect in how we build the page, and it’s a useful one to see.
Why it happens
Use-case membership comes from each provider’s free-text use_cases field, matched against aliases. It does not look at tags. We counted 164 scored providers tagged CI/CD, continuous integration, continuous delivery or continuous deployment. Only 12 of them are on the page. Of the 152 left out, 145 have no use_cases entries at all, so the build has nothing to match. The other 52 page members got there through a sentence in that field.
| Left out, tagged for CI/CD | Kin Score | Agent Readiness |
|---|---|---|
| LaunchDarkly | 80.2 | 54.1 |
| Azure DevOps | 74.4 | 31.9 |
| CircleCI | 72.6 | 49.6 |
| Buildkite | 71.8 | 44.1 |
| CloudBees | 71.4 | 36.8 |
| Octopus Deploy | 67.2 | 20.6 |
| Akuity | 66.0 | 25.0 |
| Jenkins | 40.7 | 23.0 |
LaunchDarkly would place fourth on the page, above Harness. CircleCI’s agent score is higher than GitLab’s, and it’s missing while GitLab is second. The page’s definition even names feature flags.
Who gets in instead
Salesforce earned its place with one entry, “DevOps And CI/CD Automation,” about its metadata deployment APIs. That is true, but it is not what someone looking for CI wants. Palo Alto Networks arrives through “SASE Deployment Automation” and “DevSecOps Pipeline Integration,” and it brings 468 APIs, 53% of the 883 on the page. Autodesk Maya is on the page because “VFX Pipeline Integration” contains the alias pipeline integration. Backblaze qualifies by storing build artifacts. Slack qualifies by sending the notifications.
One member isn’t a company. Evals, with 20 APIs, describes itself as a landscape catalog, and it is here because of an entry about wiring evals into CI. It should not be counted as a market participant on any page.
The observation
The page’s strong numbers, a median of 58.5 with 17 exemplars, come from what’s on it. 21 of the 64 are Amazon or AWS records, and the purpose-built tools that did make it are spread out: GitHub Actions 82.8, GitLab 82.6, Bitbucket 64.2, TeamCity 52.1. A free-text field rewards whoever wrote the most sentences. A provider that describes itself as a CI server may not bother to write “CI” in a use-case list, because it’s the whole product.
The fix is ours: admit providers by tag as well as by use case, exclude catalog records, and tighten the pipeline integration alias.
Takeaway
Use this page for discovery, but not as a ranking of CI/CD vendors until it’s fixed. If you’re choosing a pipeline tool, also read CircleCI, Buildkite and the other left-out records directly. The live page is at CI/CD & Deployment Automation.