AI Indexes
IT AI Index
Index › Products › CloudRepo · October 2026 Edition
1 category · Named, not ranked

CloudRepo

17Judge labels
2First choices
1Negative labels
9 / 14Models named it
1Category
October 2026 Edition. Every number here is derived from the raw labels under vendor table v2026-10.8, every buyer segment counted.
Standing
3 labels, too few to rank
A product needs 10 labels in a category before a share or quadrant is stated. CloudRepo was named 3 times in Artifact registries, where JFrog Artifactory led with 14%. The labels and the evidence are below, counted exactly.
By buyer segmentRead the same way at every buyer size.
In artifact registries · 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 CloudRepo 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.
CategoryFunctionShareRankNegative rateLabelsQuadrantSince September 2026
Artifact and container registriesDeveloper platform0%27 of 890%3under 10 labels · led by JFrog Artifactory at 14%

Movement

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

By model

How each model treated CloudRepo across every prompt where it was named for a mid-market B2B company. Fourteen models, six prompts per category.
ShowHide
ModelFirst choiceAlternativeMentionNegativeLabels
Claude Haiku 4.500000
GPT-5.4 mini00000
Gemini 3.5 Flash00000
Perplexity Sonar00101
Grok 4.1 Fast00000
Mistral Small00000
DeepSeek V4 Flash00000
Llama 4 Maverick00000
Qwen 3.7 Flash00000
Kimi K200000
GLM 4.7 FlashX01001
MiniMax M2.500000
GPT-6 Luna00000
Muse Glimmer 30B01001

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
Direct4 labels1
Paraphrase0 labelsNone
Comparative0 labelsNone
Budget-constrained12 labels1
Scale-constrained0 labelsNone
Negative1 labelNone
First choiceAlternativeMentionNegative17 labels in all, every segment counted; 2 of the 2 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.

“Best Cloud Option (If you cannot self-host) ... CloudRepo offers a generous free tier.” GLM 4.7 FlashX · Artifact registries · budget prompt · alternative
“CloudRepo $199/month flat, predictable pricing” Muse Glimmer 30B · Artifact registries · direct prompt · alternative

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.

No model argued against it.

Named alongside

The products named in the same answers as CloudRepo, over the 17 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and CloudRepo was named but was not.
ShowHide
ProductSame answerTook the first choice insteadHead to head
JFrog Artifactory11 of 172Not among the top eight
Sonatype Nexus Repository6 of 176Not among the top eight
GitHub Packages6 of 171Not among the top eight
AWS CodeArtifact5 of 171Not among the top eight
Cloudsmith5 of 170Not among the top eight
Harbor4 of 170Not among the top eight
Sonatype Nexus Repository OSS3 of 171Not among the top eight
Google Artifact Registry3 of 170Not among the top eight
Verdaccio2 of 170Not among the top eight
AWS ECR1 of 171Not among the top eight
A head-to-head page exists where both products are among a category's top eight. 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 CloudRepo. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 17 of the 17 answers that named CloudRepo and are not a share of its labels.

Domains cited

cloudrepo.ioYour site17
itechguides.com13
sonatype.com10
thectoclub.com9
jfrog.com8
zipdo.co8
gitnux.org5
harness.io5
imaginarycloud.com5
safeguard.sh5

Sixty-eight of the eighty-five domain citations in answers naming CloudRepo came from somebody else's page.

Pages cited

Pages are listed as the models cited them.

Search and answers

cloudrepo.io is not in Google's top ten for any of the category's searches. In the answers, CloudRepo takes 0% of first choices and JFrog Artifactory takes 14%.
ShowHide

In search

Google, US estimates
Position for “artifact repository”
–
not in the top ten
Position for “best artifact repository”
–
not in the top ten
Searches for its name, Google
20 a month (“cloudrepo”)
AI search demand for its name, est.
0 a month
Organic visits to its site
about 707 a month
Searches its site ranks for
267 · 8 in the top three
Sites linking to it
277
Paid Google search
No ads found in the estimate; that does not mean it runs none
Ads on Google
None found in Google's ad transparency records for the US

In answers

This edition
Share of first choices
0%
rank 27 of 89 in artifact registries
Segment leader
14%
JFrog Artifactory
First choices
2 across its categories
Named in
17 answers
Its own site cited
in 17 of the answers that named it

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.

What it publishes

ShowHide
Addresses on cloudrepo.io
249
subdomains included
Content
32
counted in the table below
Documentation
66
Product · Integration
0 · 0
KindPagesLast 90 days2025-11 to 2026-10LatestCategories named
Blog1912026-09-08Artifact registries
Comparison1002026-01-14
Glossary or explainer302026-01-15
How it is countedHide how it is counted

Every page cloudrepo.io exposes, subdomains included. Kind is read from the address and title. The last 90 days, the latest date and the twelve months count pages by when they were published, from the site's feeds, a date in the address, or the page's own publication date, read from up to a hundred of its most recently changed pages; a page that says only when it last changed is counted in its kind but not in when, so the recent counts are a floor, and a kind none of whose pages gives a publication date reads undated. Read October 5, 2026.

Follow CloudRepo

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.

The company

CloudRepo is its own company.
ShowHide

In its own words

Stated by the vendor, not checked
Positioning
the predictable-pricing alternative to JFrog Artifactory
For
engineering teams
Price stated
Starter $199 /month; Team $499 /month; Business $799 /month; Scale $1,199 /month cloudrepo.io
Starting price
199 cloudrepo.io
Free plan or trial
Start your 14-day free trial. No card. cloudrepo.io
Certifications
SOC 2 Certified VendorsAES-256 EncryptionUS Data ResidencyGDPR ReadySOC 2ISO 27001
Hosting
AWS US-West (N. California)US data centersUnited States
Customers named
DreevTwelve Oaks SoftwareKraneware
Not stated on the pages read
Integrations

What CloudRepo's own pages state, read October 5, 2026: cloudrepo.io, cloudrepo.io/pricing, cloudrepo.io/trust, cloudrepo.io/integrations. A claimed page can correct any of 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 CloudRepo'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 CloudRepo, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

What a new claim receivesHide what a new claim receives

A new claim receives the current edition's vendor brief for CloudRepo by email, built from the raw record of the edition. It shows:

  • where CloudRepo is named, by buyer and by framing, and which cells hold its first choices;
  • the claims the models make when they name it, ranked, with the strongest and the weakest quoted;
  • its vocabulary against the segment leader's, and the pages the models cited;
  • who was chosen in the answers that did not name CloudRepo, and every reason the record gives;
  • a battlecard for each top rival: the head-to-head split, why they win, and the reservation quoted against them;
  • one page of published figures cleared to show a buyer.
The subscriber app

A verification link goes to your work email; an address at cloudrepo.io is approved on the spot, any other is reviewed by hand. Your email is never published. Claiming gives no say over labels, shares, verdicts or which quotes appear.