Oracle–Bloom Energy

Bloom Energy, which makes fuel cells that power data centers on site, is supplying Oracle — which intends to buy up to 2.8 and had 1.2 GW under contract by April 2026 — and gave Oracle a that Oracle exercised without paying cash for 2.15M Bloom shares, $323.9M in Bloom's books, which Bloom treats as a discount on the systems.

A deal between Oracle, Bloom Energy

Why it matters

Bloom Energy gave Oracle a stock discount on data-center power equipment that Bloom sells to an unnamed buyer. Bloom's filings describe Oracle as Bloom's 'customer's customer' and show that Oracle received 2,154,231 shares for no cash. Bloom deducts the stock's value from revenue as it delivers the systems.

Tap a figure for the line in its source.

Bloom Energy gives Oracle

  • of fuel-cell systems Oracle intends to procure under a master services agreement signed in March 2026 — an intention, not an order; no price, site list or schedule is public
  • disputedcontracted by Apr 13 2026, 'with deployment underway and continuing into next year'; on Sep 24 Bloom said Oracle's contract for Project Jupiter alone is 2.4 — how the two fit, no document says
  • a to buy them at $113.28 each, Bloom's closing price on Oct 28 2025 when it was agreed — issued Apr 9 2026, fully vested, exercisable to Oct 9 2026
  • issued May 1 2026 when Oracle exercised without paying cash — 1,905,433 net, plus 248,798 Bloom added to induce the net settlement; $323.9M at Bloom's accounting value, taken off its revenue as the systems are delivered

Jul 24, 2025 announced by Bloom Energy (release)updated Nov 18, 2026warrant exercised May 1 2026 disclosed by the parties

What happened

Bloom Energy makes fuel cells that turn natural gas into electricity on site without burning it. Oracle is buying the fuel cells for its data centers. The first system went into an Oracle data center in 2025, and Bloom Energy says it delivered the system in 55 days. In March 2026 Bloom Energy and Oracle signed a master agreement under which Oracle intends to buy up to 2.8 . Of that amount, Oracle had 1.2 GW under contract by April. Oracle has since picked Bloom Energy to power its Project Jupiter campus in New Mexico. Bloom Energy said in September that Oracle's contract there is for 2.4 GW. Bloom Energy also compensated Oracle in stock. Bloom Energy gave Oracle a to buy 3.53 million shares at $113.28. Oracle exercised it in May without paying cash and received 2.15 million shares that Bloom Energy values at $323.9M. By our calculation, the shares were worth roughly twice that at the market price implied by Bloom Energy's figures for that day. Oracle says it has sold the shares. In Bloom Energy's books, Oracle is its 'customer's customer'. Bloom Energy sells the systems to the buyer of record, a customer it does not name. Bloom Energy deducts the shares' value from revenue as it delivers the systems. Brookfield is the only financier Bloom Energy points to.

Sources 23 documents — 11 SEC filings · 4 company releases · 3 press reports · 2 social posts · 1 regulatory filing · 1 other document · 1 government statement

