Meta Mesa: Desert operations make resource-adjusted computing cost important
FJI qualification held or pending: the full four-document gate, including project-specific government evidence, has not yet been accepted. Qualification evidence and decisions →
Project status: Meta announced online and serving traffic January 30, 2025. Capacity scope: IT MW undisclosed; more than USD 1 billion fully built-out investment headline. How we verify evidence.
← Back to project indexCompare this project → · Track its catalysts → · Evidence guide →
- Location
- Mesa, Arizona — representative locality pin
- Readiness
- Operating
- Status
- Meta announced online and serving traffic January 30, 2025
- Confirmed companies
- Meta; Salt River Project; DPR Construction
- Next milestone
- Measured peak resource performance, accepted expansion scope and useful workloads
- Reviewed
- October 6, 2026
Expanded analysis · Original disclosures linked below · CAD and USD preserved as labeled · Company statements attributed; interpretations labeled.
The one-minute investment takeaway
Our analysis: Desert operations make resource-adjusted computing cost important. Mesa offers a dated operating campus in Arizona. Its renewable relationship is documented, while actual campus load, cooling performance and site earnings remain undisclosed.
Readiness basis: Classification of evidence in the reviewed profile; strongest documented phase, not full-campus completion. Meta announced online and serving traffic January 30, 2025 Readiness source →
What the sources establish
- Online evidence. Meta’s January 30, 2025 announcement says Mesa is operational and serving traffic, with more than USD 1 billion investment when fully built out. Primary source →
- Energy boundary. The release names SRP and describes three renewable projects totaling 450 MW. That generation-support figure is not the data center’s IT load or measured electrical demand. Primary source →
Who receives the money?
Our analysis of disclosed roles. Revenue routes are business-model interpretations, not estimates of booked project revenue.
| Company / exposure | Economic role | What investors need to establish |
|---|---|---|
| Meta | Owner or operator of the disclosed infrastructure | Accepted useful capacity and net contribution after resource and renewal costs. |
| Named service and construction participants | Contract-specific delivery and recurring service roles | Actual contract, tariff or purchase terms; participation is not booked profit. |
| Equipment suppliers not established here | Potential procurement and renewal spending | Named awarded orders before attributing public-company project revenue. |
How financially meaningful is it?
Our analysis: Operating in a hot climate increases the importance of measured thermal performance under peak conditions, but climate alone does not establish that the campus is inefficient. The relevant cost includes energy, cooling equipment, maintenance, water obligations and hardware renewal per unit of useful computing. SRP is a distinct utility organization and should not be assigned an invented public-market ticker. Renewable-project nameplate MW cannot be treated as continuously delivered energy, hourly matching or campus computing capacity. Meta’s products monetize compute across its system; neither the local investment headline nor the number of operational jobs discloses campus contribution. Additional phases should be analyzed separately from the January 2025 online milestone, with clear capital allocation and service acceptance.
Computing contribution equals customer or product benefit minus power, network, facility operation, financing and equipment renewal. Model long-lived buildings separately from shorter-lived computing assets.
Hypothetical illustration: 10 MW steady IT load at 1.2 PUE uses 105,120 MWh annually. A USD 10/MWh tariff increase adds USD 1.0512 million annual cost. Neither load, PUE nor tariff is disclosed here; this is a sensitivity example, not a site forecast.
Milestones that would change the assessment
| Milestone | Evidence to watch |
|---|---|
| Scope and capital | Reconcile campus and portfolio figures, accepted versus potential capacity, and property versus equipment funding. |
| Electrical and cooling acceptance | Measured peak resource performance, accepted expansion scope and useful workloads. Equipment delivery, construction completion and commissioning are separate steps. |
| Commercial productivity | Useful workloads or billable customer capacity, with operating costs and renewal obligations included. |
| Counterparty attribution | Named binding service and procurement terms before estimating participant earnings. |
What could break the investment case?
Our analysis: Peak thermal conditions, resource upgrades and equipment renewal can alter cost. Renewable capacity supports an energy relationship but does not guarantee low tariffs or continuous physical supply.
What would change our view?
Our analysis: Dated acceptance, disciplined incremental capital and useful output at competitive resource cost would strengthen our assessment. Idle equipment, repeated delivery slippage or capital and renewal spending ahead of economic benefits would weaken it. We change the stage only on project-specific evidence, and would improve public-company financial attribution only with contract scope and cash-flow detail. A larger headline by itself would not justify a stronger return conclusion.
What remains unknown
Current accepted IT and facility MW, workload mix, utilization, site-attributable income, contract prices, tariffs, hardware renewal schedule and phase-specific capital allocation remain unestablished in the reviewed sources unless explicitly disclosed above. Targets remain expectations until confirmed. The map pin represents the locality rather than a verified individual building. Supplier, fund and corporate exposures must be modeled separately.
Project research for information, not a buy recommendation. Financial illustrations use assumptions, not disclosed site results or management guidance.
Arizona government record check
Reviewed October 7, 2026 · Matched legal entity and city agreement record
Mesa file 21-0552 concerns development and sustainable water-service agreements with Redale LLC for approximately 396 acres southeast of Elliot and Ellsworth Roads. The city’s public legislative API records a passed date of May 17, 2021, although the public item page still displays Agenda Ready and an empty action history. Meta’s 2024 subsidiary exhibit names Redale LLC, and independent reporting ties Redale’s Mesa development to Meta. This strengthens the project-entity match. The water agreement attachment was identified but its complete terms were not retrieved; no contractual allowance is reported as actual consumption. The agreement action does not establish completion of later phases or energized IT MW.
Mesa Redale council item · Mesa public legislative record · Meta subsidiary exhibit filed with SEC · Independent Redale / Meta campus reporting · Maricopa County air-record portals
Targeted record screen; air permits, building completion and project-specific power service remain unverified in this review. Readiness is based on the separately cited project evidence.
Company investor information & quarterly statements
Corporate-disclosure certification held: SRP: held; DPR: held; Research packet retains a corporate disclosure hold.
Meta Platforms
Campusowner/operator
Official investor & shareholder information · Quarterly financial statements: 2026 Q2, quarter ended June 30, 2026
SRP
Utility/renewablecounterparty
Disclosure verification held: Official investor and quarterly document coverage remains incomplete.
DPR
Constructioncontractor
Disclosure verification held: Official investor and quarterly document coverage remains incomplete.
Private participant: Government,cooperative,academic,or nonlisted operatingcounterparty: no public quarterlystatement requirement assumed; applicable annual/interimreporting and entity structure need explicit documented exception.
Private participant: Private/unlisted participant: no public quarterly financialstatements reviewed. No invented quarterlies or indirectparent exposure. Current ownership/private-status documentation remains tobeverified.
Corporate disclosures provide company-wide context. They do not establish this project’s revenue, spending, profit, ownership share or operating capacity. Disclosure verification records →