A reproducible comparison between Ornn's named H100 Volatility Index and gpu-memory.com's deployed volatility surface.
Illustrative launch-preview data. Live price tracking is not connected yet.
Accessed 2026-09-01 UTC · 10 tracked SKUs · 90d reference window
Illustrative price signals / launch preview
Explore
Source fields stay visible and dated. Parity, equivalence, and live-fetch claims remain outside scope.
Planned capability
Access date 2026-09-01 UTC. Ornn's formula is not published; the captured repository evidence anchors are the methodology doc and the H100 explainer brief, not a live Ornn feed.
Planned capability
Verbatim from the methodology (2026-09-01): the Ornn H100 Volatility Index references 'compute pricing' and 'OCPI price history' in their public launch but does not publish their formula; we are not claiming parity. Verbatim from the H100 brief: No claim that the Ornn H100 Volatility Index is the same methodology.
Planned capability
Annualized standard deviation of log-returns, 90d rolling window default. Formula published in docs/memorysites/price-tracker/gpu-volatility-methodology.md; the H100 explainer at briefs/gpu-memory/2026-08-27-h100-compute-volatility-explainer.md reproduces the caveat for the public reader.
Planned capability
10 tracked SKUs (A100, A40, B200, H100-NVL, H100-PCIe, H100-SXM, H200, L40S, RTX-4090, RTX-5090). Per-SKU snapshots live at pages/data/gpu-volatility/{slug}/{date}.json with an ISO-8601 as_of token and a 30-day series. Ornn's SKU coverage is UNKNOWN in the captured evidence beyond H100.
Planned capability
The planned page is dated evidence, not a live feed. Live-fetch is owned by the separate dom-3hi.4.5.9 work item (not adopted by this analysis). The volatility product epic is dom-3hi.4.5; method documentation is dom-3hi.4.5.6.
Planned capability
Ornn's formula, window, sampling cadence, data source set, and as_of timestamp are unknown (Ornn does not publish them). Per-SKU source attribution, provenance dossier, and no-parity caveat are preserved from the gpu-memory shipped surface.
The route is generated by the existing Pages build and is not a deployment claim. See the linked methodology and brief for the full no-parity caveat and the deployed formula.