Controlled provider comparisons

Compare GPU cloud providers

Hold the GPU constant or compare the shared provider portfolio. These pages exist only where both sides have enough current official evidence for a real buying decision.

Canonical decision inventory

Every page passes the evidence gate

The inventory is rebuilt from official-source records. A page needs enough configurations, regional or provider diversity and distinct price points for its exact intent. It is not published merely because a keyword can be formed.

A100 provider comparisons

Hold A100 constant and compare providers using the current evidenced price, region and availability profile for this exact accelerator.

provider model comparison118 rates

Civo vs Microsoft Azure · A100

$0.679–$8.193 per GPU-hour · 22 regions.

Deployability evidence: 0/118 rows (0%). This is not a live-stock claim.

160 GPU-hours: $108.60–$1310.80 observed compute range.

730 GPU-hours: $495.50–$5980.53 observed compute range.

provider model comparison118 rates

Crusoe Cloud vs Microsoft Azure · A100

$0.679–$8.193 per GPU-hour · 22 regions.

Deployability evidence: 0/118 rows (0%). This is not a live-stock claim.

160 GPU-hours: $108.60–$1310.80 observed compute range.

730 GPU-hours: $495.50–$5980.53 observed compute range.

provider model comparison118 rates

Hyperstack vs Microsoft Azure · A100

$0.679–$8.193 per GPU-hour · 22 regions.

Deployability evidence: 0/118 rows (0%). This is not a live-stock claim.

160 GPU-hours: $108.60–$1310.80 observed compute range.

730 GPU-hours: $495.50–$5980.53 observed compute range.

provider model comparison118 rates

Lambda vs Microsoft Azure · A100

$0.679–$8.193 per GPU-hour · 22 regions.

Deployability evidence: 0/118 rows (0%). This is not a live-stock claim.

160 GPU-hours: $108.60–$1310.80 observed compute range.

730 GPU-hours: $495.50–$5980.53 observed compute range.

provider model comparison120 rates

Microsoft Azure vs Paperspace · A100

$0.679–$8.193 per GPU-hour · 23 regions.

Deployability evidence: 2/120 rows (2%). This is not a live-stock claim.

160 GPU-hours: $108.60–$1310.80 observed compute range.

730 GPU-hours: $495.50–$5980.53 observed compute range.

B200 provider comparisons

Hold B200 constant and compare providers using the current evidenced price, region and availability profile for this exact accelerator.

provider model comparison5 rates

CoreWeave vs Nebius AI Cloud · B200

$3.950–$8.600 per GPU-hour · 2 regions.

Deployability evidence: 4/5 rows (80%). This is not a live-stock claim.

160 GPU-hours: $632.00–$1376.00 observed compute range.

730 GPU-hours: $2883.50–$6278.00 observed compute range.

provider model comparison5 rates

Nebius AI Cloud vs Verda · B200

$3.950–$7.150 per GPU-hour · 2 regions.

Deployability evidence: 4/5 rows (80%). This is not a live-stock claim.

160 GPU-hours: $632.00–$1144.00 observed compute range.

730 GPU-hours: $2883.50–$5219.50 observed compute range.

H100 provider comparisons

Hold H100 constant and compare providers using the current evidenced price, region and availability profile for this exact accelerator.

provider model comparison184 rates

Civo vs Microsoft Azure · H100

$1.290–$23.326 per GPU-hour · 31 regions.

Deployability evidence: 0/184 rows (0%). This is not a live-stock claim.

160 GPU-hours: $206.38–$3732.16 observed compute range.

730 GPU-hours: $941.63–$17027.98 observed compute range.

provider model comparison184 rates

Crusoe Cloud vs Microsoft Azure · H100

$1.290–$23.326 per GPU-hour · 31 regions.

Deployability evidence: 0/184 rows (0%). This is not a live-stock claim.

160 GPU-hours: $206.38–$3732.16 observed compute range.

730 GPU-hours: $941.63–$17027.98 observed compute range.

provider model comparison184 rates

DigitalOcean vs Microsoft Azure · H100

$1.290–$23.326 per GPU-hour · 31 regions.

Deployability evidence: 0/184 rows (0%). This is not a live-stock claim.

160 GPU-hours: $206.38–$3732.16 observed compute range.

730 GPU-hours: $941.63–$17027.98 observed compute range.

provider model comparison184 rates

Hyperstack vs Microsoft Azure · H100

$1.290–$23.326 per GPU-hour · 31 regions.

Deployability evidence: 0/184 rows (0%). This is not a live-stock claim.

160 GPU-hours: $206.38–$3732.16 observed compute range.

730 GPU-hours: $941.63–$17027.98 observed compute range.

provider model comparison184 rates

