Release Notes

AI Build Configurator Changelog

Every revision to the licensed model, what triggered it, and what it changes for licensees. Version 1.4.0 shipped on 1 October 2026 and is live on every licensed embed now: it adds the AMD Instinct line from MI300X to the Helios MI455X rack, GB200 NVL72 as its own option, a 26% GB300 repricing, the Virginia data centre electricity tax and a Q4 2026 province and state refresh. Version 1.3.2 shipped on 22 September 2026 and is live on every licensed embed now. It is a scheduled data-currency check: the reference exchange rate moved to 1.41 CAD per USD, and every provincial rate, US state rule, cost constant and accelerator price was checked against current sources and confirmed unchanged since the 16 September revision. Version 1.3.1, shipped 17 September 2026, tightened licence protection and added the data-vintage and exchange-rate notices to every result without changing a single figure. Version 1.3.0, shipped 16 September 2026, extended the model from nine Canadian provinces to all 50 US states and the District of Columbia. Provinces still price in Canadian dollars, states now price in US dollars, and state sales tax and large-load tariff rules are applied inside the calculation. Version 1.2.0, shipped 14 September, was the largest data revision since launch and tracks movement outside the software rather than a feature roadmap. Three Canadian regulators changed large-load policy inside six months, a new accelerator generation arrived at rack power levels the industry had not previously built for, and the operating expense breakdown was expanded to match how operators now report facility cost.

Version 1.4.0 — 1 October 2026

A feature and data release. Data vintage moves to Q4 2026 (rev. 1 Oct 2026). AMD Instinct joins NVIDIA in the accelerator list, GB200 NVL72 gets its own option, GB300 NVL72 is repriced, Virginia's new electricity consumption tax is modelled inside the energy cost, and provincial and state rules were checked against sources published through 30 September 2026. Licensees need to do nothing; existing embed code, licence keys and model() calls keep working.

v1.4.0 — Current

Released 1 October 2026 · data vintage Q4 2026 (rev. 1 Oct 2026) · governed by Licence Terms v1.2
  • AMD Instinct tier — MI300X, MI325X, MI350X, MI355X and the AMD Helios rack (MI455X), shown in their own AMD group in the accelerator selector
  • GB200 NVL72 added — its own rack-scale option at C$66,000 per accelerator, from ~US$3.1M bare to US$3.9M all-in per rack (SemiAnalysis)
  • GB300 NVL72 repriced +26% — C$97,000 per accelerator (was C$77,000), from August 2026 purchase orders near US$5.0M per rack; a material change for any GB300 build
  • Other NVIDIA classes refreshed — H100 C$49,000, H200 C$55,000, B200 C$67,000, B300 C$75,000, VR200 NVL72 C$147,000
  • Exchange-rate rebase — the reference rate stays at 1.41 CAD per USD (spot ran 1.41-1.42 in late September); fit-out, network and cooling constants, which are imported equipment, were rebased by 1.41/1.38 (+2.2%). Shell, land and utility lines are local costs and unchanged
  • Virginia electricity consumption tax — $0.011/kWh from 1 July 2026 (HB 30), applied to all metered energy and shown as its own row in the result, summary and CSV; capped at $600M a year and scheduled through 30 June 2028
  • Federal note — states in the six FERC-jurisdictional markets now show the June 2026 FERC show-cause orders and PJM's 13 August 50 MW+ large-load framework (curtailment ahead of other demand response from 1 June 2027 for loads without their own capacity)
  • Canada — Alberta (20,600 MW+ requested, BYOG intake slipped to later this fall), Ontario (draft Data Centre Playbook, queue 32 to 36 months), Quebec (13c/kWh rate still pending at the Regie), British Columbia (Call for Demand notifications sent, results not yet public)
  • United States — Texas permit halt and audit (queue 30 to 42 months), New York 50 MW moratorium (queue 42 to 54), Minnesota exemption repealed from 1 July 2026, Maine BETE exclusion (property index 1.10 to 1.40), Nevada EO 2026-005 (property index 0.90 to 1.10), Maryland 25 MW review, Virginia transmission and Prince William County rules, Florida, Washington and Milwaukee notes
AMD Instinct accelerators added in v1.4.0. Fully loaded cost per accelerator in CAD, including its share of CPU, NIC, chassis and interconnect.
AcceleratorPowerMemoryFully loaded costBasis
MI300X750 W192 GBC$31,500Estimate (no public list price)
MI325X1,000 W256 GBC$40,000Estimate (no public list price)
MI350X1,000 W air288 GBC$52,000~US$25K per GPU after the 2026 price rise, plus server share
MI355X1,400 W liquid288 GBC$53,000~US$25-30K per GPU plus server share
Helios MI455X2.3 kW, ~230 kW/rack432 GB HBM4C$102,000US$5.0-5.5M per 72-GPU rack; first shipments Q3 2026

Backwards compatibility: every existing accelerator, profile and region key is unchanged, so client embeds and model() calls need no action. State industrial power rates were deliberately left on the April 2026 index, because the latest EIA release reports July, a summer peak month. Questions: support@strategiccryptoreserve.ca.

Version 1.3.2 — 22 September 2026

A scheduled data-currency check, not a feature release. Data vintage moves to Q3 2026 (rev. 22 Sep 2026). The reference exchange rate is the only figure that changed; every provincial rate, US state rule, tax status, cost constant and accelerator price was re-checked against current sources and confirmed unchanged since the 16 September revision. Licensees need to do nothing; existing embed code and licence keys keep working.

v1.3.2 — Superseded

Released 22 September 2026 · data vintage Q3 2026 (rev. 22 Sep 2026) · governed by Licence Terms v1.2
  • Reference exchange rate refreshed — 1.41 CAD per USD (was 1.38), used to restate US-state figures and convert USD-quoted benchmarks; verified against current spot at time of release
  • Every dataset re-verified, not just rolled forward — Canadian provincial rates and queues, all 51 US state/DC rules, cost constants and every accelerator class were checked against current sources; none had changed since the 16 September revision
  • Calculations otherwise unchanged — no rate, tariff, tax rule, cost constant or accelerator class changed from v1.3.1 aside from the exchange rate

Only outputs for US states move, and only by the exchange-rate delta — every Canadian provincial figure is byte-for-byte identical to v1.3.1. Questions: support@strategiccryptoreserve.ca.

Version 1.3.1 — 17 September 2026

A licensing and notices release. Data vintage stays at Q3 2026 (rev. 16 Sep 2026), and every capital, energy, revenue and payback figure is identical to v1.3.0. Licensees need to do nothing; existing embed code and licence keys keep working.

