on demand observed floor
Hyperstack · $2.85/GPU hr
240 GPU-hours: $684.00
- Region sample
- Unspecified
- Observed
GPU cost intelligence
H100 cloud cost calculator
Compare H100 GPU prices from 8 providers. Observed range: $1.29–$6.98 per GPU-hour, with source evidence, availability signals, and cost estimates.
- Observed hourly range
- $1.29–$6.98 / GPU hr
- 730 GPU-hour range
- $941.63–$5,095.40
- Providers
- 8
- Official-source providers
- 8
- Fresh comparable offers
- 191
- Pricing observed
- Aug 13, 2026–Aug 13, 2026
- Regions observed
- 33
Decision snapshot by purchase model
Each card shows the lowest observed representative rate within its own purchase model. Spot and on-demand are intentionally not placed in one cheapest-to-expensive ranking because interruption risk, capacity behavior, and commercial terms are not interchangeable.
These are price floors, not recommendations: availability, region coverage, support, commitments, and workload fit can change the better purchasing choice.
spot observed floor
Microsoft Azure · $1.29/GPU hr
240 GPU-hours: $309.58
- Region sample
- eastus
- Observed
H100 price by purchase model
Purchase models are kept separate because interruption risk, commitment terms, and capacity behavior are not interchangeable. Each range uses only fresh representative offers from the same market type.
Spot vs on-demand low end
54.7% lower observed spot floor
The lowest representative spot rate is $1.29/GPU hr versus $2.85/GPU hr for on-demand. This compares observed price floors only; spot interruption risk, capacity, regions and workload suitability remain separate decisions.
Decision read: Spot has the lower observed floor in this snapshot. Treat that gap as a candidate saving only for workloads that can tolerate interruption and after checking capacity, regions, and workload fit.
Compute-only break-even: at these observed floors, spot could consume up to 120.9% more billed GPU-hours before its compute cost matches the on-demand floor. This threshold does not price engineering work, checkpointing, restart latency, SLA exposure, lost progress, or opportunity cost.
160 GPU-hours · observed floors
$249.62 lower spot cost
Spot floor: $206.38 · On-demand floor: $456.00.
Compute retry budget: spot could add up to 193.5 billed GPU-hours at this baseline before matching the on-demand floor's compute spend.
Price-floor scenario only; interruption risk, capacity, regions, commitments and workload suitability are not priced into this comparison.
240 GPU-hours · observed floors
$374.42 lower spot cost
Spot floor: $309.58 · On-demand floor: $684.00.
Compute retry budget: spot could add up to 290.3 billed GPU-hours at this baseline before matching the on-demand floor's compute spend.
Price-floor scenario only; interruption risk, capacity, regions, commitments and workload suitability are not priced into this comparison.
730 GPU-hours · observed floors
$1,138.87 lower spot cost
Spot floor: $941.63 · On-demand floor: $2,080.50.
Compute retry budget: spot could add up to 882.9 billed GPU-hours at this baseline before matching the on-demand floor's compute spend.
Price-floor scenario only; interruption risk, capacity, regions, commitments and workload suitability are not priced into this comparison.
Observed H100 price dispersion
Across the representative offers in this snapshot, the normalized rate runs from $1.29 to $6.98 per GPU-hour, a gap of $5.69. At 730 GPU-hours, that rate gap corresponds to $4,153.77.
160 GPU-hours
$910.42 price-range gap
Observed compute budget range: $206.38–$1,116.80 at this usage level.
If the observed floor rate were otherwise suitable for the same workload, that ceiling budget would mathematically cover 865.8 GPU-hours — 705.8 more than this scenario.
Difference between the lowest and highest representative H100 rates at this usage level.
240 GPU-hours
$1,365.62 price-range gap
Observed compute budget range: $309.58–$1,675.20 at this usage level.
If the observed floor rate were otherwise suitable for the same workload, that ceiling budget would mathematically cover 1298.7 GPU-hours — 1058.7 more than this scenario.
Difference between the lowest and highest representative H100 rates at this usage level.
730 GPU-hours
$4,153.77 price-range gap
Observed compute budget range: $941.63–$5,095.40 at this usage level.
If the observed floor rate were otherwise suitable for the same workload, that ceiling budget would mathematically cover 3950.2 GPU-hours — 3220.2 more than this scenario.
Difference between the lowest and highest representative H100 rates at this usage level.
Read from the budget floor, the highest observed representative rate is 441.1% above the lowest; read from the ceiling, the lowest is 81.5% below the highest. This is price dispersion, not a guaranteed saving: purchase model, availability, region coverage, support, commitments, and workload fit can differ between offers.
Current H100 cloud pricing evidence
Representative comparable offers are normalized to a per-GPU-hour rate and ranked from lowest to highest.
| Provider | Variant | Market | Price | 730 GPU hr | Freshness | Observed | Evidence |
|---|---|---|---|---|---|---|---|
| Microsoft Azure | NVL 94GB | spot | $1.29/GPU hr | $941.63 | recent | Source | |
| Nebius AI Cloud | NVLink 80GB | spot | $2.15/GPU hr | $1,569.50 | recent | Source | |
| Hyperstack | H100 | on demand | $2.85/GPU hr | $2,080.50 | recent | Source | |
| Civo | H100 | on demand | $2.99/GPU hr | $2,182.70 | recent | Source | |
| Lambda | H100 | on demand | $3.79/GPU hr | $2,766.70 | recent | Source | |
| Nebius AI Cloud | NVLink 80GB | on demand | $3.85/GPU hr | $2,810.50 | recent | Source | |
| Crusoe Cloud | H100 | on demand | $3.90/GPU hr | $2,847.00 | recent | Source | |
| DigitalOcean | H100 | on demand | $4.41/GPU hr | $3,219.30 | recent | Source | |
| Paperspace | SXM 80GB | on demand | $5.95/GPU hr | $4,343.50 | recent | Source | |
| Microsoft Azure | NVL 94GB | on demand | $6.98/GPU hr | $5,095.40 | recent | Source |
H100 regional coverage
These are explicitly named regions reported by fresh comparable offers. Counts and provider identities describe observed catalog coverage, not live capacity or guaranteed availability; unspecified placements are not assigned to a region.
Regional provider concentration
0 of 33 named regions have evidence from 2+ providers
0 observed regions include fresh comparable H100 catalog evidence from at least two providers, while 33 are represented by one provider only.
Cross-provider catalog coverage: 0% of explicitly named regions.
3+ provider catalog depth: 0 named regions (0%) include a third observed provider option. This is a deeper catalog-diversity signal only, not proof that those providers are operationally substitutable or simultaneously available.
Decision read: Every explicitly named region in this fresh comparable snapshot is represented by one provider only, so regional fallback planning has no cross-provider catalog evidence here.
Single-provider region watchlist: eastus2 — Microsoft Azure, centralus — Microsoft Azure, eastus — Microsoft Azure, plus 30 more in the region table below. Each provider shown is only the sole provider represented by fresh comparable catalog rows for that named region in this snapshot; it is not a live availability or exclusivity claim.
This is a catalog-breadth signal for fallback planning, not proof of simultaneous capacity, failover readiness, quota, latency, workload fit, or contractual substitutability.
| Region | Fresh comparable offers | Providers represented | Observed providers |
|---|---|---|---|
| eastus2 | 16 | 1 | Microsoft Azure |
| centralus | 14 | 1 | Microsoft Azure |
| eastus | 14 | 1 | Microsoft Azure |
| northcentralus | 11 | 1 | Microsoft Azure |
| polandcentral | 10 | 1 | Microsoft Azure |
| swedencentral | 10 | 1 | Microsoft Azure |
| japaneast | 8 | 1 | Microsoft Azure |
| koreacentral | 8 | 1 | Microsoft Azure |
| southcentralus | 8 | 1 | Microsoft Azure |
| southeastus | 8 | 1 | Microsoft Azure |
| spaincentral | 8 | 1 | Microsoft Azure |
| australiaeast | 6 | 1 | Microsoft Azure |
| canadacentral | 6 | 1 | Microsoft Azure |
| centralindia | 4 | 1 | Microsoft Azure |
| germanywestcentral | 4 | 1 | Microsoft Azure |
| indonesiacentral | 4 | 1 | Microsoft Azure |
| japanwest | 4 | 1 | Microsoft Azure |
| koreasouth | 4 | 1 | Microsoft Azure |
| malaysiawest | 4 | 1 | Microsoft Azure |
| westeurope | 4 | 1 | Microsoft Azure |
| westus | 4 | 1 | Microsoft Azure |
| westus2 | 4 | 1 | Microsoft Azure |
| westus3 | 4 | 1 | Microsoft Azure |
| eu-north1 | 2 | 1 | Nebius AI Cloud |
| jioindiacentral | 2 | 1 | Microsoft Azure |
| jioindiawest | 2 | 1 | Microsoft Azure |
| southafricanorth | 2 | 1 | Microsoft Azure |
| southafricawest | 2 | 1 | Microsoft Azure |
| switzerlandnorth | 2 | 1 | Microsoft Azure |
| uaenorth | 2 | 1 | Microsoft Azure |
| uksouth | 2 | 1 | Microsoft Azure |
| westcentralus | 2 | 1 | Microsoft Azure |
| ny2 | 1 | 1 | Paperspace |
Deployability evidence coverage
3 of 10 representative offers (30%) have a non-unknown deployment status backed by a separate HTTPS evidence source and a valid observation time.
Deployability evidence gap
30% separately evidenced
7 representative offers currently lack qualifying deployment-eligibility evidence and remain explicitly unevidenced.
Decision read: 7 representative offers should still be treated as unknown for deployability comparisons; do not use a current price row as a substitute for capacity evidence.
Deployment eligibility is separate from price freshness. It does not prove live stock or allocatable capacity; offers without qualifying evidence remain explicitly unknown.
Typed availability evidence
Availability is tracked separately from pricing. The evidence kind distinguishes deployment eligibility from live stock or allocatable capacity; none of those claims is inferred from a listed price.
| Provider | Market | Regions | Status | Evidence kind | Observed | Evidence |
|---|---|---|---|---|---|---|
| Microsoft Azure | spot | eastus | unknown | unknown | Not separately observed | No separate source |
| Nebius AI Cloud | spot | eu-north1 | available | deployment eligibility | Availability source | |
| Hyperstack | on demand | Unspecified | unknown | unknown | Not separately observed | No separate source |
| Civo | on demand | Unspecified | unknown | unknown | Not separately observed | No separate source |
| Lambda | on demand | Unspecified | unknown | unknown | Not separately observed | No separate source |
| Nebius AI Cloud | on demand | eu-north1 | available | deployment eligibility | Availability source | |
| Crusoe Cloud | on demand | Unspecified | unknown | unknown | Not separately observed | No separate source |
| DigitalOcean | on demand | Unspecified | unknown | unknown | Not separately observed | No separate source |
| Paperspace | on demand | ny2 | available | deployment eligibility | Availability source | |
| Microsoft Azure | on demand | eastus | unknown | unknown | Not separately observed | No separate source |
Calculate H100 GPU cost
Enter the GPU-hours you expect to consume. The estimate uses the same lowest and highest representative hourly rates shown above and excludes storage, bandwidth, support, taxes, commitments, and negotiated discounts.
H100 cost scenarios
These estimates multiply GPU-hours by the lowest and highest representative hourly rates above. They exclude storage, bandwidth, support, taxes, commitments, and negotiated discounts.
| GPU-hours | Published price range |
|---|---|
| 40 | $51.60–$279.20 |
| 160 | $206.38–$1,116.80 |
| 240 | $309.58–$1,675.20 |
| 730 | $941.63–$5,095.40 |
Compare H100 by provider
Open the exact provider × H100 decision sheets that currently pass the autonomous publication gates. Each page keeps provider-specific regions, configurations, evidence, and normalized rates separate from the broader market view above.
How this comparison is built
- Only comparable normalized records for the exact H100 model are eligible.
- Fresh records are limited to the existing live, recent, or verified freshness states; this snapshot is 100% fresh.
- Representative rows keep the lowest normalized rate for each provider and market type, so spot and on-demand offers are not blended together.
- Pricing evidence does not guarantee live capacity. Check the linked source and provider availability before purchasing.
Verification and policies
Review the broader GPU cloud pricing hub, the data sources, the editorial policy, and the corrections policy to inspect how SaaS Sentinel sources, reviews, and corrects published evidence.