Research trail Found 157 documents and read 146 of them while checking this deal and related ones.

  1. SEC · SEC filingsec.gov
    States 6 figures: net shares · inducement · shares issued · $323.9M exercise fair value · customers customer · $17.3M cumulative reduction
  2. Bloom Energy · company releasebloomenergy.com
    States 3 figures: up to 2.8 GW msa ceiling · 1.2 GW initial contracted · first delivery
  3. SEC · SEC filingsec.gov
    States 2 figures: $113.28 exercise price · issuance
  4. SEC · SEC filingsec.gov
    States msa history
  5. Bloom Energy · company releaseinvestor.bloomenergy.com
    States first site
  6. SEC · SEC filingsec.gov
    States warrant
  7. SEC · SEC filingsec.gov
    States oracle sale
  8. SEC filingsec.gov
    Cited by the record; no single figure is quoted from it.
  9. SEC filingsec.gov
    Cited by the record; no single figure is quoted from it.
  10. SEC filingsec.gov
    Cited by the record; no single figure is quoted from it.
  11. SEC filingsec.gov
    Cited by the record; no single figure is quoted from it.
  12. SEC filingsec.gov
    Cited by the record; no single figure is quoted from it.
  13. company releaseoracle.com
    Cited by the record; no single figure is quoted from it.
  14. company releaseoracle.com
    Cited by the record; no single figure is quoted from it.
  15. social postpublish.x.com
    Cited by the record; no single figure is quoted from it.
  16. press reportApr 13, 2026cnbc.com
    Cited by the record; no single figure is quoted from it.
  17. social postlinkedin.com
    Cited by the record; no single figure is quoted from it.
  18. press reportnews.bloomberglaw.com
    Cited by the record; no single figure is quoted from it.
  19. regulatory filingpscdocs.utah.gov
    Cited by the record; no single figure is quoted from it.
  20. other documenthrratings.com
    Cited by the record; no single figure is quoted from it.
  21. SEC filingsec.gov
    Cited by the record; no single figure is quoted from it.
  22. government statementJul 2026env.nm.gov
    Cited by the record; no single figure is quoted from it.
  23. press report (archived copy)investing.com
    Cited by the record; no single figure is quoted from it.

The record's own summary of its sourcing: Bloom 8-Ks Items 1.01/3.02 (Oct 30 2025; Apr 13 2026, with the warrant as EX-4.1); 424B7 resale prospectus (Apr 27 2026); FY2025 10-K, Q1–Q3 2026 10-Qs and the Q2 10-Q/A; Bloom releases (Jul 24 2025; Apr 13 2026) and its post on X (Sep 24 2026); Oracle's Project Jupiter releases (Apr 27 and Oct 15 2026) and Q4 FY2026 results release (8-K ex-99.1, furnished Jun 10 2026); CNBC (Apr 13 2026), CNBC-TV18, Bloomberg Law (Sep 24 2026), BIP's Q4 2025 letter, a FERC Form 556 (May 18 2026), HR Ratings and a public comment in NMED's record for the contested cells · as of Oct 2026

The evidence 15 sourced figures · 4 disputes

The record's headline Oracle–Bloom Energy: up to 2.8 of fuel cells Oracle intends to procure, 1.2 GW contracted by Apr 2026 — and a Bloom gave Oracle, exercised without cash for 2,154,231 shares that Bloom values at $323.9M and takes off its revenue as consideration to a 'customer's customer': Oracle is not the buyer of record

Size
≤2.8 GW intended (master services agreement, Mar 2026) · 1.2 GW contracted by Apr 13 2026 (2.4 GW at Project Jupiter alone, per Bloom in Sep — contested) · warrant ≤3,531,073 sh @ $113.28 → 2,154,231 sh issued cashless May 1 2026, $323.9M at Bloom's accounting value, a reduction of its revenue
When
early 2025 collaboration (424B7) → Jul 2025 supply agreement for one Oracle data-center site, announced Jul 24 2025 → 2025 first system delivered 'in just 55 days' (Bloom) → Oct 28 2025 warrant agreed (8-K Oct 30) → Mar 2026 master services agreement (424B7) → Apr 9 2026 warrant issued (8-K Apr 13) → Apr 13 2026 'up to 2.8 GW', 1.2 GW contracted (release) → Apr 27 2026 Oracle: Project Jupiter on up to 2.45 GW of Bloom fuel cells; Bloom's resale prospectus for Oracle's shares → May 1 2026 cashless exercise, 2,154,231 shares → fiscal 2026 (to May 31) Oracle sells its 'Bloom Energy warrants' → Sep 24 2026 Bloom: Oracle's Jupiter contract 'to deliver 2.4 GW' → Oct 22 2026 Q3 10-Q: $17.3M of the $323.9M taken off revenue so far
Status
warrant exercised May 1 2026 (cashless, 2,154,231 shares); Oracle says it sold its 'Bloom Energy warrants' in fiscal 2026 · 1.2 GW contracted and deploying (Apr 2026) · Project Jupiter to run on Bloom fuel cells, its air permit pending (sg-oai-orcl) · $17.3M of the $323.9M taken off Bloom's revenue by Sep 30 2026, the rest carried as a customer consideration asset ($91.0M current, $215.5M long-term)
Structure
vendor-pays-customer warrant on a supply agreement (reverse vendor financing), with the customer not the buyer of record: Bloom gives the cloud (Oracle) equity, booked as 'consideration payable to a customer’s customer', and sells the systems to a buyer it does not name, whose customer Oracle is — Bloom's 'customer' may be 'a project‑finance affiliate rather than the ultimate end user', and the one framework it names in that role is Brookfield's (pw-brookfield-bloom)
Programme
Time-to-power
Parties
Oracle buyer by intent under the master services agreement + warrantholder — in Bloom's accounting the 'customer’s customer', not the buyer of record · Bloom Energy fuel-cell supplier + warrant-issuer
Capital
the seller's own money or backing comes back as its sales
Record
disclosed / primary source · as of Oct 2026