v1.3.1 — Superseded

Released 17 September 2026 · data vintage Q3 2026 (rev. 16 Sep 2026) · governed by Licence Terms v1.2
  • Hashed licence registry — licence keys and authorised domains are stored as salted SHA-256 hashes in the hosted file, so licensee names, keys and domains are no longer readable in the script
  • Development hosts narrowed — the widget renders without a matching domain only on localhost and 127.0.0.1, as the licence terms describe; local files and private network addresses now need a licensed domain
  • Data-vintage and exchange-rate notice — every result footer, clipboard summary and CSV export now states the model version, data vintage and the 1.38 CAD per USD reference rate used to restate benchmarks for US states
  • Headless model access requires an Enterprise key — SCRAIBuild.model() now takes a key option and runs only for an Enterprise licence authorised on the calling domain
  • Public demo export — the demo on strategiccryptoreserve.ca still runs every Pro calculation, but CSV export is reserved for Pro and Enterprise licensees and the demo links to site screening reports
  • Brand attribute escaped — the data-brand value is HTML-escaped before display
  • Calculations unchanged — no rate, tariff, tax rule, cost constant or accelerator class changed from v1.3.0

Enterprise licensees calling the headless model should add their licence key: SCRAIBuild.model({ key: 'YOUR-KEY', profile: 'ai-factory', region: 'US-VA' }). Questions: support@strategiccryptoreserve.ca.

Version 1.3.0 at a Glance

Shipped 16 September 2026. Data vintage stamp moved from Q3 2026 (rev. 14 Sep 2026) to Q3 2026 (rev. 16 Sep 2026). Licensees need to do nothing.

v1.3.0

Released 16 September 2026 · data vintage Q3 2026 (rev. 16 Sep 2026)
  • United States coverage added — all 50 states and the District of Columbia, 51 new location datasets alongside the nine provinces
  • Currency follows the location — Canadian provinces return every figure in CAD; US states return every figure in USD, including the clipboard summary and CSV export
  • State power rates indexed to EIA state industrial averages, with PJM capacity pricing embedded where it applies
  • Equipment sales and use tax modelled wherever a state has no data centre exemption open to new projects, and itemised as its own capital line
  • Large-load take-or-pay tariffs modelled in eight states, including Dominion GS-5 in Virginia and the AEP Ohio data centre tariff
  • State construction location factor and property tax index applied to capital, staffing and carrying cost
  • Location selector grouped by country, embeds accept US-TX or plain TX, and the power rate slider extends to $0.45 for US states
  • Canadian outputs unchanged — every province, profile and accelerator combination returns exactly the v1.2.0 figures

What Changes When a US State Is Selected

Pick any province and the model behaves exactly as it did in v1.2.0, in Canadian dollars. Pick any state and the whole model switches to US rules and US dollars at once. Nothing is converted at the end as a display trick. Each input is restated in USD before the maths runs, and the state rules are applied inside the calculation.

Currency

The model's capital benchmarks, accelerator prices and staffing constants were originally derived from USD-quoted sources at 1.38 Canadian dollars per US dollar. For a US state, every one of those constants is divided by the same 1.38, which recovers the underlying USD benchmark rather than layering a second exchange-rate assumption on top. For reference, the ECB-derived reference rate was 0.7216 US dollars per Canadian dollar on 11 September 2026, or about 1.386. Default revenue rates are converted the same way. If a user has already moved the revenue slider and then switches country, the setting is carried across at the same rate rather than reset.

Power rate and queue

Each state carries an indicative large-load industrial rate in USD per kilowatt-hour and an indicative queue in months. Rates start from each state's EIA industrial average, indexed to the April 2026 US industrial mean of 8.66 cents. In the 13 PJM states and DC, capacity cost is already inside that rate; PJM's 2028/2029 auction cleared at the cap of roughly $325 per MW-day. Transmission-voltage loads usually settle below the state average, so the slider stays live for a negotiated figure.

Sales and use tax on equipment

When a state has no data centre exemption open to new projects, the model applies that state's combined state and average local sales tax to the taxable share of each capital line. That share is 60% of fit-out, 75% of cooling, 85% of network fabric and 100% of accelerators. Shell and land are treated as real property and excluded. The tax appears as its own row and bar in the widget and its own line in the CSV. In 2026 this is no longer a theoretical line: Arizona's exemption is closed to new applications until 30 June 2029, Illinois paused its incentives for two years from 1 July 2026, and Ohio stopped approving new ones on 27 May 2026.

Large-load take-or-pay tariffs

Where a utility bills large loads on a minimum-demand basis, the model never lets billed IT energy fall below the floor multiplied by full-load IT energy once the site passes the tariff threshold. At 88% utilisation the floor rarely binds. At lower utilisation it does, and the shortfall is shown as its own line. A 50 MW neocloud in Virginia at 60% utilisation carries about $10.4 million a year of take-or-pay energy under the modelled GS-5 floor. Under pass-through billing, the line is marked as the tenant's cost.

StateTariff modelledThresholdFloor
VirginiaDominion GS-5 (from 1 January 2027; 14-year contracts, 85% T&D and 60% generation minimum demand)25 MW85%
OhioAEP Ohio data centre tariff (85% take-or-pay on contracted capacity)25 MW85%
OregonPOWER Act large-load class20 MW80%
New JerseyVery-large-customer service rules (threshold not specified in statute; modelled at 50 MW)50 MW80%
IndianaI&M large-load settlement70 MW80%
Kansas and MissouriEvergy large-load power service75 MW80%
GeorgiaGeorgia PSC large-load rule100 MW80%

Virginia uses the published 85% transmission and distribution floor, which is the more demanding of its two components. Floors of 80% are planning assumptions where a published blended figure is not directly comparable.

Construction cost, property tax and staffing

Shell, fit-out, cooling, network and staffing are multiplied by a state construction location factor, with the US national level at 1.00. The range runs from 0.86 in Arkansas and Mississippi to 1.30 in Hawaii. Property tax and insurance are scaled by a state index, from 0.60 in Delaware, Alabama and Hawaii to 1.40 in Illinois and New Jersey. Montana's special data centre property classification is reflected at 0.70.

The same builds, side by side

Default settings, 50 MW of IT load, 88% utilisation, B200-class accelerators. Canadian rows are in CAD and US rows in USD, so compare shapes across the border rather than raw figures.

