Google Montgomery County / Clarksville: An established Tennessee campus needs current workload attribution
FJI source-qualified: four-document gate met, including project-specific government evidence. Qualification evidence and decisions →
Project status: Google records official opening in 2019; current utilization 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
- Clarksville / Montgomery County, Tennessee — representative locality pin
- Readiness
- Operating
- Status
- Google records official opening in 2019; current utilization undisclosed
- Confirmed companies
- Google / Alphabet
- Next milestone
- Campus-specific accepted capacity, resource costs and useful cloud or product output
- 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: An established Tennessee campus needs current workload attribution. Clarksville provides dated official opening evidence, while the state investment headline remains broader than the campus. Its role is owner-user computing rather than a disclosed independent lease.
Readiness basis: Classification of evidence in the reviewed profile; strongest documented phase, not full-campus completion. Google records official opening in 2019; current utilization undisclosed Readiness source →
What the sources establish
- Dated opening. Google’s Tennessee page records the official Montgomery County opening in 2019 and the original plan announcement in 2015. Primary source →
- Portfolio budget. The page reports more than USD 6 billion invested in Tennessee since the facility was built in 2018. Build year and official opening year differ; the state total is not a site-only 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: Operating evidence changes the question from whether a facility can be built to whether subsequent capital earns adequate useful computing benefits. The state page refers to a build year and a later official opening; these represent different milestones rather than two new facilities. Investment can include later phases, servers or wider state activity, so no uniform campus return is calculated from the headline. The page also links advanced energy initiatives, but those broader arrangements should not automatically be assigned as exclusive physical supply to this campus. Evaluate actual service cost, dependable electrical capacity and hardware renewal. Google monetizes cloud services and product activity across its infrastructure system, leaving a site attribution gap. An established workforce and shared infrastructure may reduce marginal cost, while density upgrades or resource constraints could offset that advantage.
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: Statewide figures and broad energy initiatives can be assigned too aggressively to a single facility. Accepted load, renewal needs and workload productivity remain unknown.
What would change our view?
Our analysis: Dated acceptance, improved useful output and competitive net resource costs would strengthen our assessment. Underutilized capacity, expensive upgrades without customer support, or rising renewal costs ahead of economic benefits would weaken it. We would update this profile using campus-specific operating and contractual evidence. A larger corporate investment headline, a grant program or a design capability alone would not establish a stronger return.
What remains unknown
Current accepted IT MW, facility load, billable occupancy or workload utilization, site-attributable earnings, tariff details, phase capital, supplier contract values and measured performance remain unestablished unless explicitly stated above. Operator specifications are not independently measured outcomes. The pin represents the locality rather than a verified server hall. Broad portfolio AI demand is not proof of a dedicated AI deployment here.
Project research for information, not a buy recommendation. Financial illustrations use assumptions, not disclosed site results or management guidance.
Company investor information & quarterly statements
Alphabet
developer/operator
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 →