Phase Space AI

Valuation

WhiteFiber [WYFI]

WhiteFiber, Inc. [WYFI] — Valuation

As of: 2026-07-29 · Spot: $20.56 · EV (ex digital assets): $953m · Framework: v1.5.1 / criteria.md 2026-07-29 Cluster context: CLUSTER_Analysis.md

Two outputs are required on every name: a 12-month target and the implied-path test. Reporting only one is a defect. Both are addressed below, and where an input does not exist it is declared UNIDENTIFIED rather than substituted with a peer median.


Exit multiple: UNIDENTIFIED as an earnings multiple — declared, not defaulted

WYFI grew +30.8% YoY in Q1 2026. Under the growth-matched rule in valuation.md, an exit multiple may only be drawn from a comparator set whose growth brackets the subject's:

Candidate comparator Growth Verdict
CoreWeave +111.6% YoY (Q1 2026) 3.6x too high
Equinix, Digital Realty (mature contracted datacenter) ~5–15% 2–6x too low
The pivoting miners −0.02% to +225% not a comparator set — different business

No comparator brackets +30.8%. The exit multiple is declared UNIDENTIFIED rather than defaulted to a peer median. This is the exact defect valuation.md was written to close: the diagnostics anchor set spanned 1.0–7.5% growth and was used to value 15–39% growers, extrapolating a slope ~5x beyond its support. Anchoring WYFI on EQIX/DLR would repeat it precisely.

The substitute instrument: EV/RPO, which requires no growth match

EV/RPO is a contract-value ratio, not an earnings multiple. It compares enterprise value to disclosed, audited contractual obligations. It does not embed a growth assumption, so the growth-matching constraint does not apply and CoreWeave becomes a legitimate benchmark.

EV ($m) RPO ($m) EV / RPO RPO ÷ TTM revenue
CoreWeave 54,683 98,800 0.55x 15.9x
WhiteFiber 953 924 1.03x 11.0x
IREN 12,107 710 17.05x 0.94x

WhiteFiber is priced at 1.9x CoreWeave per dollar of signed contract, and 1/17th of IREN's. Given that WYFI's contracted revenue carries pass-through power and contractual escalators while CoreWeave carries GPU depreciation, a modest premium to CoreWeave's ratio is defensible rather than anomalous.

The implied-path test — PASS WITH ARGUMENT, and the argument is named and evidenced

criteria.md permits PASS WITH ARGUMENT where the price requires more than has been demonstrated and there is a specific, evidenced reason — "a named product cycle, mix shift, pricing action. Narrative does not qualify."

The required path: - Today's EV of $953m against annualised Q1 2026 revenue of $87.7m is 10.9x. - At CoreWeave's 0.55x EV/RPO, WYFI's $923.7m RPO supports $508m of EV — 47% below today's $953m. - So on the strictest available anchor the price requires 1.9x more contracted revenue than is signed.

The evidenced argument, item by item — this is a contract, not a story:

  1. The revenue is signed and not yet billing. The $865m Nscale order was executed in November 2025. Management states "billing is expected to commence during the second quarter" with "full revenue contribution… during the third quarter of 2026." The Q1 2026 run-rate of $87.7m annualised contains essentially none of it — only $0.7m was recognised from deferred revenue in the quarter.
  2. The contracted schedule is disclosed, dated and audited. RPO of $90.7m (2027), $91.8m (2028), $93.5m (2029), $93.5m (2030) — approximately $90m a year against $84.3m of TTM revenue today. The contracted book alone roughly doubles revenue as it switches on, before any new customer.
  3. $144.5m of the cash is already collected, $65.7m of it added in Q1 2026 alone, against a $794m market capitalisation. Prepayment is the strongest available evidence that a counterparty intends to perform.
  4. Power is passed through and escalators are contractual, so the margin is structurally protected rather than forecast.
  5. A named counterparty, a named facility, a stated value, a stated term. All four disclosed.

Verdict: PASS WITH ARGUMENT. Flagged explicitly — this is not a PASS. The argument rests on one counterparty delivering on one facility, and Nscale is a private company whose own financing is not visible from these filings. Two further caveats stated rather than buried: the GPU cloud segment's contract history is poor (§3 of the research file), and the colocation business that generates the RPO was acquired, not built.