LocationCurrencyPowered shell CapExPowered shell EBITDA / yrNeocloud CapExof which sales/use taxNeocloud EBITDA / yrShell build + queue
British ColumbiaCAD$872M$85.1M$3,188M—$768.0M66 mo
TexasUSD$572M$59.9M$2,232M—$549.1M60 mo
GeorgiaUSD$572M$62.1M$2,232M—$546.7M66 mo
VirginiaUSD$602M$60.8M$2,271M—$538.1M78 mo
OhioUSD$617M$61.2M$2,404M$125.2M$539.2M72 mo
ArizonaUSD$595M$62.0M$2,395M$146.5M$537.7M72 mo
New YorkUSD$778M$55.8M$2,635M$152.6M$531.1M72 mo
CaliforniaUSD$779M$57.6M$2,640M$158.3M$476.1M78 mo

The pattern is the point. For a neocloud that buys its own silicon, a closed sales tax exemption adds $125 to $160 million to a 50 MW build. That is a bigger swing than the gap between the cheapest and the median power rate. The full 51-row state table, with rate, queue, tax status, tariff and construction factor for every state, is on the AI data center economics page.

Equipment tax status as modelled for new projects

Exemption open (30 states): Alabama, Arkansas, Connecticut, Florida, Georgia, Idaho, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maine, Maryland, Michigan, Minnesota, Mississippi, Missouri, Nevada, North Carolina, North Dakota, Pennsylvania, South Carolina, Tennessee, Texas, Utah, Virginia, Washington, West Virginia, Wisconsin and Wyoming.

Paused or closed to new projects, so tax is modelled (7): Arizona, Illinois, Massachusetts, Nebraska, New Jersey, Ohio and Oklahoma.

No data centre exemption, so tax is modelled (10): Alaska, California, Colorado, the District of Columbia, Hawaii, New Mexico, New York, Rhode Island, South Dakota and Vermont.

No state sales tax (4): Delaware, Montana, New Hampshire and Oregon.

Several "open" states are under active review. Texas lists repeal of its exemption among the governor's 2027 priorities, Virginia's legislature is weighing an impact fee, North Carolina has repealed its electricity exemption with a broader phase-out proposed, and Georgia, Maryland, Michigan and Pennsylvania all saw repeal or moratorium bills in 2026. The hosted file will be revised as each lands.
Currency: key points illustration, AI Build Configurator Changelog Currency: AI Build Configurator Changelog Power rate and queue: AI Build Configurator Changelog Sales and use tax on equipment: AI Build Configurator Changelog Large-load take-or-pay tariffs: AI Build Configurator Changelog Large-load take-or-pay tariffs: AI Build Configurator Changelog Construction cost, property tax and staffing: AI Build Configurator Changelog The same builds, side by side: AI Build Configurator Changelog

v1.3.0 Backwards Compatibility and Pre-Release Verification

Before v1.3.0 replaced the hosted file, both live licences were mounted in a browser environment. The full model was then swept across every location. These are the checks that were run.

CheckExpectedResult
Licence registry contentsUnchanged from v1.2.0Byte-for-byte identical
Pro-tier licence on its authorised domainSeven profiles, CSV button, 60 locations, opens in CADPass
Standard-tier licence opening on a US state and requesting a pro-only profileThree profiles, no CSV, opens in New York in USDPass
Province embed (data-region="ON")Opens in Ontario, figures in CADPass
Plain state code (data-region="TX")Maps to US-TX, figures in USDPass
Unrecognised region codeSilent fallback to British ColumbiaPass
Valid key on an unauthorised domainRefused with reasonPass
Unrecognised keyRefused with reasonPass
Canadian outputs against v1.2.0Identical CapEx and EBITDA0 differences across 441 profile, province and accelerator combinations
Full model sweepNo non-finite output; currency correct on every run23,520 runs (7 profiles × 60 locations × 7 accelerators × 4 cooling × 2 billing modes), 0 failures
Currency round trip on the revenue sliderCAD → USD → CAD returns the user's setting175 → 125 → 175, Pass
Build profile, province, cooling and accelerator keysNone removedNone removed; 51 location keys added

One input range changed: the power rate slider extends to $0.450 per kilowatt-hour when a US state is selected, to accommodate Hawaii. Provinces keep the $0.220 ceiling. No existing embed's default state changed.

What v1.3.0 Means by Licence Tier

  1. Standard. All 51 US locations are live on your three lease-model configurations, in USD, with state tax and tariff rules applied. The clipboard summary now states the currency and, where relevant, the sales tax and large-load tariff. No action required.
  2. Pro. Everything above across all seven configurations. The CSV export gains six rows. Country, Currency, Construction location factor, Large-load tariff and Take-or-pay energy cost follow the Utility row, and Sales and use tax on equipment follows Accelerator capex. Every currency column now reads CAD or USD to match the location. The rows also appear on Canadian exports with neutral values (CA, CAD, 1, n/a, 0).
  3. Enterprise. Everything above. Pinned cost constants stay in CAD and are converted at 1.38 for US locations, then multiplied by the state location factor. If your pinned basis is already a US-dollar basis, tell us and we will set it per country. Custom US sites, utility territories or negotiated rates can be added per licence key.
The same narrow breaking risk as last release, in a new place. If you parse the CSV export by row position, six new rows now sit above the capital block. This applies to Canadian exports as well as US ones. Parsing by the label in the first column is unaffected. This affects pro and enterprise licensees only.
What v1.3.0 Means by Licence Tier: key points illustration, AI Build Configurator Changelog What v1.3.0 Means by Licence Tier: AI Build Configurator Changelog

Engineering Note — 16 September 2026

Version 1.2.0 tracked three regulatory changes in Canada. Version 1.3.0 responds to a different kind of movement. Licensees and prospects kept bringing us sites south of the border, and US data centre policy moved faster in 2026 than in any year the model has existed.

The design constraint was that a province must not change. Every Canadian figure in v1.3.0 is identical to v1.2.0, which we verified by running both files side by side across every province, profile and accelerator. The US layer sits alongside the Canadian data rather than replacing it. Its constants are the same USD benchmarks the Canadian figures were built from, restated in their original currency rather than converted twice.

Power price turned out to be the least interesting variable in the US data. The gap between the cheapest and the median state rate is smaller than the effect of one closed tax exemption on a build that owns its silicon. It is also smaller than the effect of an 85% take-or-pay floor on a site running below plan. Arizona, Illinois and Ohio all pulled back incentives inside a few weeks this summer, and Virginia's GS-5 class takes effect in January. A US model that ignored tax and tariff structure would be precise about the wrong thing.

We have been deliberate about what we do not model. County and municipal abatements, negotiated deal by deal, are not in the file. Nor are water rights, fibre routes or demand-charge structures beyond the take-or-pay floor. State averages are a starting point for a screening conversation, and the sliders stay live for the numbers a utility actually quotes.

These numbers will move quickly. Texas has repeal of its exemption on the 2027 agenda, several states have moratorium bills circulating, and PJM's next auction is in December. When those land, the hosted file is replaced and every embed picks it up on the next page load.

— SCR Engineering, Strategic Crypto Reserve

Engineering Note — 16 September 2026: key points illustration, AI Build Configurator Changelog Engineering Note — 16 September 2026: AI Build Configurator Changelog

How the US Numbers Were Sourced

State policy status reflects actions reported through August 2026. State power rates start from EIA state industrial averages indexed to the 2026 national industrial mean. They are planning constants, not month-specific tariff quotes. Where a tariff floor or threshold is a modelling assumption rather than a published figure, it is labelled as one above.

  • U.S. Energy Information Administration, Electric Power Monthly, Table 5.6.A — state industrial average prices and the April 2026 national industrial average
  • PJM Interconnection, 2028/2029 Base Residual Auction results, July 2026, and the capacity price cap and floor extended through the December 2026 auction
  • Virginia State Corporation Commission, final order in Dominion Energy Virginia's 2025 biennial review — GS-5 rate class
  • Public Utilities Commission of Ohio, AEP Ohio data centre tariff approved July 2025
  • Texas Senate Bill 6 (2025) large-load interconnection and curtailment provisions, and the governor's 2026 direction to the PUCT
  • State data centre incentive actions in 2026 as reported by the National Conference of State Legislatures, MultiState, Thomson Reuters Tax & Accounting and Telecompetitor — including the Arizona moratorium, Illinois, Ohio and Nebraska pauses, the Massachusetts closure, the New Jersey freeze, the Oklahoma sunset and the Washington changes of 1 July 2026
  • Published combined state and average local sales tax rates
  • Published construction city cost indices, rebased to US national = 1.00
  • European Central Bank reference rates for CAD/USD, 11 September 2026
How the US Numbers Were Sourced: key points illustration, AI Build Configurator Changelog How the US Numbers Were Sourced: AI Build Configurator Changelog

Version 1.2.0 at a Glance — 14 September 2026

Shipped 14 September 2026. Data vintage stamp moved from September 2026 to Q3 2026 (rev. 14 Sep 2026). Licensees needed to do nothing.

v1.2.0 — Superseded

Released 14 September 2026 · data vintage Q3 2026
  • Provincial power data revised across all nine jurisdictions, with three of them changing for regulatory rather than price reasons
  • Capital cost benchmarks raised on every build profile to track published 2026 construction indices
  • Liquid cooling density ceiling lifted from 140 to 250 kW per rack, immersion from 220 to 300
  • Accelerator table rebuilt around GB300 NVL72 and Vera Rubin VR200, with two new classes added
  • Expanded operating expense breakdown separating property tax, insurance and general administration
  • Build timelines extended on every profile to reflect current equipment lead times
  • Two input sliders widened because the new data exceeded their old ranges
  • Full backwards compatibility — no key removed, no attribute changed, both live licences verified rendering before release

v1.0.1 — Superseded

Released 4 September 2026 · data vintage September 2026
  • Initial public release of the licensed widget
  • Seven build profiles, nine provincial datasets, four cooling architectures, five accelerator classes
  • Per-domain licence validation, tier gating, CSV export and clipboard summary

v1.2.0: What Licensees Need to Do

Nothing. That is not a throwaway line, it is the reason the product is structured the way it is.

The entire model — every cost constant, every provincial rate, every interconnection queue estimate, every accelerator specification — lives in one hosted JavaScript file on our server. A licensed embed is two elements on your page: a container div carrying your key, and a script tag pointing at our file. When we replace that file, your page serves the new model on its next load. There is no package to update, no build to run, no snippet to re-paste, and no version drift between licensees.

That matters more than it sounds. The failure mode for a cost calculator is not that it breaks. It is that it quietly keeps working while the numbers behind it go stale, and a consultant puts a five-year-old power rate in front of a client who knows better. Central hosting means that cannot happen to a licensee, because there is no stale copy to run.

Your licence is untouched. Keys, authorised domain lists, tier entitlements and expiry dates were not modified in this release. The licence registry is byte-for-byte identical to v1.0.1. If your embed worked on 13 September, it works on 15 September, with better numbers in it.

The one thing worth checking is your own copy. If you have published prose alongside the widget that quotes specific outputs — a blog post citing a cost per megawatt, a proposal template with a payback figure, a case study with a capital number — that text is now out of step with the tool sitting next to it. The widget updated. Your paragraph did not. Search your site for hard-coded figures before your next client meeting.

v1.2.0: What Licensees Need to Do: key points illustration, AI Build Configurator Changelog v1.2.0: What Licensees Need to Do: AI Build Configurator Changelog

v1.2.0: Provincial Power Data — the Headline Change

Power is the recurring value of the subscription. It is also the part of the model that moves for reasons nobody controls. Three provinces changed in ways that alter site selection logic, not just arithmetic.

Quebec was repriced, and it is the biggest single change in the release

Hydro-Quebec filed a dedicated rate for large data centres with the Regie de l'energie averaging 13 cents per kilowatt hour — roughly double what large-power customers pay today. It applies to facilities above 5 megawatts, is expected in force in the second half of 2026 subject to approval, and applies automatically to all new customers in the segment. Sites already connected transition to it over five years.

Alongside it, the utility proposed moving the rate for cryptographic use applied to blockchains to an average of 19.5 cents per kilowatt hour, with a three-year transition for existing customers, on the reasoning that the activity is energy intensive with limited economic return to the province.

The model moved Quebec from 5.5 cents to 13.0 cents. The practical effect is blunt: run the hybrid mining and AI profile against Quebec now and it returns negative EBITDA. That is not a modelling artefact, it is the correct signal. Under a 19.5 cent blockchain tariff the hashing side of a hybrid site does not clear its own power cost. Quebec has spent two decades as the reflexive answer to "where should we put it," and for this class of load that answer has changed. Anyone still running a Quebec hybrid thesis on 2024 numbers is working from a document that a regulator has already overtaken.

British Columbia cancelled the rate schedule the old figure was based on

Rate Schedule 1823, the stepped transmission rate, closed to all customers at the end of the fiscal 2026 billing year, and any remaining customers were moved to Rate Schedule 1830. RS 1830 is now the default transmission service rate, and from 1 April 2026 its three separate energy charges were consolidated into a single charge. The current structure is 4.914 cents per kilowatt hour on all energy, plus a demand charge of $12.178 per kVA of billing demand. Bills across the board rose roughly 3.75 percent on the same date.

For a high load factor data centre, that demand charge spreads across a lot of kilowatt hours and blends out near 6.6 cents. That is the figure the model now carries, up from 6.2 cents, and it is derived from the published tariff components rather than a rounded industry estimate.

The queue estimate moved more than the rate did. BC Hydro's process for emerging industries is a competitive allocation, not a queue — applicants compete for a finite block of capacity rather than waiting their turn. The utility received 15 applications representing close to 800 megawatts of requested load, with successful applicants notified from mid-September 2026. The model now carries 36 months for BC and flags the region as allocation-constrained, because the honest answer to "how long is the wait" in British Columbia is that there may not be a wait, there may be a refusal.

Alberta is no longer the fast lane, and v1.0 said it was

This is the province-wide change that most affects how the tool advises. Alberta spent years as the fastest interconnection path in Canada, and the model carried a 14-month queue on that basis. Provincial policy has since moved decisively.

The Alberta Electric System Operator's Phase 1 large-load allocation was capped at approximately 1,200 megawatts, and that cap was fully allocated to two projects with in-service dates in 2027 and 2028. Meanwhile the connection project list still carries roughly 19,500 megawatts of requested data load across dozens of projects. Phase 2 of the Large Load Integration programme is developing the long-term framework covering connections, planning, operations, markets and tariff, without a published completion timeline. In June 2026 the province filed a Data Centre Regulation creating a framework for loads of 75 megawatts and above, and the system operator has been building out a bring-your-own-generation pathway as the practical route for capacity beyond the interim cap.

So the queue went from 14 months to 26, and the region flag changed from fast to byog. Alberta is still a serious answer — but the answer now involves generation you bring yourself, regulatory approval for that generation, and emissions permitting, not simply a faster interconnect.

On Alberta pricing. Pool prices averaged roughly $32 per megawatt hour in the first quarter of 2026, which looks cheap. Power for delivery in 2029 was trading closer to $63 per megawatt hour. A ten-year model built on a soft spot price is a model that flatters itself. The widget's default sits above spot deliberately, and licensees modelling long-term Alberta positions should override it with the forward curve rather than the headline.

Every province, before and after

Provincev1.0.1 ratev1.2.0 rateQueue changeWhy
Quebec$0.055$0.13036 mo (no change)New large data centre tariff filed; blockchain rate proposed at 19.5c
Nova Scotia$0.115$0.12024 → 26 moRate drift and tighter capacity
Ontario$0.098$0.10230 → 32 moRate drift; Global Adjustment still the dominant variable
Saskatchewan$0.084$0.08824 mo (no change)Rate drift
New Brunswick$0.081$0.08420 mo (no change)Rate drift; now the fastest realistic Canadian path at modest scale
Alberta$0.078$0.08014 → 26 moPhase 1 cap fully allocated; BYOG now the practical route
Newfoundland & Labrador$0.068$0.07028 mo (no change)Rate drift; transmission and fibre still the limiters
British Columbia$0.062$0.06630 → 36 moRS 1823 cancelled, RS 1830 now default; competitive allocation
Manitoba$0.051$0.05526 → 28 moStill the cheapest industrial power in the model

Rates are indicative blended all-in industrial figures in Canadian dollars per kilowatt hour at high load factor, for screening purposes. They are not tariff quotes. Every licensee should verify against the applicable rate schedule and their own load profile before a rate reaches a client document.

Quebec was repriced, and it is the biggest single change in the release: key points illustration, AI Build Configurator Changelog Quebec was repriced, and it is the biggest single change in the release: AI Build Configurator Changelog Quebec was repriced, and it is the biggest single change in the release: AI Build Configurator Changelog British Columbia cancelled the rate schedule the old figure was based on: AI Build Configurator Changelog British Columbia cancelled the rate schedule the old figure was based on: AI Build Configurator Changelog Alberta is no longer the fast lane, and v1.0 said it was: AI Build Configurator Changelog Alberta is no longer the fast lane, and v1.0 said it was: AI Build Configurator Changelog Every province, before and after: AI Build Configurator Changelog

v1.2.0: Capital Cost Benchmarks

Construction costs moved in one direction across every published index we track, and the model moved with them. The global average shell-and-core construction cost for a single-tenant facility reached roughly $11.3 million US per megawatt in 2026, up from $7.7 million in 2020 — a 47 percent increase in six years that has almost nothing to do with general inflation and almost everything to do with electrical density, liquid cooling, redundant power trains and testing regimes. AI-optimised facilities run materially higher, with all-in figures for a deliverable megawatt commonly quoted between $20 million and $37 million US.

Every profile's shell, fit-out, land, utility contribution and network lines were raised. Soft costs moved from 8 percent of hard cost to 9 percent. The stabilised-asset valuation multiple came down from 15 times EBITDA to 14, reflecting deal multiples compressing through 2026 even as transaction volume set records.

Build profileShell & core, v1.0.1Shell & core, v1.2.0Build months
Hyperscale AI Factory$20.0M / MW$23.0M / MW34 → 38
Neocloud / GPU-as-a-Service$9.0M / MW$10.5M / MW16 → 20
Powered Shell$8.5M / MW$10.0M / MW26 → 30
Bitcoin Miner Retrofit$6.0M / MW$7.0M / MW18 → 20
Modular / Prefabricated$11.0M / MW$12.5M / MW9 → 11
Edge / Micro Deployment$22.0M / MW$24.0M / MW6 → 8
Hybrid Mining + AI$5.5M / MW$6.5M / MW14 → 16

Why every build timeline got longer

Not because construction got slower. Because procurement did. Medium-voltage switchgear has been running lead times around 22 months. High-capacity transformers sit near 18. The average across critical components is longer still. Against that backdrop, a meaningful majority of data centre projects in 2025 slipped at least three months from their original schedule.

The build duration figures in the model already assume competent procurement rather than luck, and they are added to the provincial queue to produce a single time-to-first-revenue number. Version 1.2.0 also exposes the underlying lead time assumptions through the public API so that enterprise licensees integrating the engine into their own reporting can sanity-check a schedule a client brings them against the same figures the model uses.

Why every build timeline got longer: key points illustration, AI Build Configurator Changelog v1.2.0: Capital Cost Benchmarks: AI Build Configurator Changelog Why every build timeline got longer: AI Build Configurator Changelog Why every build timeline got longer: AI Build Configurator Changelog

v1.2.0: Cooling Ceilings and Accelerator Classes

This change tracks a step-change in rack power across the industry rather than a refinement of an estimate.

Version 1.0 capped direct-to-chip liquid cooling at 140 kilowatts per rack, reflecting a GB200-class reference deployment. The industry has moved well past that ceiling. GB300 NVL72 sits at roughly 140 kilowatts per rack on its own, and the Vera Rubin VR200 NVL72 ships in two power profiles — Max Q at roughly 1.8 kilowatts per GPU and 190 kilowatts per rack, and Max P at roughly 2.3 kilowatts per GPU and 230 kilowatts per rack. Vendor rack specifications for Vera Rubin pods quote rack power consumption up to 240 kilowatts. A 140 kilowatt ceiling cannot represent the hardware now being ordered.

Density ceilings were raised accordingly, and the incremental cooling capital cost was raised with them. Liquid cooling typically adds somewhere in the range of 7 to 10 percent to total build cost versus a comparable air-cooled facility, and it re-weights the budget — mechanical systems rise from roughly 22 percent of facility cost to roughly 33 percent while electrical falls. Expressed per megawatt, the liquid premium lands in the low single-digit millions.

Cooling architecturePUEDensity ceilingIncremental capex
Air-cooled / hot-aisle containment1.38 → 1.4050 kW (no change)Baseline
Rear-door heat exchanger1.25 → 1.2480 → 90 kW$0.9M → $1.4M / MW
Direct-to-chip liquid (DLC)1.15 → 1.13140 → 250 kW$1.8M → $3.6M / MW
Single-phase immersion1.08 → 1.06220 → 300 kW$2.6M → $4.4M / MW

The air-cooled PUE moved upward deliberately, tracking measured industry performance. Facilities at 20 megawatts and above averaged a PUE around 1.44 globally in 2025, so the model now sits closer to that observed figure and reports a power bill reflecting how these halls actually run.

The accelerator table, rebuilt

Two existing keys were repointed at current silicon rather than removed, so no embed anywhere breaks. Two new classes were added. Unit costs are now expressed as fully loaded cost per accelerator — the GPU plus its share of CPU, NIC, storage, chassis and rack-scale interconnect — derived from published system and rack prices, which is the number that actually hits a capital plan.

Keyv1.2.0 classPer-accelerator drawLoaded cost (CAD)Status
h100H100-class700 W$48,000Repriced from $38,000
h200H200-class, high bandwidth700 W$54,000Repriced from $45,000
b200B200-class liquid1,200 W$66,000Repriced from $62,000
b300B300 / Blackwell Ultra1,400 W$74,000New in v1.2.0
nvl72GB300 NVL72 rack-scale, ~140 kW/rack1,400 W$77,000Key retained, repointed
nextVR200 NVL72 Max Q, ~190 kW/rack1,800 W$145,000Key retained, repointed
vr200pVR200 NVL72 Max P, ~230 kW/rack2,300 W$145,000New in v1.2.0

Rubin-generation pricing is the softest data in the release and is labelled as such in the source file. Channel quotes for a VR200 NVL72 rack have circulated between roughly $5 million and $7 million US, while a widely cited May 2026 sell-side estimate put the figure nearer $7.8 million, with memory alone accounting for around a quarter of system cost after a very large increase in high-bandwidth memory pricing. The model carries a figure inside that band. Licensees modelling a Rubin deployment against a real quote should override it.

What the density change does to your outputs. Selecting a Vera Rubin class at high density produces far fewer, far more expensive accelerators for the same megawatt. That is correct, and it is the useful insight: at rack-scale Rubin economics, the constraint stops being how much silicon you can afford and becomes how much power you can get delivered to a single rack footprint. The tool now surfaces that trade-off rather than capping the input below what the current hardware generation draws.
The accelerator table, rebuilt: key points illustration, AI Build Configurator Changelog v1.2.0: Cooling Ceilings and Accelerator Classes: AI Build Configurator Changelog v1.2.0: Cooling Ceilings and Accelerator Classes: AI Build Configurator Changelog v1.2.0: Cooling Ceilings and Accelerator Classes: AI Build Configurator Changelog The accelerator table, rebuilt: AI Build Configurator Changelog The accelerator table, rebuilt: AI Build Configurator Changelog

v1.2.0: An Expanded Operating Expense Model

Operating expense reporting across the sector has become considerably more granular through 2026. Lease disclosures, operator filings and colocation cost surveys now routinely separate facility operating cost from the carrying cost of the asset and the overhead of the business running it. Version 1.2.0 brings the model's operating expense breakdown into line with that convention.

Version 1.0 grouped operating expense into three lines: electricity, maintenance as a percentage of capital, and staffing. Version 1.2.0 adds a fourth covering property tax, insurance and general administration, set per profile as a per-megawatt charge plus a percentage of revenue. It appears in the widget's operating expense breakdown, in the clipboard summary, and as two separate rows in the CSV export.

The effect on reported margin varies by commercial structure, and that variation is the useful part. A powered shell with power passed through to the tenant genuinely carries very low operating cost against its rent — one publicly disclosed figure from a large lease put pure facility operating cost near $15 US per kilowatt per month against wholesale rent in the high $100s. Structures that own silicon, employ technical staff and sell compute hours carry materially more. Breaking the fourth line out lets the model show that spread across the seven profiles rather than flattening it into a single number.

Build profilev1.0.1 EBITDA marginv1.2.0 EBITDA margin
Hyperscale AI Factory83%77%
Neocloud / GPU-as-a-Service86%75%
Powered Shell85%73%
Edge / Micro Deployment83%73%
Modular / Prefabricated64%53%
Bitcoin Miner Retrofit54%43%
Hybrid Mining + AI43%31%

Payback periods lengthened correspondingly. A 50 megawatt powered shell in British Columbia moved from roughly 8.7 years to roughly 10.2. A 20 megawatt neocloud moved from 3.6 years to 4.2.

Licensees who have quoted a margin or payback figure from the previous model inside a live document should refresh it against the current output. The revised range reflects both the expanded expense breakdown and the capital benchmark movement described above, and it is the range that will stand up in a room with a chief financial officer in it.

v1.2.0: An Expanded Operating Expense Model: key points illustration, AI Build Configurator Changelog v1.2.0: An Expanded Operating Expense Model: AI Build Configurator Changelog v1.2.0: An Expanded Operating Expense Model: AI Build Configurator Changelog

