| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Artifact and container registries | Developer platform | 0% | 23 of 89 | 0% | 17 | accepted challenger |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 1 | 0 | 1 |
| GPT-5.4 mini | 0 | 1 | 1 | 0 | 2 |
| Gemini 3.5 Flash | 0 | 4 | 0 | 0 | 4 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.1 Fast | 0 | 3 | 1 | 0 | 4 |
| Mistral Small | 0 | 0 | 0 | 0 | 0 |
| DeepSeek V4 Flash | 0 | 0 | 0 | 0 | 0 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 1 | 0 | 0 | 1 |
| Kimi K2 | 0 | 1 | 0 | 0 | 1 |
| GLM 4.7 FlashX | 0 | 0 | 1 | 0 | 1 |
| MiniMax M2.5 | 0 | 1 | 0 | 0 | 1 |
| GPT-6 Luna | 0 | 1 | 0 | 0 | 1 |
| Muse Glimmer 30B | 0 | 0 | 1 | 0 | 1 |
Verbatim evidence the judge attached to positive labels.
“their native registries (AWS CodeArtifact, Google Artifact Registry, or Azure Artifacts) are highly practical options” Gemini 3.5 Flash · Artifact registries · direct prompt · alternative
“Best if: You are 100% committed to a single cloud provider and want deep integration with their IAM, KMS, and private networking.” Gemini 3.5 Flash · Artifact registries · scale prompt · alternative
“Pay-per-use (~$14/month for small team est.) | AWS users | Bills on storage/requests; no self-host” Grok 4.1 Fast · Artifact registries · budget prompt · alternative
“AWS CodeArtifact | AWS shops | Cheap, multi-format, IAM integration. | AWS-only, less UI.” Grok 4.1 Fast · Artifact registries · scale prompt · alternative
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.
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 47 of the 54 answers that named AWS CodeArtifact and are not a share of its labels.
194 of the 194 domain citations in answers naming AWS CodeArtifact came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read October 5, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What AWS CodeArtifact's own pages state, read October 5, 2026: aws.amazon.com/codeartifact, aws.amazon.com/codeartifact/sla, aws.amazon.com/codeartifact/pricing, aws.amazon.com/codeartifact/features, aws.amazon.com/de/codeartifact/faq. A claimed page can correct any of them.
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 CodeArtifact'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 CodeArtifact, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for AWS CodeArtifact by email, built from the raw record of the edition. It shows: