Offers

The dashboard preserves each configuration inside its provider row. The five added records appear only in the currently listed bucket. Provider-stated self-service paths, supported zones, published prices and documented create workflows do not establish current stock, launchability, reservability or successful provisioning.

These records differ in hardware generation, cluster size, region disclosure, availability, term and source type. They do not establish a market average or directly comparable quotes. Every derived normalization is labeled in the dashboard. No authenticated inventory query, reservation, provisioning request or billable launch was performed.

Direct source log

• Verda H200 VM: product page, CLI instance reference, GPU instances catalog, pricing and billing, terms, and locations.
• Verda B200 VM: product page, CLI instance reference, GPU instances catalog, pricing and billing, terms, and locations.
• Gcore H100 VM: pricing, launch notice, and virtual GPU flavors API reference.
• Google Cloud A3 High Flex-start VM: pricing, A3 specifications, GPU regions and zones, Flex-start overview, and creation guide.
• Crusoe H100 VM: pricing, VM quickstart, InfiniBand reference, VM specifications, billing documentation, and legal terms.

Electrical disclosure boundary

The provider pages do not display the utility, service voltage, committed megawatts, study status or grid-energization date for these records. Compute-fabric terms such as InfiniBand or bandwidth per node do not establish electrical interconnection.

FERC’s 18 June 2026 action addresses the rules governing how data centers and other large energy users connect to the grid. FERC large-load integration release.

Boundary

This is dated public-data curation. It is not an offer, availability confirmation, valuation, pricing recommendation, demand forecast or matching service. Availability, configuration, taxes, region and commercial terms require confirmation before procurement or scheduling.

One model, three planning envelopes

These public records differ in cluster size, term, interconnect disclosure, region, availability and source type. They do not form comparable quotes.

Availability as a schedule field

A GPU-hour rate can be public while its delivery date remains blank. For an electrical-infrastructure schedule, that blank cannot be read as immediate availability. It stays unknown.

The first record carries a dated availability field. The second listing leaves that field blank. The reserved example states neither a region nor an availability date. Preserving those differences keeps a public price record separate from a delivery plan.

Boundary

This issue is public-data curation. It is not an offer, availability confirmation, valuation, pricing recommendation, demand forecast or matching service. It collects no reader data.

Price index

Ornn’s H100 SXM daily index printed $2.72 per GPU-hour on July 27. Across its last seven daily observations, the index moved from $2.73 to $2.72, a 0.4% decline. Ornn public history.

Ornn defines this global index as a weighted average of verified compute transactions in US dollars per GPU-hour. The daily value is an aggregate of hourly observations. Ornn price-index methodology.

Public capacity watch

These rows cover different hardware generations, cluster sizes, availability fields, regions and terms. Ornn is a transaction index. The other figures are provider list or example prices. The table does not establish a market average or an achievable quote.

Site-owner read

A GPU-hour rate becomes useful to a powered-site plan when the same record preserves six fields:

1. GPU model
2. Cluster size
3. Region
4. Availability date
5. Minimum term
6. Interconnect

That envelope separates an index, an on-page listing and a reserved-cluster example before any rate enters an infrastructure or revenue model.

Boundary

This issue is public-data curation. It is not an offer, valuation, pricing recommendation, availability confirmation, demand forecast or matching service. It collects no reader data.