v1.2.0 Backwards Compatibility and Pre-Release Verification

Before v1.2.0 replaced the hosted file, every live licence was rendered in a real browser environment and checked against expected behaviour. These are the actual checks that were run.

CheckExpectedResult
Licence registry contentsUnchanged from v1.0.1Byte-for-byte identical
Pro-tier licence on its authorised domainRenders, seven profiles, CSV button presentPass
Standard-tier licence on its authorised domainRenders, three profiles, CSV button absentPass
Standard tier requesting a pro-only profileSilent fallback, no errorPass
Legacy embed using data-accel="nvl72"Renders against repointed classPass
Valid key on an unauthorised domainRefused with reasonPass
Unrecognised keyRefused with reasonPass
Build profile keysNone removedNone removed
Province keysNone removedNone removed
Cooling architecture keysNone removedNone removed
Accelerator keysNone removedNone removed; two added
Embed data attributesAll six parse identicallyPass
Tier gating profile listUnchangedUnchanged

Two input ranges were widened because the new data exceeded them: the power rate slider now extends to $0.220 per kilowatt hour to accommodate Quebec's proposed blockchain tariff, and the accelerator-hour revenue slider now extends to $12.00 to accommodate current rack-scale rate cards. Neither change affects an existing embed's default state.

What v1.2.0 Means by Licence Tier

  1. Standard. All revised provincial data, all revised capital benchmarks, the new operating expense line and the new accelerator classes are live in your three lease-model configurations. Your profile list is unchanged. Clipboard summary now includes the new operating expense figures. No action required.
  2. Pro. Everything above, across all seven configurations, plus two additional columns in the CSV export breaking out property tax and insurance separately from general and administrative cost. If you have built a downstream template or spreadsheet that parses our CSV by row position rather than by label, check it — two rows were inserted into the operating expense block.
  3. Enterprise. Everything above, plus the newly exposed lead-time constants through the public API for firms integrating the engine into their own reporting. If your cost constants are pinned to an internally agreed basis, your pinned values are unaffected by the benchmark revisions — but the new operating expense category will apply unless you override it, and the density ceilings and accelerator classes have moved underneath your pins. Worth a review call.
One genuine breaking risk, and it is narrow. If you parse the CSV export positionally, two new rows now sit inside the operating expense block. Parsing by the label in the first column is unaffected. This is the only change in the release with any potential to disturb a downstream integration, and it affects pro and enterprise licensees only.
What v1.2.0 Means by Licence Tier: key points illustration, AI Build Configurator Changelog What v1.2.0 Means by Licence Tier: AI Build Configurator Changelog

Engineering Note — 14 September 2026

This release tracks three separate changes in Canadian large-load policy that landed inside six months. BC Hydro concluded Rate Schedule 1823 and moved transmission customers onto RS 1830 effective 1 April 2026, consolidating its energy charges in the process. Hydro-Quebec filed a dedicated large data centre tariff with the Regie de l'energie that roughly doubles the rate for the segment, alongside a separate proposed rate for cryptographic use. Alberta's interim large-load allocation was fully taken up, and the province filed a Data Centre Regulation covering loads of 75 megawatts and above. Any one of those would trigger a data review on its own. Three together warranted a full pass across the model.

Hardware moved on a similar timescale. A 140 kilowatt per rack ceiling on direct-to-chip liquid cooling reflected a GB200-class reference deployment, which was the industry standard when the model was built. Vera Rubin now ships in a Max P power profile at roughly 230 kilowatts per rack, with vendor pod specifications quoting up to 240 and Rubin Ultra figures already circulating well beyond that. Provincial power allocation and rack-level power density have effectively become the same conversation, and the model needed headroom to represent it.

The operating expense breakdown was expanded in the same pass. Sector reporting has moved steadily toward separating facility operating cost from asset carrying cost and business overhead, and the widget now follows that convention with property tax, insurance and general administration shown as a distinct fourth line in the widget, the clipboard summary and the CSV export.

Everything in this release was verified before the hosted file was replaced. Both live licences were mounted in a real browser environment and checked for correct rendering, correct tier gating and correct refusal against unauthorised domains and unrecognised keys. The full model was swept across all seven profiles, all nine provinces and all seven accelerator classes checking for non-finite outputs. The licence registry was diffed and confirmed unchanged. No licensee needed to be told to do anything, which is the entire point of hosting the model centrally.

Numbers will move again. Quebec's filing remains subject to the Regie. Alberta's Phase 2 framework has no published completion date. Rubin pricing is quoted across a wide band and will firm up as volume ships. When those land, the hosted file is replaced and every embed picks it up on the next page load.

— SCR Engineering, Strategic Crypto Reserve

Engineering Note — 14 September 2026: key points illustration, AI Build Configurator Changelog Engineering Note — 14 September 2026: AI Build Configurator Changelog Engineering Note — 14 September 2026: AI Build Configurator Changelog

How the v1.2.0 Canadian Numbers Were Sourced

Provincial rate data is taken from published utility tariffs and regulatory filings wherever a published figure exists, and from the utility's own rate design documentation where it does not. Construction benchmarks come from published 2026 industry cost indices. Accelerator specifications come from vendor and system-integrator published rack specifications. Pricing for shipping silicon comes from published rate cards and system prices; pricing for pre-volume silicon is a band, and is labelled as a band in the source file.

  • BC Hydro transmission rate schedules, fiscal 2027 updates effective 1 April 2026 — RS 1823 conclusion, RS 1830 energy and demand charges
  • BC Hydro emerging industries connections process — application volume and notification timing
  • Hydro-Quebec filing to the Regie de l'energie, February 2026 — proposed large data centre rate and cryptographic use rate
  • Alberta Electric System Operator Large Load Integration programme materials and connection project reporting
  • Alberta Data Centre Regulation, filed 9 June 2026
  • Published 2026 global data centre construction cost indices for shell-and-core and AI-optimised per-megawatt benchmarks
  • Published cost-structure analysis on the air-cooled to liquid-cooled budget shift
  • Published operator and vendor rack specifications for GB300 NVL72 and Vera Rubin VR200 NVL72 power profiles
  • Published cloud GPU rate cards and system pricing for accelerator cost and revenue calibration
  • Published wholesale colocation asking-rate surveys for North American primary markets

Every figure in the model is a planning-grade screening estimate. Rates, queues, allocation policy and silicon pricing change without notice. Nothing on this page or in the widget is an engineering estimate, a utility commitment, a price quote, or financial advice.

