SemiAnalysis releases ClusterMAX 3.0 rating 77 GPU cloud providers
SemiAnalysis published ClusterMAX 3.0, a rating of GPU cloud (neocloud) providers. The report covers 77 providers, expanding its market view to 323 providers, up from 209, 169, 124 in previous versions. Over 200 end‑user interviews were conducted, and the methodology tests 32 GPUs per provider, high‑bandwidth networking, storage, orchestration, monitoring, and support.
Key points
- ClusterMAX 3.0 evaluates 77 providers, expanding market view to 323 providers (up from 209, 169, 124).
- Nebius joins CoreWeave in Platinum tier; Google Cloud joins Oracle in Gold tier, Azure moves to Silver.
- Only 19 neoclouds receive Medallion rating; 15 providers placed in new Participation Ribbon tier.
The tier list places CoreWeave and Nebius together in the Platinum tier, while Google Cloud joins Oracle in Gold. Azure moves to Silver, Fluidstack is marked Unavailable, Crusoe drops to Bronze, and several others shift down. Only 19 providers achieve a Medallion rating, and a new Participation Ribbon tier holds 15 providers that meet minimal criteria.
The report also discusses financing trends, the dominance of frontier labs such as OpenAI and Anthropic, and the growing importance of managed clusters despite labs building their own stacks. SemiAnalysis announces hiring for MTS and other roles to support future ClusterMAX work.
The headline, key points and digest above were generated by Digest AI's editorial model from the linked sources. Automated summaries can contain errors: the sources are the record. Spotted a mistake? Tell us. Published by Martin K., who runs Digest AI and handles corrections.
More in Research
All →- Anthropic says Claude identified new enzyme system resembling crispr · 2 src
- GPT-6 Astra drives a car in leaderboard tests · 1 src
- Anthropic is setting up a biology lab where Claude guides robots in drug experiments · 2 src
- OpenAI says its agents solved Navier‑Stokes equations, proof incomprehensible · 2 src
- Guide details AI security measures after OpenAI data leak · 1 src
Comments
via GitHub Discussions