Google Mesa: Clean-energy procurement and computing capacity use different measures
FJI source-qualified: four-document gate met, including project-specific government evidence. Qualification evidence and decisions →
Project status: Mesa appears in Google’s current facility efficiency reporting; 2024 launch target is historical. Capacity scope: Campus IT MW undisclosed; 430 MW-plus regional clean energy program is separate. How we verify evidence.
Compare this project → · Track its catalysts → · Evidence guide →
← Back to project index- Location
- Mesa, Arizona — locality pin
- Readiness
- Operating
- Status
- Mesa appears in Google’s current facility efficiency reporting; 2024 launch target is historical
- Confirmed companies
- Google / Alphabet (GOOGL); Salt River Project; NextEra Energy Resources / NextEra Energy (NEE)
- Next milestone
- Measured resource performance, phase computing output and verification of the hourly energy target
- 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: Clean-energy procurement and computing capacity use different measures. Mesa adds a second operator to Arizona coverage, distinct from Meta Mesa and CyrusOne Chandler. The energy procurement program is relevant to operating cost and carbon accounting but does not establish campus IT capacity. SRP is a public power entity; NextEra is a listed parent with generation exposure distinct from Google compute profit. Published efficiency demonstrates measured facility activity without revealing full load. Hot-weather resilience, cooling requirements and actual hourly energy matching matter more than a broad annual claim. The earlier 2025 opening target should not be treated as proof of its own achievement.
Readiness basis: Classification of evidence in the reviewed profile; strongest documented phase, not full-campus completion. Mesa appears in Google’s current facility efficiency reporting; 2024 launch target is historical Readiness source →
What the sources establish
- Current facility evidence. Google includes Mesa in its reported data-center efficiency table. This is operational measurement evidence, not a published utilization or AI workload split. Primary source →
- Named energy program. Google’s March 2024 announcement names SRP and NextEra Energy Resources in a 430 MW-plus clean-energy program. It targeted an 80% hourly carbon-free energy level for 2026. 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 |
|---|---|---|
| Google / Alphabet (GOOGL) | Product and cloud-service contribution; an owner-user return | Useful computing after replacement costs |
| Named resource or service participants | Utility service, network provision or managed-fund ownership only where documented | Contracts, billing scope and cost recovery; do not treat customer payments as automatic profit. |
| Other equipment and construction vendors | Potential capital-purchase receipts; no undisclosed vendor assigned | Actual orders and scope before attributing earnings or AI exposure. |
How financially meaningful is it?
Our analysis: Mesa adds a second operator to Arizona coverage, distinct from Meta Mesa and CyrusOne Chandler. The energy procurement program is relevant to operating cost and carbon accounting but does not establish campus IT capacity. SRP is a public power entity; NextEra is a listed parent with generation exposure distinct from Google compute profit. Published efficiency demonstrates measured facility activity without revealing full load. Hot-weather resilience, cooling requirements and actual hourly energy matching matter more than a broad annual claim. The earlier 2025 opening target should not be treated as proof of its own achievement.
Evaluate facility electricity as IT load multiplied by actual PUE, then model the cost and timing of the energy portfolio independently.
Hypothetical illustration: A hypothetical reduction from PUE 1.30 to 1.20 at 30 MW IT load saves 26,280 MWh annually; at USD 60/MWh that is USD 1.5768 million. These are assumptions, not reported Mesa savings.
Milestones that would change the assessment
| Milestone | Evidence to watch |
|---|---|
| Readiness and scope | Measured resource performance, phase computing output and verification of the hourly energy target |
| Customer economics | Named commitments and accepted equipment scope; reconcile recurring receipts, electricity recoveries, incentives and maintenance. |
| Capital and resources | Document the incremental power, cooling and network investment needed at the intended density; identify which party pays. |
| Evidence of useful output | For owner-users, useful computing per dollar; for landlords, billable load and service margin; neither is inferred from a building count. |
What could break the investment case?
Our analysis: Summer electricity demand, equipment efficiency and resource resilience can affect useful cost. Neither clean-generation MW nor PUE discloses available GPU capacity. Renewable supply additions can have independent construction and operating risks.
What would change our view?
Our analysis: Phase-specific customer acceptance, sustained useful workloads and cash generation after recurring costs would strengthen our assessment. Missed acceptance, deteriorating margins or additional capital required without equivalent contract protection would weaken it. A larger design envelope alone would not change the operating assessment.
What remains unknown
Current phase utilization, site-specific cash flow, customer acceptance detail, actual tariff, measured PUE, maintenance obligations and incremental capital returns are not fully disclosed in the reviewed sources. Coordinates represent the named locality or campus vicinity, not a surveyed building. A target date is not a verified completion. Building area is not IT MW, and utility or generation capacity is not automatically campus computing capacity.
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 city project entity; phase approvals not fully reviewed
Mesa file 19-0809 explicitly names Google and Stone Applications LLC for a roughly 187-acre phased data-center development at the northwest corner of Elliot and Sossaman Roads. Later April 9, 2024 design-review items identify the same owner and site: Redhawk Phase 2 (DRB24-00134) and Redhawk HUB (DRB24-00194). The city’s public legislative API records July 1, 2019 as the passed date for the agreement item. The later design-review pages show Agenda Ready and no action history; their agenda language is not treated as final approval, an issued building permit or completion. The Arizona Commerce Authority separately reported Google’s September 6, 2023 groundbreaking. Current operation rests on Google’s facility reporting, not these historical planning records.
Mesa Google agreement item 19-0809 · Mesa Redhawk Phase 2 review · Mesa Redhawk HUB review · Arizona Commerce Authority groundbreaking report · Mesa public agreement action record · 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
Alphabet
developer/operator
Official investor & shareholder information · Quarterly financial statements: 2026 Q2, quarter ended June 30, 2026
NextEra Energy
Additional named public-company role;exact scope in current full profile
Official investor & shareholder information · Quarterly financial statements: Q2 2026 ended June30 2026
Corporate disclosures provide company-wide context. They do not establish this project’s revenue, spending, profit, ownership share or operating capacity. Disclosure verification records →