How the v1.2.0 Canadian Numbers Were Sourced: key points illustration, AI Build Configurator Changelog How the v1.2.0 Canadian Numbers Were Sourced: AI Build Configurator Changelog How the v1.2.0 Canadian Numbers Were Sourced: AI Build Configurator Changelog

Frequently Asked Questions

What changed in version 1.4.0?

Version 1.4.0, released 1 October 2026, adds five AMD Instinct accelerators (MI300X, MI325X, MI350X, MI355X and the Helios MI455X rack) and GB200 NVL72 as its own option, reprices GB300 NVL72 by 26% to C$97,000 per accelerator from August 2026 purchase orders, and rebases the import-heavy cost constants for the weaker Canadian dollar while keeping the reference rate at 1.41 CAD per USD. It also models Virginia's new $0.011/kWh data centre electricity consumption tax inside the energy cost, adds a FERC and PJM large-load note for states in FERC-regulated markets, and refreshes Alberta, Ontario, Quebec, British Columbia and ten US states. No keys changed, so existing embeds and model() calls keep working without any action.

What changed in version 1.3.2?

Version 1.3.2, released 22 September 2026, is a scheduled data-currency check rather than a feature release. The reference exchange rate moved to 1.41 CAD per USD, which is the only figure that changed; every Canadian provincial rate, US state rule, tax status, cost constant and accelerator price was re-checked against current sources and confirmed unchanged since the 16 September revision. Canadian provincial outputs are byte-for-byte identical to v1.3.1.

What changed in version 1.3.1?

Version 1.3.1, released 17 September 2026, changes licensing and notices only. Licence keys and authorised domains are now stored as salted hashes in the hosted file, development access is limited to localhost and 127.0.0.1, the public demo no longer exports CSV files, the headless model call requires an Enterprise key, and every result, summary and CSV now shows the model version, data vintage and reference exchange rate. No calculation, rate or dataset changed.

Do licensees need to do anything to receive version 1.3.0?

No. The hosted file was replaced on 16 September 2026 and every licensed embed picks up version 1.3.0 on its next page load. Licence keys, authorised domains, tier entitlements and expiry dates are unchanged, and existing embeds open exactly where they did before.

Which US states does version 1.3.0 cover?

All 50 states and the District of Columbia. Each carries an indicative large-load power rate, an interconnection queue estimate, a construction location factor, a property tax index, its data centre sales tax status for new projects and, in eight states, a large-load take-or-pay tariff. Embeds can open on a state with data-region set to a code such as US-TX or simply TX.

When does the configurator show USD instead of CAD?

Whenever a US state is selected. Canadian provinces return every figure in Canadian dollars and US states return every figure in US dollars, including the capital breakdown, revenue, operating cost, clipboard summary and CSV export. Switching between a province and a state converts the whole model at once, and a revenue setting the user has already adjusted is carried across at the same exchange rate.

Did version 1.3.0 change any Canadian numbers?

No. Every province, build profile and accelerator combination returns the same capital and EBITDA figures as version 1.2.0, verified by running both versions side by side across all 441 combinations before release. The only visible changes for a Canadian user are the grouped location selector and six additional rows in the CSV export.

How does the model treat US sales tax on data centre equipment?

Where a state has no data centre exemption open to new projects, the model applies that state's combined state and average local sales tax to the taxable share of fit-out, cooling, network and accelerator capital, and shows it as its own line. In 2026 that includes states whose exemptions were paused or closed, such as Arizona, Illinois and Ohio, as well as states that never offered one, such as California and New York. States with an open exemption, and states with no sales tax, carry no equipment tax line.

Do licensees need to do anything to receive version 1.2.0?

No. The model lives in a single hosted file on strategiccryptoreserve.ca. When that file is replaced, every licensed embed picks up the new version on its next page load. There is nothing to download, redeploy, reinstall or re-paste. Licence keys, authorised domains, tier entitlements and expiry dates are untouched by the update.

Will version 1.2.0 break an existing embed?

No. Every configuration key that worked before still works. No build profile, province or cooling architecture was removed, the two accelerator keys that were repointed at newer silicon kept their original names, and all six data attributes parse identically. Both live licences were rendered in a real browser environment before release and both produced correct output, correct tier gating and correct refusal on unauthorised domains.

Why did the Quebec power rate more than double in this release?

Hydro-Quebec filed a dedicated rate for large data centres averaging 13 cents per kilowatt hour, roughly double what large-power customers currently pay, applying to facilities drawing more than 5 megawatts and expected to take effect in the second half of 2026 subject to approval by the Regie de l'energie. Existing connected sites transition over five years. The rate for cryptographic use applied to blockchains is proposed to move to an average of 19.5 cents with a three-year transition. The model now reflects the filed rate rather than the legacy industrial rate.

Why did outputs get less profitable in version 1.2.0?

Two industry-wide movements. Capital cost benchmarks rose across every build profile in line with published 2026 construction indices, which have tracked upward every year since 2020. And the operating expense breakdown was expanded to separate property tax, insurance and general administration from facility maintenance, following how operators and lease disclosures now report facility cost. Version 1.2.0 returns EBITDA margins between 31 and 77 percent depending on the commercial structure.

What happened to the accelerator classes named nvl72 and next?

Both keys were kept so existing embeds continue to work, and both were repointed at current generation silicon. The key nvl72 now describes a GB300 NVL72 rack-scale deployment at roughly 140 kilowatts per rack, and the key next now describes a Vera Rubin VR200 NVL72 in the Max Q power profile at roughly 190 kilowatts per rack. Two new classes were added alongside them, b300 for Blackwell Ultra and vr200p for the Vera Rubin Max P profile at roughly 230 kilowatts per rack.

Can a licensee stay on the previous version of the model?

Not on the standard or pro tiers. Central maintenance is the product: every licensee runs the same current model so that no client is ever shown a stale number in a live meeting. Enterprise licences can pin cost constants to an internally agreed basis, which is a different mechanism from version pinning and is intended for firms modelling against their own build costs rather than published benchmarks.

How often is the model revised?

There is no fixed schedule. Revisions are triggered by material movement in the underlying data rather than by the calendar. A utility cancelling a rate schedule, a regulator filing a new large-load tariff, a system operator closing an allocation window, or a new accelerator generation shipping at a different rack power will each trigger a review. Version 1.2.0 was prompted by three separate regulatory changes landing inside the same six months.

Run the Current Model

The live demo on the main configurator page runs v1.3.0 under a demo licence. Switch configuration, Canadian province or US state, cooling architecture and accelerator class and the whole model recalculates — in CAD for provinces and USD for states — against the data described on this page.