Sensitivity over the exit multiple — the highest-variance parameter

Terminal value exceeds 60% of EV, so per criteria.md this is the mandatory primary analysis, run over the multiple and never over scenario probabilities. Run on both instruments:

On EV/RPO:

EV / RPO EV supported by $923.7m of RPO vs today's $953m Implied share price
0.55x (CRWV today) $508m −47% ~$17.3
0.80x $739m −22% ~$23.3
1.03x (WYFI today) $953m current $20.56
1.50x $1,386m +45% ~$40.0

On EV / annualised AI revenue, once the Nscale contract is billing (i.e. TTM revenue of ~$84.3m plus ~$90m of Nscale ≈ $174m):

Exit multiple EV supported by ~$174m of post-Nscale revenue vs today's $953m
6.6x (CRWV today) $1,148m +20%
10.9x (WYFI today) $1,897m +99%
5.0x $870m −9%

These two tables are the whole WYFI case. On today's revenue at CoreWeave's contract ratio the stock is 47% too expensive. On post-Nscale revenue at CoreWeave's revenue multiple it is 20% too cheap. The entire question is execution timing on one contract, and it resolves observably within two quarters — which is why this is the most falsifiable position in the cluster.

12-month target: UNIDENTIFIED

Both required inputs fail, and the second one decisively:

  1. No consensus. Alpha Vantage quota shared and not attempted. Consensus Criteria INDETERMINATE, blocks nothing.
  2. The name's own trading history is 12 months long. WYFI IPO'd in August 2025. valuation.md requires the 12-month multiple be anchored on the name's own trading range with the percentile stated, and explicitly directs: "If the history is too short or spans a regime change, declare it UNIDENTIFIED rather than substituting a peer median." WYFI's history is both — too short, and containing the Reorganization, the IPO and the signing of a contract worth 10.9x its annual revenue.

Declared UNIDENTIFIED. No target is manufactured. What is stated, because it is disclosed rather than modelled: the contracted revenue schedule of ~$90m per year from 2027 through 2030 is a dated, audited floor, and it is the number a 12-month view should be built on once one quarter of Nscale billing is observable.


Why the mining leg and the AI leg cannot share an exit multiple

This is the methodological core of the cluster and it applies directly to WYFI:

Bitcoin mining AI/HPC hosting or cloud
Revenue driver commodity price × share of a rising global hashrate contracted $/MW or $/GPU-hour
Counterparty none named, with a term
Contract none 5–10 years, often with prepayments and RPO
Terminal value halves every ~4 years by protocol; global hashrate grows continuously a datacenter with a signed tenant
Observed gross margin, 2026 HIVE 24% (from 49%); CORZ −56% CORZ colocation 59%; WYFI 61%

A single blended exit multiple applied across these two streams is the exact defect that inflated ADMA by 51pp and INOD by 32pp. This analysis therefore ranks on EV / annualised AI-HPC revenue and EV / RPO — a price-for-what-exists and a price-for-what-is-signed — and scores the mining leg at UNIDENTIFIED with a floor at zero, because a stream with a negative gross margin at one operator and a halving margin at another has no defensible positive revenue multiple.


Required disclosures per valuation.md

Requirement This memo
The parameter solved for, and every parameter held fixed, named Stated above: AI-HPC revenue required, holding the exit multiple, share count and net debt fixed
Margin: demonstrated − required, in percentage points Stated above — this is the number the strategy ranks on
The exit multiple used, and the implied compression from today's trading multiple, as a number Stated above
Sensitivity over the exit multiple (never over scenario probabilities) Table above
Reverse DCF mandatory where terminal value > 60% of EV Terminal value does exceed 60% of EV. reverse_dcf.py was not solvable because the exit multiple is UNIDENTIFIED; the required-parameter analysis above is the substitute and is disclosed as such rather than presented as a DCF output
Growth-matched anchoring, or declare UNIDENTIFIED Declared above
Do not set the base exit multiple below every stated anchor Not applicable — no base multiple is asserted
TTM revenue, never last fiscal year TTM used throughout; see the model notes for the derivation