Flows 2 as the record states them

  • Bloom Energy → Oraclefuel-cellsfuel-cell power systems for Oracle's data centers in the US under a master services agreement (Mar 2026): Oracle 'intends to procure up to 2.8 gigawatts (GW)', 'an initial 1.2 GW of capacity has been contracted' (Bloom release, Apr 13 2026); Project Jupiter in New Mexico on 'up to 2.45 GW of installed Bloom fuel cell capacity' (Oracle, Apr 27 2026), a 2.4 GW contract by Bloom's Sep 24 account — no price, site list or schedule public. Bloom books the systems as sold to a buyer it does not name, whose customer Oracle is; who pays Bloom for them is contested (systems-owner)
  • Bloom Energy → Oracleequitywarrant for up to 3,531,073 shares @ $113.28 (agreed Oct 28 2025, issued Apr 9 2026, fully vested, to Oct 9 2026), exercised cashless May 1 2026: 1,905,433 net shares + 248,798 inducement shares = 2,154,231 issued, Oracle paying no cash; $323.9M at Bloom's accounting value (the warrant's grant-date value, contested $251.6M–$261.3M, + $72.3M for the inducement shares), taken off Bloom's revenue as the systems are delivered — $17.3M by Sep 30 2026; ≈ $400.0M of strike only on a cash exercise, which Oracle did not make

