All field guides

Constraint Alpha · Research analysis · 3 charts

GPU Rents Are Rising. AI Margins Need a Better Test.

GPU rental benchmarks, CoreWeave’s EBITDA-to-net-loss bridge and transparent productivity scenarios explain who captures value in AI compute.

Published October 27, 2026 · Updated October 27, 2026 · Source periods and chart data are shown below.
Long-form research · Compute economicsData cutoff · 27 Oct 2026

AI infrastructure can be scarce while its owners earn disappointing returns. The investment question is who can turn a constrained resource into durable cash after operating costs, financing and replacement investment.

The research in three points

  1. GPU rental benchmarks indicate tighter spot conditions, but neither a spot quote nor a token-price index measures a company’s realized margin.
  2. CoreWeave’s financial reconciliation shows why EBITDA, operating profit and net income answer different questions about the same infrastructure.
  3. The critical denominator is useful, billable output under a specified quality and latency requirement. Productivity and utilization can reverse the conclusion drawn from prices alone.

1. The spot market is a signal, not the entire business

The supply chain has several distinct owners of scarce resources: chip designers and manufacturers, owners of energized buildings, compute operators, and businesses selling model access. They do not share a single revenue model. One sells equipment, another rents time, and another monetizes an outcome. A constraint can support one layer while raising costs for another.

Figure 1 records five GPU benchmarks from the same settlement date. The dispersion matters: a newer accelerator can command a higher hourly rate while delivering a different quantity of useful work. Comparing those dollar rates as if they were identical services confuses the price of an input with the cost of production. [ornn]

FIGURE 01 · EVIDENCE

Compute has several prices, not one

Ornn on-demand benchmarks · 26 October 2026 · USD per GPU-hour; monthly changes shown as text

Bars measure hourly rental cost, not cost per token or relative hardware value. Monthly changes are benchmark observations, not matched-company realized contract pricing. No historical line is inferred from this snapshot.

Inspect the chart data and source
CategoryValue1-month change
H100 SXM$3.17+24.80%
H200$6.21+29.92%
B200$9.76+21.39%
A100 SXM4$1.09+14.74%
RTX PRO 6000$1.54+1.32%

26 October 2026 settlement · USD per GPU-hour; monthly change %

Source: Ornn Compute Price Index dashboard · Ornn OCPI methodology

Ornn’s methodology uses active on-demand transactions and a volume-weighted, winsorized calculation. Long-term and reserved contracts are outside that spot benchmark; contributors are not publicly identified. A change in the index should therefore prompt investigation of availability and contract renewals. It cannot establish the repricing of every installed machine. [ornn-method]

The timing of exposure is decisive. A business that owns usable capacity and reprices frequently may benefit promptly. An operator that already sold capacity under a long contract may see little immediate upside. A model provider with committed supply could be insulated from a temporary spot spike, while a competitor relying on short-term capacity could face a higher bill. Contract structure determines whose earnings respond and when.

2. Translate the GPU-hour into a comparable task

A GPU-hour is a time-based input. A token is an output unit whose economic meaning depends on the model, workload and serving configuration. Even “one million tokens” is an incomplete product definition: input and output tokens can consume different resources, and cached requests are not equivalent to uncached generation.

Compute cost per million billable tokens = rental price per GPU-hour × GPU-hours required per million billable tokens

The second term must be measured at the required service level. Increasing concurrency can improve aggregate throughput while degrading the experience of an individual user. A lower-quality model or looser response-time limit can make a benchmark cheaper without delivering an equivalent product. MLCommons explicitly defines inference benchmarks through models, datasets, quality targets and scenario-specific metrics. Its Closed and Open divisions also permit different degrees of model flexibility. [mlcommons]

For commercial research, the comparable unit may be a successfully completed coding task, a generated video meeting a quality threshold, or an accepted business workflow. Token economics remain useful, but they should sit underneath a task-level view whenever the customer buys a result. More tokens generated can represent more productive work, more reasoning effort, or simply more verbosity.

Figure 3 below makes this distinction explicit with a scenario rather than a forecast. With hourly rent up 20%, unchanged throughput increases unit compute cost by 20%. A 40% throughput improvement instead lowers that cost by 14.3%. Neither outcome can be inferred from the rent increase alone.

3. EBITDA does not settle the return on the asset

The operator’s problem extends beyond renting or owning an accelerator. If hardware is owned, cash was committed before revenue arrived. Financing, economic obsolescence and replacement capacity still matter when a quarterly operating metric excludes them. If hardware is rented, the contractual bill may be visible in operating expense instead. Two businesses can report different margin structures while bearing related economic risks.

CoreWeave reported Q2 2026 revenue of $2.575bn and adjusted EBITDA of $1.510bn. Its GAAP operating loss was $49m and net loss was $626m. The reconciliation below shows where the differences arise, without treating accounting depreciation as current cash spending. [coreweave]

FIGURE 02 · EVIDENCE

A $1.51bn EBITDA headline ends at a $626m net loss

CoreWeave · Q2 2026 · USD million · a reconciliation, not a cash-flow bridge

Derived by reversing the issuer’s adjusted-EBITDA reconciliation. Depreciation is an accounting expense, not current cash capex. Start, subtotal and end bars are neutral.

