<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Teraplex capacity digest</title>
    <link>https://teraplex.us/capacity-digest</link>
    <atom:link href="https://teraplex.us/capacity-digest/rss.xml" rel="self" type="application/rss+xml" />
    <description>A dated read of public GPU capacity and price pages, for people who own a site with land and power. Every number carries a live source and the date it was read.</description>
    <language>en-us</language>
    <item>
      <title>Capacity digest 03: Public GPU capacity listings</title>
      <link>https://teraplex.us/capacity-digest/2026-07-28-issue-03</link>
      <guid isPermaLink="true">https://teraplex.us/capacity-digest/2026-07-28-issue-03</guid>
      <pubDate>Wed, 29 Jul 2026 02:52:02 GMT</pubDate>
      <description>Fourteen dated public GPU listings from six providers, shown with pricing, scale, provider-stated status and missing infrastructure fields preserved.</description>
      <content:encoded><![CDATA[<p>Every row below is a dated read of public provider pages. The pages can change after re-read, so
the source log preserves the observation boundary.</p>
<h2 id="offers">Offers</h2>
<table>
<thead>
<tr>
<th>Provider</th>
<th>Public configurations</th>
<th>Capacity per listing</th>
<th>Status boundary</th>
<th style="text-align: right">Published price</th>
<th>Commercial basis</th>
<th>Source</th>
</tr>
</thead>
<tbody>
<tr>
<td>Impossible Cloud</td>
<td>H100 SXM; GB300; two B300 configurations</td>
<td>8–1,152 GPUs</td>
<td>Two dated listings; two not displayed</td>
<td style="text-align: right">$2.41–$4.42/GPU-hour</td>
<td>12–60 months</td>
<td><a href="https://www.impossiblecloud.com/en-us/baremetal">Impossible Cloud</a></td>
</tr>
<tr>
<td>Prime Intellect</td>
<td>B300 SXM6 reserved example</td>
<td>512 GPUs</td>
<td>Not displayed</td>
<td style="text-align: right">$5.00/GPU-hour</td>
<td>3 years</td>
<td><a href="https://www.primeintellect.ai/">Prime Intellect</a></td>
</tr>
<tr>
<td>Verda</td>
<td>Four Instant Cluster configurations; one H200 VM; one B200 VM</td>
<td>1–144 GPUs</td>
<td>Provider-stated self-service; current stock not verified</td>
<td style="text-align: right">$4.00–$8.62/GPU-hour</td>
<td>PAYG; VM use billed in prepaid 10-minute increments; VAT applies</td>
<td><a href="https://verda.com/instant-clusters">Instant Clusters</a>, <a href="https://verda.com/h200">H200 VM</a>, <a href="https://verda.com/b200">B200 VM</a></td>
</tr>
<tr>
<td>Gcore</td>
<td>One H100 80 GB virtual GPU machine</td>
<td>1 GPU</td>
<td>Provider-stated self-service. Sines-3 is the named launch region. Current stock is unverified.</td>
<td style="text-align: right">€1.65/VM-hour</td>
<td>Minimum term not published; prices exclude VAT</td>
<td><a href="https://gcore.com/pricing/ai">Gcore</a></td>
</tr>
<tr>
<td>Google Cloud</td>
<td>One a3-highgpu-8g Flex-start VM</td>
<td>8 GPUs</td>
<td>Listed in us-central1-c. The zone is supported. Current stock is unverified.</td>
<td style="text-align: right">USD 38.32/VM-hour</td>
<td>PAYG; runtime up to 7 days; reservations unsupported</td>
<td><a href="https://cloud.google.com/products/dws/pricing">Google Cloud</a></td>
</tr>
<tr>
<td>Crusoe</td>
<td>One h100-80gb-sxm-ib.8x VM</td>
<td>8 GPUs</td>
<td>Provider-stated self-service; current stock not verified</td>
<td style="text-align: right">$3.90/GPU-hour</td>
<td>On demand; no minimum commitment</td>
<td><a href="https://www.crusoe.ai/cloud/pricing">Crusoe</a></td>
</tr>
</tbody>
</table>
<p>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.</p>
<p>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.</p>
<h2 id="direct-source-log">Direct source log</h2>
<ul>
<li>Verda H200 VM: <a href="https://verda.com/h200">product page</a>, <a href="https://docs.verda.com/cli/instances/">CLI instance reference</a>, <a href="https://verda.com/gpu-instances">GPU instances catalog</a>, <a href="https://docs.verda.com/welcome-to-verda/pricing-and-billing/">pricing and billing</a>, <a href="https://verda.com/terms-and-conditions">terms</a>, and <a href="https://docs.verda.com/welcome-to-verda/locations-and-sustainability/">locations</a>.</li>
<li>Verda B200 VM: <a href="https://verda.com/b200">product page</a>, <a href="https://docs.verda.com/cli/instances/">CLI instance reference</a>, <a href="https://verda.com/gpu-instances">GPU instances catalog</a>, <a href="https://docs.verda.com/welcome-to-verda/pricing-and-billing/">pricing and billing</a>, <a href="https://verda.com/terms-and-conditions">terms</a>, and <a href="https://docs.verda.com/welcome-to-verda/locations-and-sustainability/">locations</a>.</li>
<li>Gcore H100 VM: <a href="https://gcore.com/pricing/ai">pricing</a>, <a href="https://gcore.com/blog/gpu-vm-launch">launch notice</a>, and <a href="https://gcore.com/docs/api-reference/cloud/gpu-virtual/list-virtual-gpu-flavors">virtual GPU flavors API reference</a>.</li>
<li>Google Cloud A3 High Flex-start VM: <a href="https://cloud.google.com/products/dws/pricing">pricing</a>, <a href="https://docs.cloud.google.com/compute/docs/accelerator-optimized-machines">A3 specifications</a>, <a href="https://docs.cloud.google.com/compute/docs/regions-zones/gpu-regions-zones">GPU regions and zones</a>, <a href="https://docs.cloud.google.com/compute/docs/instances/about-flex-start-vms">Flex-start overview</a>, and <a href="https://docs.cloud.google.com/compute/docs/instances/create-flex-start-vm">creation guide</a>.</li>
<li>Crusoe H100 VM: <a href="https://www.crusoe.ai/cloud/pricing">pricing</a>, <a href="https://docs.crusoecloud.com/quickstart/creating-a-vm/index.html">VM quickstart</a>, <a href="https://docs.crusoecloud.com/networking/infiniband/managing-infiniband-networks/">InfiniBand reference</a>, <a href="https://docs.crusoecloud.com/compute/virtual-machines/overview/">VM specifications</a>, <a href="https://docs.crusoecloud.com/usage-billing/viewing-billing/index.html">billing documentation</a>, and <a href="https://legal.crusoe.ai/">legal terms</a>.</li>
</ul>
<h2 id="electrical-disclosure-boundary">Electrical disclosure boundary</h2>
<p>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.</p>
<p>FERC’s 18 June 2026 action addresses the rules governing how data centers and other large energy
users connect to the grid.
<a href="https://www.ferc.gov/news-events/news/ferc-launches-aggressive-targeted-action-speed-large-load-integration">FERC large-load integration release</a>.</p>
<h2 id="boundary">Boundary</h2>
<p>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.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Capacity digest 02: One GPU model, three sets of quoted terms</title>
      <link>https://teraplex.us/capacity-digest/2026-07-28-issue-02</link>
      <guid isPermaLink="true">https://teraplex.us/capacity-digest/2026-07-28-issue-02</guid>
      <pubDate>Tue, 28 Jul 2026 00:54:48 GMT</pubDate>
      <description>The same B300 silicon at $3.86, $4.42 and $5.00 per GPU-hour, and what separates the three numbers.</description>
      <content:encoded><![CDATA[<p>Both pages were read on July 27, 2026, and both can change after capture. No page-level effective
date was captured from either page. “Not captured” marks a field Teraplex did not record from that
page on that date; it is not a statement about what the publisher did or did not show.</p>
<h2 id="one-model-three-sets-of-quoted-terms">One model, three sets of quoted terms</h2>
<table>
<thead>
<tr>
<th>Public B300 record</th>
<th>Region</th>
<th>Availability</th>
<th style="text-align: right">Minimum term</th>
<th style="text-align: right">Listed rate</th>
<th>Source</th>
</tr>
</thead>
<tbody>
<tr>
<td>256 GPUs, 32 nodes, SXM</td>
<td>US</td>
<td>2027-08-01</td>
<td style="text-align: right">36 months</td>
<td style="text-align: right">$4.42/GPU-hour</td>
<td><a href="https://www.impossiblecloud.com/en-us/baremetal">Impossible Cloud</a></td>
</tr>
<tr>
<td>1,024 GPUs, 128 nodes, SXM</td>
<td>US</td>
<td>Not captured</td>
<td style="text-align: right">60 months</td>
<td style="text-align: right">$3.86/GPU-hour</td>
<td><a href="https://www.impossiblecloud.com/en-us/baremetal">Impossible Cloud</a></td>
</tr>
<tr>
<td>512-GPU SXM6 reserved example</td>
<td>Not captured</td>
<td>Not captured</td>
<td style="text-align: right">Three years</td>
<td style="text-align: right">$5.00/GPU-hour</td>
<td><a href="https://www.primeintellect.ai/">Prime Intellect</a></td>
</tr>
</tbody>
</table>
<p>These public records differ in cluster size, term, interconnect detail captured, region, availability
and source type. Teraplex does not treat them as comparable quotes.</p>
<h2 id="availability-as-a-schedule-field">Availability as a schedule field</h2>
<p>A GPU-hour rate can be public while no delivery date is captured alongside it. Teraplex’s reading
method for an electrical-infrastructure schedule is to treat an uncaptured delivery date as unknown
rather than as immediate availability.</p>
<p>The first record carries a dated availability field. For the second record, availability was not
captured; for the reserved example, neither region nor availability was captured. Teraplex records
those differences to keep a public price record separate from a delivery plan.</p>
<h2 id="boundary">Boundary</h2>
<p>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.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Capacity digest 01: Six fields that decide whether a GPU-hour rate means anything</title>
      <link>https://teraplex.us/capacity-digest/2026-07-27-issue-01</link>
      <guid isPermaLink="true">https://teraplex.us/capacity-digest/2026-07-27-issue-01</guid>
      <pubDate>Tue, 28 Jul 2026 00:36:47 GMT</pubDate>
      <description>H100 index at $2.72, public listings from $2.41 to $5.00, and why the headline rate is the least useful number on the page.</description>
      <content:encoded><![CDATA[<p>Every value below was read from a public page on July 27, 2026. Listings are live documents and can
change after capture. “Not captured” marks a field Teraplex did not record from that page on that
date; it is not a statement about what the publisher did or did not show.</p>
<h2 id="price-index">Price index</h2>
<p>Ornn’s H100 SXM daily index printed <strong>$2.72 per GPU-hour on July 27</strong>. Across its last seven daily
observations, the index moved from $2.73 to $2.72, a <strong>0.4% decline</strong>.
<a href="https://index.ornn.com/api/gpu/H100%20SXM/index-history?startDate=2026-07-20&amp;endDate=2026-07-28">Ornn public history</a>.</p>
<p>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.
<a href="https://data.ornn.com/docs/price-index">Ornn price-index methodology</a>.</p>
<h2 id="public-capacity-watch">Public capacity watch</h2>
<table>
<thead>
<tr>
<th>GPU</th>
<th>Public capacity record</th>
<th style="text-align: right">Listed rate</th>
<th>Source</th>
</tr>
</thead>
<tbody>
<tr>
<td>H100 SXM</td>
<td>8 GPUs, 1 node, US, 12-month minimum; availability not captured</td>
<td style="text-align: right">$2.41/GPU-hour</td>
<td><a href="https://www.impossiblecloud.com/en-us/baremetal">Impossible Cloud</a></td>
</tr>
<tr>
<td>GB300</td>
<td>1,152 GPUs, 16 nodes, US, available September 30, 2026, 36-month minimum</td>
<td style="text-align: right">$4.32/GPU-hour</td>
<td><a href="https://www.impossiblecloud.com/en-us/baremetal">Impossible Cloud</a></td>
</tr>
<tr>
<td>B300 SXM6</td>
<td>512-GPU example, three-year reserved term; region and availability not captured</td>
<td style="text-align: right">$5.00/GPU-hour</td>
<td><a href="https://www.primeintellect.ai/">Prime Intellect</a></td>
</tr>
</tbody>
</table>
<p>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.</p>
<h2 id="site-owner-read">Site-owner read</h2>
<p>This section is Teraplex’s own reading method for these records. No published standard or industry
convention defines it. We treat a GPU-hour rate as usable in a powered-site plan only when the same
record also preserves six fields:</p>
<ol>
<li>GPU model</li>
<li>Cluster size</li>
<li>Region</li>
<li>Availability date</li>
<li>Minimum term</li>
<li>Interconnect</li>
</ol>
<p>Recording those six fields next to the rate is what keeps an index, an on-page listing and a
reserved-cluster example distinguishable from one another before any rate enters an infrastructure
or revenue model.</p>
<h2 id="boundary">Boundary</h2>
<p>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.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
