Google Pryor / Mayes County: Established infrastructure needs incremental return discipline
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: Operating Google campus explicitly identified by operator; current IT MW, utilization and expansion acceptance undisclosed. Capacity scope: Campus IT MW and current utilization undisclosed. How we verify evidence.
← Back to project indexCompare this project → · Track its catalysts → · Evidence guide →
- Location
- Pryor / Mayes County, Oklahoma — representative locality pin
- Readiness
- Operating
- Status
- Established Google campus; current IT load and AI share undisclosed
- Confirmed companies
- Google / Alphabet
- Next milestone
- Campus-specific expansion scope, operating load and renewal productivity
- 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: Established infrastructure needs incremental return discipline. Pryor supplies a long-running computing footprint in a state now receiving additional investment. Its existing role is credible; the financial case for a new dollar at this campus remains distinct from statewide growth.
Readiness basis: Classification of evidence in the reviewed profile; strongest documented phase, not full-campus completion. Established Google campus; current IT load and AI share undisclosed Readiness source →
What the sources establish
- Established footprint. Google identifies Mayes County as its original Oklahoma data center location, with construction beginning in 2007. Primary source →
- Portfolio boundary. Its current location page reports more than USD 15 billion invested across Oklahoma and lists newer locations including Muskogee, Stillwater and Tulsa. That state total is not Pryor’s campus budget. 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 | 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: The relevant comparison is an incremental refresh or expansion against alternative computing capacity elsewhere in Google’s system. Reusing buildings and staff can improve capital efficiency, while older distribution and cooling systems may require substantial upgrades for denser hardware. Operating history establishes execution experience, not a permanent cost advantage. Google’s current statewide spending includes geographically distinct developments and should neither be assigned entirely to Mayes County nor added to the earlier state totals. Model useful service output after energy, networking, support and equipment renewal. Cloud revenue and advertising benefits occur across a broad platform, so site economics require an explicit attribution method. A credible expansion announcement would clarify the asset scope and resource obligations before the atlas upgraded capacity or AI-specific exposure.
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 | Campus-specific expansion scope, operating load and renewal productivity. 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: Historical infrastructure may require retrofit spending. Portfolio investment totals can inflate perceived campus scale. Broad Google AI growth does not establish Pryor’s workload mix.
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.
Readiness evidence update · October 14, 2026
Operating existing campus. The current Google Oklahoma location page explicitly calls Pryor / Mayes County an operating site and separates three newer developments. State government corroborates the established footprint. Operating applies to the existing campus, not every phase, current metered IT MW or AI-only economics.
This corrects the prior unverified-readiness label. It records newly checked evidence, not a new opening event. Current IT MW, customer utilization, AI workload share, site earnings and acceptance of every expansion remain unverified. The wider Oklahoma investment envelope remains excluded from campus capital totals.
- Google Data Centers: Google's current Oklahoma location page explicitly identifies Pryor, Mayes County as operating, while distinguishing Tulsa County, Muskogee County and Stillwater as developments. This supports the existing-campus Operating label, not completion of every expansion, delivered IT MW or current utilization.
- Office of the Governor of Oklahoma: The Oklahoma governor's 2025 State of the State address describes continuing investment in Google's Pryor data center. This corroborates the established footprint; it is not a commissioning certificate or a campus capacity measurement.
- Google Data Centers: Google's security page describes control-station staff monitoring buildings and power, with a Mayes County control-room example. This supports ongoing operational context, not a measured site load or proof of every phase's acceptance.
- Google Cloud: Google Cloud's May 11, 2022 announcement describes an Oklahoma TPU v4 ML cluster in Preview. It is historical AI-infrastructure context, not proof of the present hardware inventory, customer utilization or building-level capacity at Pryor.
Company investor information & quarterly statements
Alphabet
Named Google owner-user operating campus; no allocated revenue.
Official investor & shareholder information · Quarterly financial statements: 2026 Q2, quarter ended June 30, 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 →