Inspect the chart data and source
ItemAmount / changeRoleRunning total
Adjusted EBITDA1,510total1,510
Depreciation + amortization-1,393change117
Stock compensation-165change-48
Acquisition costs-1change-49
GAAP operating loss-49subtotal-49
Net interest expense-640change-689
Other income, net+125change-564
Income tax provision-62change-626
GAAP net loss-626total-626

Q2 2026, three months ended 30 June · USD million

Source: CoreWeave Q2 2026 results

This is not an argument that EBITDA is useless. It helps isolate an operating layer of the business. But the owner of a rapidly evolving asset base must eventually earn enough to service its obligations and sustain competitive capacity. A metric that removes depreciation cannot, on its own, answer whether the assets earn their replacement cost.

Depreciation is an estimate of expense allocation; replacement investment is an actual financing requirement that may occur on a different schedule. Maintenance capex and growth capex are also economically different, yet clean separation can be difficult when a new generation improves both capacity and efficiency. Analysts should test several useful-life and residual-value assumptions rather than substitute the accounting schedule for the investment thesis.

FIGURE 03 · SCENARIO

Productivity changes the cost conclusion

Illustration only · rental cost +20% · initial compute cost index = 100

Scenario arithmetic, not measured efficiency gains. Cost index = 120 ÷ (1 + throughput gain). With realized selling price down 10%, a 33.3% throughput gain is required to preserve the initial compute-only revenue-to-cost ratio. Other costs and quality are held constant.

Inspect the chart data and source
CategoryValue
No throughput gain120.0
10% throughput gain109.1
20% throughput gain100.0
40% throughput gain85.7

Illustrative scenarios, not observations · Cost index, baseline 100

Source: ConstraintAlpha calculation from explicitly stated assumptions

The hurdle becomes higher when selling prices fall. Under the chart’s assumptions, preserving the original compute-only revenue-to-cost ratio after a 10% selling-price decline requires throughput to rise 33.3%: 1.20 ÷ 0.90 − 1. Improving throughput by 20% merely holds compute unit cost flat; it does not offset the lower selling price. These are algebraic conditions, not predictions about any provider.

4. Read the contract before assigning the winner

QuestionWhy it changes the analysis
What exactly is committed?A specific GPU configuration, available capacity, billable hours and a service-level promise are different products.
Who pays for low utilization?Take-or-pay terms may shift volume risk, subject to enforceability and availability obligations. Usage pricing leaves more occupancy risk with the operator.
When can pricing reset?Spot rates can rise while legacy revenue remains fixed. Renewals reveal realized pricing power.
Who finances the infrastructure?Customer advances, equipment finance and corporate debt create different obligations and timing.
What happens at the next hardware generation?A fleet may remain commercially useful, require upgrades or face a lower renewal price. Residual value is a thesis variable.

The most attractive bottleneck owner is not necessarily the company with the highest headline rental price. Reliable availability, software integration and customer switching costs can support realized value, but their benefit has to exceed the cost of delivering them. Conversely, a cheaper service may have sound economics if it operates efficiently and fills otherwise idle capacity.

The counterargument to permanent scarcity deserves equal attention. New supply can arrive, workloads can migrate, and better software can reduce the resources needed for a comparable task. At the same time, lower task cost can stimulate additional demand. The balance cannot be settled by assuming either unlimited efficiency or unlimited consumption.

5. The evidence that would change our view

Research propositionEvidence that strengthens itEvidence that weakens it
Capacity owners capture scarcityHigher realized renewal rates alongside durable utilization and cash after sustaining capacity.Spot gains fail to reach contracts; occupancy or collections weaken.
Inference providers protect marginsLower cost per comparable task exceeds pricing pressure while service quality is retained.Discounting and workload complexity outpace efficiency.
The buildout is economically durableOperating assets monetize before financing and replacement requirements overwhelm returns.Commissioning slips, contracts weaken, or cash needs repeatedly exceed internally generated funds.

Monitor the chain in order: available capacity, paid utilization, realized pricing, task productivity, operating cash and sustaining investment. Each link should carry its own period, definition and source. A strong observation at one link should not fill an empty field elsewhere.

ConstraintAlpha view: Higher GPU rents are a reason to investigate. Sustainable value capture requires a fuller test of useful output, contractual risk allocation and lifetime asset returns. The scarce input matters; so does the cost of keeping it productive.

Sources and measurement boundaries

  1. Ornn Compute Price Index dashboardSettlement 26 October 2026 · Current GPU rental prices; snapshot reviewed 27 October 2026
  2. Ornn OCPI methodologyMethodology accessed 27 October 2026 · Sections 2 and 3: universe and calculation
  3. MLPerf Inference Datacenter benchmark definitionsAccessed 27 October 2026 · Scenarios, metrics, quality targets and divisions
  4. CoreWeave Q2 2026 results11 August 2026 · Three months ended 30 June 2026; net-loss to adjusted-EBITDA reconciliation

Evidence cutoff: 27 October 2026. Company figures are reported disclosures; benchmark observations are publisher data. Scenarios and calculations are identified separately. Research and information only, not personalized investment advice.