IT AI Index

Index › Vendors › AWS CodePipeline · September 2026 Edition

AWS · 1 category · Named, not ranked

AWS CodePipeline

10Judge labels

0First choices

4Negative labels

7 of 12Models named it

1Category

September 2026 Edition. Every number here is derived from the raw labels under vendor table vv2026-09.2, every buyer segment counted.

Standing

2 labels, too few to rank

A product needs 10 labels in a category before a share or quadrant is stated. AWS CodePipeline was named 2 times in CI/CD, where GitHub Actions led with 65%. The labels and the evidence are below, counted exactly.

By buyer segmentRead the same way at every buyer size.

Small business38 of 55

under the label threshold

Mid-market35 of 45

under the label threshold

Enterprise15 of 41

under the label threshold

In ci/cd · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading

Standing by category

Every category where a model named AWS CodePipeline for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.

Category	Function	Share	Rank	Negative rate	Labels	Quadrant
CI/CD platforms	Developer platform	0%	35 of 45	50%	2	under 10 labels · led by GitHub Actions at 65%

Movement

This is the first edition on this tier, so no move can be computed for AWS CodePipeline yet. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated AWS CodePipeline across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.

Model	Mention	Negative	Labels
Claude Haiku 4.5	0	0	0
GPT-5.4 mini	1	0	1
Gemini 3.5 Flash	0	1	1
Perplexity Sonar	0	0	0
Grok 4.1 Fast	0	0	0
Mistral Small	0	0	0
DeepSeek V4 Flash	0	0	0
Llama 4 Maverick	0	0	0
Qwen 3.7 Flash	0	0	0
Kimi K2	0	0	0
GLM 4.7 FlashX	0	0	0
MiniMax M2.5	0	0	0

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.

FramingLabels by classFirst choices

Direct1 labelNone

Paraphrase2 labelsNone

Comparative2 labelsNone

Budget-constrained0 labelsNone

Scale-constrained0 labelsNone

Negative5 labelsNone

First choiceAlternativeMentionNegative10 labels in all, every segment counted; 0 of the 0 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

No positive label carried a quote.

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

“Approach with awareness of the golden handcuffs.” Gemini 3.5 Flash · CI/CD · negative prompt · soft negative

Named alongside

The products named in the same answers as AWS CodePipeline, over the 10 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and AWS CodePipeline was named but was not.

ProductSame answerTook the first choice insteadHead to head

GitHub Actions10 of 105Not in the top three

GitLab CI/CD10 of 102Not in the top three

Jenkins8 of 100Not in the top three

CircleCI7 of 100Not in the top three

Azure DevOps6 of 100Not in the top three

Travis CI5 of 100Not in the top three

Atlassian Bamboo4 of 100Not in the top three

Azure Pipelines3 of 100Not in the top three

JetBrains TeamCity3 of 100Not in the top three

AWS CodeBuild2 of 100Not in the top three

A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named AWS CodePipeline. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 6 of the 10 answers that named AWS CodePipeline and are not a share of its labels.

Domains cited

blog.jetbrains.com3

toolradar.com3

atlassian.com2

checkthat.ai2

deployhq.com2

devopsplatforms.com2

docs.aws.amazon.com2

docs.github.com2

g2.com2

kuberns.com2

Twenty-two of the twenty-two domain citations in answers naming AWS CodePipeline came from somebody else's page.

Pages cited

blog.jetbrains.com/teamcity/2026/03/best-ci-tools3

atlassian.com/continuous-delivery/continuous-integration/tools2

checkthat.ai/answers/what-are-the-best-ci-cd-tools2

deployhq.com/blog/best-ci-cd-software-top-10-tools-to-know-in-20252

devopsplatforms.com/buying-guides/best-ci-cd-platforms2

g2.com/categories/continuous-delivery-tools/small-business2

kuberns.com/blogs/best-cicd-tools2

learn.g2.com/best-continuous-delivery-tools2

Pages are listed as the models cited them.

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when AWS CodePipeline's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as AWS CodePipeline, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at awscodepipeline.com is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.