Resolved figures 15 each with the verbatim line from its document

  • msa-ceilingup to 2.8 GW
    a ceiling and an intention, not an order: under a master services agreement Oracle 'intends to procure up to 2.8 gigawatts (GW) of Bloom’s fuel cell systems', for 'Oracle projects in the U.S.' (Bloom release, Apr 13 2026) — no site, price or schedule named. The one filed account of the agreement, Bloom's resale prospectus of Apr 27 2026, has it signed in March 2026 and 'contemplates the intended purchase by Oracle of up to 2.8MW of fuel cells' (msa-history): megawatts, a thousandth of the release's figure, with no correction filed. The record reads gigawatts with every other document: the release two weeks earlier says 'gigawatts (GW)' and puts 1.2 GW already under contract inside the agreement (initial-contracted), which a 2.8 MW ceiling could not hold, and Oracle's release of Apr 27 places Project Jupiter's 'up to 2.45 GW' inside the same 'expanded partnership' (contracted-volume). The prospectus's MW reads as a unit error, but the filing's own reading is kept here, visible, rather than silently normalized
    “Under a master services agreement, Oracle intends to procure up to 2.8 gigawatts (GW) of Bloom’s fuel cell systems.”
    Bloom release (Apr 13 2026) · bloomenergy.com
  • msa-history
    the agreement's history in the one filing that tells it: a collaboration on fuel-cell installations for Oracle's AI cloud from early 2025, a supply agreement for one Oracle data-center site in July 2025 (first-site), and the master services agreement in March 2026 — its 'up to 2.8MW' discussed at msa-ceiling. The same prospectus registers the 3,531,073 warrant shares for resale by Oracle; Bloom 'will not receive any of the proceeds'
    “In July 2025, Bloom Energy and Oracle entered into an agreement for the supply of fuel cells at an Oracle data center site, and in March 2026, the parties entered into a master services agreement that contemplates the intended purchase by Oracle of up to 2.8MW of fuel cells to power its AI data centers.”
    Bloom 424B7 resale prospectus (Apr 27 2026) · sec.gov
  • initial-contracted1.2 GW
    1.2 GW contracted by Apr 13 2026, inside the up-to-2.8 GW agreement: 'an initial 1.2 GW', 'with deployment underway and continuing into next year', for Oracle projects in the US (Bloom release). No site, price or buyer of record is named, and no Bloom filing gives an Oracle figure in gigawatts. CNBC the same day: Oracle 'contracting 1.2 gigawatts of capacity from Bloom', 'with plans to finish the deployment in 2027'. Whether more is firm since stays contested (contracted-volume)
    “As part of this agreement, an initial 1.2 GW of capacity has been contracted, with deployment underway and continuing into next year.”
    Bloom release (Apr 13 2026) · bloomenergy.com
  • first-site90 days
    the first public step: Bloom would 'deploy its fuel cell technology at select Oracle Cloud Infrastructure (OCI) data centers in the U.S.' and power 'an entire data center within 90 days' — the July 2025 single-site supply agreement of the prospectus (msa-history). Bloom later said it took 55 (first-delivery)
    “To support the growing demand for OCI’s AI and cloud computing services, Bloom Energy will deliver highly reliable and cost-efficient onsite power for an entire data center within 90 days.”
    Bloom release (Jul 24 2025) · investor.bloomenergy.com
  • first-delivery55 days
    the first system, by Bloom's account: delivered 'to Oracle in just 55 days' in 2025, 'more than a month ahead' of the 90 days promised (release, Apr 13 2026); its CEO gives the size: 'We delivered 55 megawatts for Oracle in 55 days - down from 90 days' (CNBC-TV18 interview, via its LinkedIn post). Neither names the site. Brookfield's first project under its Bloom framework was 55 MW 'for a data center site in the U.S.', completed in Q4 2025, no site named (BIP's Q4 2025 letter; pw-brookfield-bloom inaugural-project); a 54.6 MW Bloom-operated plant 85% owned by a Brookfield venture sits at the address of a campus leased to Oracle (FERC, HR Ratings: pw-brookfield-bloom bolt-orc). That the three are one plant — Oracle's first system, Brookfield's first project, the Utah plant — is the monitor's reading: no document links them (contested systems-owner). The speed has no source but Bloom
    “Last year, Bloom Energy delivered a fully operational fuel cell system to Oracle in just 55 days”
    Bloom release (Apr 13 2026) · bloomenergy.com
  • warrantup to 3,531,073
    up to 3,531,073 Bloom shares at $113.28 each, Bloom's close on Oct 28 2025, agreed that day 'in connection with the partnership' to supply on-site power for AI data centers, 'subject to the negotiation of a warrant mutually acceptable' to both; to expire six months after it was issued, with no voting or dividend rights before exercise, and issued privately under Section 4(a)(2). Issued Apr 9 2026 (issuance). Bloom booked it as consideration it pays, a cut in its revenue (customers-customer); the '$400 million' of headlines is the shares × the strike (exercise-price)
    “On October 28, 2025, in connection with the partnership between the Company and Oracle Corporation (“Oracle”) to provide on-site solid state power for AI data centers, subject to the negotiation of a warrant mutually acceptable to the Company and Oracle, the Company agreed to issue to Oracle a warrant (the “Warrant”) to purchase up to an aggregate of 3,531,073 shares of Class A Common Stock, par value $0.0001 per share (the “Class A Common Stock”), with an exercise price of $113.28 per share, closing market price on October 28, 2025.”
    Bloom 8-K Items 1.01/3.02 (Oct 30 2025) · sec.gov
  • exercise-price$113.28
    $113.28 a share, Bloom's close on the New York Stock Exchange on Oct 28 2025 — a strike, not a value. × 3,531,073 = $399,999,949 (our multiplication): what Oracle would have paid Bloom on a full cash exercise, and the '$400 million' of CNBC's story ('a warrant to purchase $400 million in Bloom Energy's stock', 'for a total investment of $400 million', Apr 13 2026). Oracle exercised cashless instead (net-shares) and paid nothing; what the shares were worth stays contested (value-to-oracle)
    “the Company agreed to issue to Oracle a warrant (the “Warrant”) to purchase up to an aggregate of 3,531,073 shares (the “Warrant Shares”) of Class A Common Stock, par value $0.0001 per share (the “Class A Common Stock”), of the Company, with an exercise price of $113.28 per share, the closing price of the Class A Common Stock on the New York Stock Exchange on October 28, 2025.”
    Bloom 8-K Items 1.01/3.02 (Apr 13 2026) · sec.gov
  • issuance
    issued Apr 9 2026, 'fully vested and immediately exercisable' until Oct 9 2026, for cash or cashless at Oracle's election; transferable only with Bloom's consent, with registration rights for the shares (8-K; the warrant itself is EX-4.1). Four days later the two announced the up-to-2.8 GW agreement (msa-ceiling), and on Apr 27 Bloom's prospectus registered the shares for Oracle's resale (msa-history). The grant date fixes the warrant's accounting value (grant-date-value)
    “On April 9, 2026, the Company issued the Warrant to Oracle. The Warrant is fully vested and immediately exercisable, in whole or in part, at any time until 5:00 p.m. (Eastern time) on October 9, 2026, at Oracle’s election, by cash payment or by cashless exercise.”
    Bloom 8-K Items 1.01/3.02 (Apr 13 2026) · sec.gov
  • net-shares1,905,433
    1,905,433 shares on May 1 2026, three weeks after issue: a cashless exercise, so Oracle paid no cash and Bloom withheld shares worth the strike instead, by the warrant's formula on its 'Fair Market Value' of a share (EX-4.1) — 3,531,073 − 1,905,433 = 1,625,640 withheld (our subtraction). Oracle 'could elect either net or gross settlement' (Q3 10-Q); Bloom paid it to take net (inducement)
    “On May 1, 2026 (the “Exercise Date”), Oracle completed a cashless exercise of the Warrant, resulting in the issuance of 1,905,433 shares of our common stock.”
    Bloom Q3 2026 10-Q, Note 3 (Oct 22 2026) · sec.gov
  • inducement248,798
    248,798 more shares, which Bloom gave Oracle 'as an inducement for Oracle to elect net settlement' — net settlement issued 1.4 million fewer shares than a gross one (3,531,073 − 1,905,433 − 248,798 = 1,376,842, our subtraction). Valued at $72.3M, $290.60 a share (our division) — 'additional consideration', added to what Bloom takes off its revenue (exercise-fair-value)
    “Because the net settlement would result in 1.4 million fewer shares being issued than a gross settlement, we agreed to issue Oracle an additional 248,798 shares of common stock as an inducement for Oracle to elect net settlement. These incremental shares represented additional consideration with a fair value of $72.3 million.”
    Bloom Q3 2026 10-Q, Note 3 (Oct 22 2026) · sec.gov
  • shares-issued2,154,231
    2,154,231 shares in all, the 1,905,433 net plus the 248,798 inducement shares (net-shares, inducement), on a line of their own in Bloom's statement of stockholders' equity for the nine months to Sep 30 2026 — about 0.7% of the 295,537,217 shares outstanding at that date (our division). Oracle says it sold its 'Bloom Energy warrants' in its fiscal 2026 (oracle-sale)
    “Issuance of common stock upon warrant exercise, including incremental shares (cashless) (Note 3) 2,154,231”
    Bloom Q3 2026 10-Q, statement of stockholders' equity (Oct 22 2026) · sec.gov
  • exercise-fair-value$323.9M
    $323.9M, Bloom's accounting value of the 2,154,231 shares: the warrant at its grant-date value — $251.6M in the same 10-Q, contested (grant-date-value) — plus the inducement shares' $72.3M ($251.6M + $72.3M = $323.9M, our addition). Not their market value when Oracle exercised (value-to-oracle). The Q2 10-Q and its 10-Q/A gave '$324.4 million' beside the same two parts; the Q3 10-Q does not explain the $0.5M change, and its equity statement carries '(520)' thousand on the line 'Share-based consideration payable to customer’s customer' for the quarter. The latest filing's figure is carried. Bloom takes it off its revenue as the systems are delivered (cumulative-reduction)
    “As a result, the aggregate fair value of the shares issued upon exercise of the Warrant, including the incremental shares, was $323.9 million.”
    Bloom Q3 2026 10-Q, Note 3 (Oct 22 2026) · sec.gov
  • customers-customer
    how Bloom books it: as 'consideration payable to a customer’s customer', taken off Bloom's revenue 'as the underlying Energy Server systems sold under the Oracle arrangement are delivered' (Q2 and Q3 2026 10-Qs) — a price cut on systems that Bloom sells to someone else, whose customer Oracle is. Who that buyer is, no filing says (contested systems-owner). Bloom's 10-K paces the cut by 'executed statements of work with the key hyperscaler', and records a $9.6M 'payment to customer’s customer' in 2024 as well, unnamed
    “Following the Grant Date, the fair value of the Warrant was fixed, and is accounted for as consideration payable to a customer’s customer”
    Bloom Q3 2026 10-Q, Note 3 (Oct 22 2026); FY2025 10-K, Note 3 · sec.gov
  • cumulative-reduction$17.3M
    $17.3M of the $323.9M taken off Bloom's revenue by Sep 30 2026 — the pace at which the systems sold under the Oracle arrangement are delivered: $15.9M by Dec 31 2025 (10-K), $17.9M by Jun 30 2026 (Q2 10-Q), an 'increase of $0.5 million' to revenue in Q3 (Q3 10-Q). The rest sits on Bloom's balance sheet as a 'Customer Consideration Asset', $91.0M current and $215.5M long-term at Sep 30 2026, to be taken off as more systems are delivered
    “As of September 30, 2026, $17.3 million has been recognized on a cumulative basis as a reduction of revenue related to the Warrant.”
    Bloom Q3 2026 10-Q, Note 3 (Oct 22 2026) · sec.gov
  • oracle-sale
    Oracle's only word on the shares: its fiscal-2027 earnings guidance excludes 'the one-time events of selling our Ampere chip business and Bloom Energy warrants in fiscal year 2026' — the year to May 31 2026. It says warrants; Bloom's filings record a cashless exercise into 2,154,231 shares on May 1 (shares-issued). Neither company gives the date, the price or the gain: Oracle's fiscal 2026 results 'include one-time net investment gains from certain transactions', not split
    “after adjusting for the one-time events of selling our Ampere chip business and Bloom Energy warrants in fiscal year 2026”
    Oracle Q4 FY2026 results release (8-K ex-99.1, furnished Jun 10 2026) · sec.gov

Contested figures 9 not reconciled — every position side by side, with its source and tier

contracted-volume2 positions, side by side
1.2 GW across Oracle's US projects, as of Apr 13 2026: 'an initial 1.2 GW of capacity has been contracted, with deployment underway and continuing into next year', inside the up-to-2.8 GW agreement (initial-contracted). No later Bloom filing or results release gives an Oracle figure in gigawatts (the 424B7's is in megawatts; msa-ceiling) Bloom release (Apr 13 2026); Bloom's 10-Qs and Q1–Q3 2026 results releases (absence)
2.4 GW at one site, Project Jupiter in New Mexico, as of Sep 24 2026: 'Oracle remains committed to Project Jupiter and its contract with Bloom to deliver 2.4 GW of fuel cell capacity' (Bloom on X, 'As discussed with Oracle an hour ago', the day Bloomberg reported Oracle 'citing force majeure in a move to shield itself in case a Stargate data center in New Mexico gets derailed'). Oracle's own release of Apr 27 2026 puts Jupiter's 'up to 2.45 GW of installed Bloom fuel cell capacity' inside 'Oracle and Bloom’s previously announced expanded partnership', without the word contract (sg-oai-orcl dona-ana-power). The two readings do not add up: 1.2 GW + 2.4 GW = 3.6 GW, above the 2.8 GW ceiling (our arithmetic) — unless April's 1.2 GW is part of Jupiter, which its 'deployment underway' while Jupiter's air permit was still pending (it was in October: Oracle–YGI release, Oct 15 2026) makes hard to read, or the agreement has grown, which no document says Bloom on X (Sep 24 2026); Oracle releases (Apr 27 and Oct 15 2026); Bloomberg Law (Sep 24 2026)
grant-date-value2 positions, side by side
$251.6M at the Apr 9 2026 grant: 'As of the Grant Date and December 31, 2025, the estimated fair value of the Warrant and the commitment to issue the Warrant was $251.6 million and $55.9 million, respectively' (Black-Scholes, 115.0% volatility, a half-year term) — the two later 10-Qs, and the figure that with the inducement shares' $72.3M makes the $323.9M (exercise-fair-value) Bloom Q2 2026 10-Q and Q3 2026 10-Q, Note 3
about $261.3M at the same grant: the Q1 2026 10-Q's subsequent-events note, written weeks after the Apr 9 grant, gives a 'fair value of approximately $261.3 million'. No later filing explains the $9.7M difference or calls it a correction. Before the grant Bloom marked the commitment each quarter: $55.9M at Dec 31 2025, $183.6M at Mar 31 2026 Bloom Q1 2026 10-Q, Notes 3 and 16
value-to-oracle3 positions, side by side
$323.9M, Bloom's accounting value: the warrant at its grant-date value plus the inducement shares at theirs (exercise-fair-value) — the figure Bloom takes off its revenue, not a market price Bloom Q3 2026 10-Q, Note 3
about $626M at the market when Oracle exercised (our arithmetic): the 10-Q values the 248,798 inducement shares at $72.3M, $290.60 each, and at that price the 2,154,231 shares come to ≈ $626.0M (our multiplication). A public commenter in New Mexico's air-permit record, in an email of Oct 17 2026, reaches '$625.6 million' at a '$290.39' price for May 1. What Oracle got when it sold, Oracle does not say (oracle-sale) Bloom Q3 2026 10-Q (the monitor's arithmetic); a public comment in NMED's record for Project Jupiter's air permit (Oct 2026)
'$316 million' before the exercise: on Apr 13 2026, with Bloom's stock at 'almost $203', CNBC counted 'a $316 million gain for Oracle over the warrant price' — the gain on a cash exercise at that day's price, three weeks before Oracle exercised CNBC (Apr 13 2026)
systems-owner2 positions, side by side
not named: no filing says who buys the systems 'sold under the Oracle arrangement' — only that Oracle is the customer of Bloom's customer (customers-customer). Bloom's 'customer' 'refers to the contractual counterparty to which we sell our products and fulfil installation obligations, which in certain transactions may be a project‑finance affiliate rather than the ultimate end user' (Q3 2026 10-Q, Note 1). In 2026 the Brookfield ventures are not Bloom's largest such customer: over the nine months to Sep 30 its two largest took 'approximately 43% and 23%' of revenue, 'the second of which is our related party' (same note; in Q3 alone 43% and 26%, the related party again second) — the first, Bloom does not name. Most of its sales go to 'a financier or other strategic partner that owns the Energy Server product' (FY2025 10-K). For Project Jupiter, Oracle names the plant's developer, not its owner: 'Oracle and Yucca Growth Infrastructure (YGI) today proposed' a refinement to 'the Bloom Energy fuel cell microgrid that will power Project Jupiter', YGI being the applicant for its 'pending air permit' (Oracle release, Oct 15 2026); who owns YGI, no document on file says Bloom Q3 2026 10-Q and FY2025 10-K; Oracle–YGI release (Oct 15 2026)
Brookfield's ventures, for the first 55 MW at least (the monitor's reading): the same Note 1 sends the reader to 'the Brookfield‑affiliated financing framework structure'; Brookfield's first project under that framework was 55 MW 'for a data center site in the U.S.', completed in Q4 2025 (BIP), while Bloom delivered its first Oracle system in 2025 'in just 55 days' and its CEO said 'We delivered 55 megawatts for Oracle'; a FERC filing puts a 54.6 MW Bloom-operated plant, 85% owned by Brookfield ORC HoldCo and 15% by Bloom, at 6477 Wells Park Road, West Jordan, Utah — the address of a data-center campus '100.0% leased to Oracle America, Inc' (HR Ratings). And a project option whose 'original holder' was Oracle, bought by Bloom for $50.0M in May 2026, went to a Brookfield vehicle in July (pw-brookfield-bloom project-option). No document links the Utah plant to BIP's first project or to Oracle's first system — the match is by size, timing and address — and none says Brookfield owns or finances the 1.2 GW, or Project Jupiter's plant Bloom Q3 2026 10-Q; BIP Q4 2025 letter (6-K ex-99.1, Jan 29 2026); Bloom release (Apr 13 2026); CNBC-TV18 (Bloom's CEO); FERC Form 556 for Bolt ORC Project SPV (May 18 2026); HR Ratings on Project Novva (2025) — assembled by the monitor

Scope note what this record leaves to other records

NOT this record (carried elsewhere or not carried): the Brookfield–Bloom framework, the Fund JVs' purchases, Bloom's stakes in them and the Oracle-linked project option → pw-brookfield-bloom; Project Jupiter's own figures — the 2,462 MW nameplate, the proposed 1,600 MW output cap, emissions, the Green Chile gas pipeline, the schedule, the county's bond authorization, the reported bank loan and the force-majeure notice itself — are the site's (sg-oai-orcl dona-ana-power; for its next update, not carried here); Bloom's company figures → the bloomenergy entity; AEP's fuel-cell plant for Google → pw-aep-google; Nebius's Bloom-powered project, Bloom's scandium supply and the short sellers' fleet-performance claims → not carried here. No ribbon: no party gives a price for Oracle's systems and Bloom books them as sold to a buyer it does not name, so an oracle→bloomenergy width would rest on Jefferies' 'assumed $3,200 per kilowatt average selling price' (its 'approximately $3.8 billion' for the 1.2 GW, via Investing.com, Wayback) and could count the same systems twice beside brookfield→bloomenergy, which draws the Fund JVs' filed purchases (pw-brookfield-bloom). The warrant's shares run back to Oracle and stay on the deal's flows, like every backward flow here. Not adopted: CNBC's 'total investment of $400 million' (shares × strike; exercise-price); Jefferies' reading of the warrant as 'an 8% discount to headline average selling prices' (its own price assumption); Rystad's 'contracted' 9 GW across Bloom, framework agreements included; the prospectus's 2.8MW read as megawatts (msa-ceiling).

More between Oracle and Bloom Energy

The record holds no other deal between them.

Everything between Oracle and Bloom Energy →