# Radiant/Ori (Unavailable) — ClusterMAX GPU Cloud Review

> Radiant/Ori earns a ClusterMAX Unavailable rating from SemiAnalysis (introduced April 2026 in the ClusterMAX 2.1 Update). Radiant was announced recently after Brookfield acquired Ori, a Saudi Aramco backed neocloud with H100s and H200s in London and Dallas. When we tested with Ori on two occasions…

- **Provider**: Radiant/Ori
- **ClusterMAX Tier**: Unavailable
- **Tier definition**: Interesting service we cannot verify yet (not launched, sold out, government-only, etc.).
- **Authors**: Jordan Nanos, Daniel Nishball, Dylan Patel (SemiAnalysis)
- **Published**: 2026-04-20 (Apr 20, 2026)
- **Last updated**: 2026-04-20 (Apr 20, 2026)
- **Source**: ClusterMAX 2.1 Update
- **Canonical URL**: https://www.clustermax.ai/cloudreview/radiantori
- **Source article**: https://newsletter.semianalysis.com/i/194395279/clustermax-21-update
- **Topics**: Radiant/Ori review, Radiant/Ori GPU cloud, Radiant/Ori ClusterMAX rating, Radiant/Ori Unavailable, Unavailable tier GPU cloud, GPU cloud review, neocloud review, Radiant/Ori H200, Radiant/Ori H100, H200 cloud, H100 cloud, Kubernetes, Slurm, NCCL, DCGM, ClusterMAX 2.0, ClusterMAX 2.1, ClusterMAX 2.1 Update, SemiAnalysis

---

Radiant was announced recently after Brookfield acquired Ori, a Saudi Aramco backed neocloud with H100s and H200s in London and Dallas. When we tested with Ori on two occasions in the fall, we saw some quick progress but not enough to get to silver. Ori fell victim to the exact same issues as FPT, with PKey and SAKey not configured correctly. In addition, during our first round of testing, we were unable to run nccl-tests at full bandwidth on kubernetes due to an issue with the NetworkOperator picking up NICs that were intended to be for the frontend but were named/configured incorrectly to be used for NCCL. Finally, DCGMI health watches are not enabled by default, and there is no automated background health check program. Our testing of a simple hardware failure simulation showed that the system did not trigger any automated alerting or node replacement over an 18-hour window. The team is targeting Q2 2026 for the release of monitoring dashboards, and seems well on their way to having the funding they need to build Blackwell clusters with comprehensive slurm, kubernetes, monitoring and reliability features customers expect.

---

Other Unavailable tier providers:
- NScale: https://www.clustermax.ai/cloudreview/nscale
- Core42/G42: https://www.clustermax.ai/cloudreview/core42g42
- HUMAIN Compute: https://www.clustermax.ai/cloudreview/humaincompute
- Corvex: https://www.clustermax.ai/cloudreview/corvex
- Highrise: https://www.clustermax.ai/cloudreview/highrise
- BluSky: https://www.clustermax.ai/cloudreview/blusky
- Andromeda: https://www.clustermax.ai/cloudreview/andromeda
- Mistral: https://www.clustermax.ai/cloudreview/mistral
- Firebird: https://www.clustermax.ai/cloudreview/firebird
- TELUS: https://www.clustermax.ai/cloudreview/telus
- Telenor: https://www.clustermax.ai/cloudreview/telenor
- Alibaba Cloud: https://www.clustermax.ai/cloudreview/alibabacloud
- ARC Compute: https://www.clustermax.ai/cloudreview/arccompute
- MegaSpeed: https://www.clustermax.ai/cloudreview/megaspeed
- Bitdeer: https://www.clustermax.ai/cloudreview/bitdeer
- Runsun: https://www.clustermax.ai/cloudreview/runsun
- FPT CLOUD: https://www.clustermax.ai/cloudreview/fptcloud
- Backend: https://www.clustermax.ai/cloudreview/backend
- Naver: https://www.clustermax.ai/cloudreview/naver
- Indosat: https://www.clustermax.ai/cloudreview/indosat
- SAKURA: https://www.clustermax.ai/cloudreview/sakura
- Yotta: https://www.clustermax.ai/cloudreview/yotta
- Neev Cloud: https://www.clustermax.ai/cloudreview/neevcloud
- Evroc: https://www.clustermax.ai/cloudreview/evroc
- greenai.cloud: https://www.clustermax.ai/cloudreview/greenaicloud

Full ClusterMAX 2.0 + 2.1 index: https://www.clustermax.ai/cloudreview
Full LLM dump of all reviews: https://www.clustermax.ai/llms-full.txt