Lambda vs Microsoft Azure · H100

$1.290–$23.326 per GPU-hour · 31 regions.

Deployability evidence: 0/184 rows (0%). This is not a live-stock claim.

160 GPU-hours: $206.38–$3732.16 observed compute range.

730 GPU-hours: $941.63–$17027.98 observed compute range.

provider model comparison185 rates

Microsoft Azure vs Nebius AI Cloud · H100

$1.290–$23.326 per GPU-hour · 32 regions.

Deployability evidence: 2/185 rows (1%). This is not a live-stock claim.

160 GPU-hours: $206.38–$3732.16 observed compute range.

730 GPU-hours: $941.63–$17027.98 observed compute range.

provider model comparison184 rates

Microsoft Azure vs Paperspace · H100

$1.290–$23.326 per GPU-hour · 32 regions.

Deployability evidence: 1/184 rows (1%). This is not a live-stock claim.

160 GPU-hours: $206.38–$3732.16 observed compute range.

730 GPU-hours: $941.63–$17027.98 observed compute range.

H200 provider comparisons

Hold H200 constant and compare providers using the current evidenced price, region and availability profile for this exact accelerator.

provider model comparison9 rates

Civo vs Nebius AI Cloud · H200

$2.450–$4.500 per GPU-hour · 4 regions.

Deployability evidence: 8/9 rows (89%). This is not a live-stock claim.

160 GPU-hours: $392.00–$720.00 observed compute range.

730 GPU-hours: $1788.50–$3285.00 observed compute range.

provider model comparison9 rates

Crusoe Cloud vs Nebius AI Cloud · H200

$2.450–$4.500 per GPU-hour · 4 regions.

Deployability evidence: 8/9 rows (89%). This is not a live-stock claim.

160 GPU-hours: $392.00–$720.00 observed compute range.

730 GPU-hours: $1788.50–$3285.00 observed compute range.

provider model comparison9 rates

DataCrunch (now Verda) vs Nebius AI Cloud · H200

$2.450–$4.500 per GPU-hour · 4 regions.

Deployability evidence: 8/9 rows (89%). This is not a live-stock claim.

160 GPU-hours: $392.00–$720.00 observed compute range.

730 GPU-hours: $1788.50–$3285.00 observed compute range.

provider model comparison9 rates

DigitalOcean vs Nebius AI Cloud · H200

$2.450–$4.500 per GPU-hour · 4 regions.

Deployability evidence: 8/9 rows (89%). This is not a live-stock claim.

160 GPU-hours: $392.00–$720.00 observed compute range.

730 GPU-hours: $1788.50–$3285.00 observed compute range.

provider model comparison9 rates

Hyperstack vs Nebius AI Cloud · H200

$2.450–$4.500 per GPU-hour · 4 regions.

Deployability evidence: 8/9 rows (89%). This is not a live-stock claim.

160 GPU-hours: $392.00–$720.00 observed compute range.

730 GPU-hours: $1788.50–$3285.00 observed compute range.

L4 provider comparisons

Hold L4 constant and compare providers using the current evidenced price, region and availability profile for this exact accelerator.

provider model comparison20 rates

OVHcloud vs Scaleway · L4

$0.787–$1.923 per GPU-hour · 4 regions.

Deployability evidence: 20/20 rows (100%). This is not a live-stock claim.

160 GPU-hours: $126.00–$307.60 observed compute range.

730 GPU-hours: $574.88–$1403.43 observed compute range.

L40S provider comparisons

Hold L40S constant and compare providers using the current evidenced price, region and availability profile for this exact accelerator.

provider model comparison7 rates

Civo vs OVHcloud · L40S

$1.290–$1.800 per GPU-hour · 2 regions.

Deployability evidence: 6/7 rows (86%). This is not a live-stock claim.

160 GPU-hours: $206.40–$288.00 observed compute range.

730 GPU-hours: $941.70–$1314.00 observed compute range.

provider model comparison7 rates

Crusoe Cloud vs OVHcloud · L40S

$1.500–$1.800 per GPU-hour · 2 regions.

Deployability evidence: 6/7 rows (86%). This is not a live-stock claim.

160 GPU-hours: $240.00–$288.00 observed compute range.

730 GPU-hours: $1095.00–$1314.00 observed compute range.

provider model comparison7 rates

DigitalOcean vs OVHcloud · L40S

$1.570–$1.800 per GPU-hour · 2 regions.

Deployability evidence: 6/7 rows (86%). This is not a live-stock claim.

160 GPU-hours: $251.20–$288.00 observed compute range.

730 GPU-hours: $1146.10–$1314.00 observed compute range.

provider model comparison10 rates

OVHcloud vs Scaleway · L40S

$1.470–$1.800 per GPU-hour · 3 regions.

Deployability evidence: 10/10 rows (100%). This is not a live-stock claim.

160 GPU-hours: $235.19–$288.00 observed compute range.

730 GPU-hours: $1073.04–$1314.00 observed compute range.

provider model comparison7 rates

OVHcloud vs Vultr · L40S

$1.670–$1.800 per GPU-hour · 2 regions.

Deployability evidence: 6/7 rows (86%). This is not a live-stock claim.

160 GPU-hours: $267.20–$288.00 observed compute range.

730 GPU-hours: $1219.10–$1314.00 observed compute range.

Compare provider portfolios

Use these broader comparisons when provider choice comes first and you want to inspect the shared GPU catalog before narrowing to one accelerator.

provider comparison302 rates

Civo vs Microsoft Azure comparison

$0.679–$23.326 per GPU-hour · 38 regions.

Deployability evidence: 0/302 rows (0%). This is not a live-stock claim.

160 GPU-hours: $108.60–$3732.16 observed compute range.

730 GPU-hours: $495.50–$17027.98 observed compute range.

provider comparison12 rates

Civo vs Nebius AI Cloud comparison

$2.150–$4.500 per GPU-hour · 4 regions.

Deployability evidence: 10/12 rows (83%). This is not a live-stock claim.

160 GPU-hours: $344.00–$720.00 observed compute range.

730 GPU-hours: $1569.50–$3285.00 observed compute range.

provider comparison302 rates

Crusoe Cloud vs Microsoft Azure comparison

$0.679–$23.326 per GPU-hour · 38 regions.

Deployability evidence: 0/302 rows (0%). This is not a live-stock claim.

160 GPU-hours: $108.60–$3732.16 observed compute range.

730 GPU-hours: $495.50–$17027.98 observed compute range.

provider comparison12 rates

Crusoe Cloud vs Nebius AI Cloud comparison

$2.150–$4.500 per GPU-hour · 4 regions.

Deployability evidence: 10/12 rows (83%). This is not a live-stock claim.

160 GPU-hours: $344.00–$720.00 observed compute range.

730 GPU-hours: $1569.50–$3285.00 observed compute range.

provider comparison12 rates

DigitalOcean vs Nebius AI Cloud comparison

$2.150–$4.500 per GPU-hour · 4 regions.

Deployability evidence: 10/12 rows (83%). This is not a live-stock claim.

160 GPU-hours: $344.00–$720.00 observed compute range.

730 GPU-hours: $1569.50–$3285.00 observed compute range.

provider comparison302 rates

Hyperstack vs Microsoft Azure comparison

$0.679–$23.326 per GPU-hour · 38 regions.

Deployability evidence: 0/302 rows (0%). This is not a live-stock claim.

160 GPU-hours: $108.60–$3732.16 observed compute range.

730 GPU-hours: $495.50–$17027.98 observed compute range.

provider comparison12 rates

Hyperstack vs Nebius AI Cloud comparison

$2.150–$4.500 per GPU-hour · 4 regions.

Deployability evidence: 10/12 rows (83%). This is not a live-stock claim.

160 GPU-hours: $344.00–$720.00 observed compute range.

730 GPU-hours: $1569.50–$3285.00 observed compute range.

provider comparison302 rates

Lambda vs Microsoft Azure comparison

$0.679–$23.326 per GPU-hour · 38 regions.

Deployability evidence: 0/302 rows (0%). This is not a live-stock claim.

160 GPU-hours: $108.60–$3732.16 observed compute range.

730 GPU-hours: $495.50–$17027.98 observed compute range.

provider comparison304 rates

Microsoft Azure vs Paperspace comparison

$0.679–$23.326 per GPU-hour · 39 regions.

Deployability evidence: 3/304 rows (1%). This is not a live-stock claim.

160 GPU-hours: $108.60–$3732.16 observed compute range.

730 GPU-hours: $495.50–$17027.98 observed compute range.

provider comparison30 rates

OVHcloud vs Scaleway comparison

$0.787–$1.923 per GPU-hour · 4 regions.

Deployability evidence: 30/30 rows (100%). This is not a live-stock claim.

160 GPU-hours: $126.00–$307.60 observed compute range.

730 GPU-hours: $574.88–$1403.43 observed compute range.

Autonomous, not indiscriminate

How this index stays useful

Publish

A new URL becomes indexable only after its current official data passes family-specific breadth, freshness, source and uniqueness thresholds.

Update or noindex

Changed evidence triggers an update. A formerly qualified route that fails a cycle is preserved for users but immediately removed from search indexing.

Retire

After three consecutive failed cycles the route is retired. Canonical migrations are merged explicitly, preventing uncontrolled duplicates and crawl waste.