Meta Rosemount
FJI source-qualified: four-document gate met, including project-specific government evidence. Qualification evidence and decisions →
Project status: Development described in operator fact sheet; opening not confirmed by reviewed evidence. Capacity scope: Current comparable IT capacity not established in reviewed profile. How we verify evidence.
← Back to project index- Location
- Minnesota / Rosemount
- Readiness
- Proposed / development
- Status
- Development described in operator fact sheet; opening not confirmed by reviewed evidence
- Confirmed companies
- Meta Platforms; Xcel Energy; City of Rosemount
- Next milestone
- Dated operating confirmation, service-cost terms and measured energy and water use.
- 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
Rosemount links computing development to the cost of local services. Meta describes paying the full costs of its energy, water and wastewater service, which helps identify who is meant to bear the infrastructure burden. That commitment is economically different from utility profit or completed operation. The owner still needs useful computing outcomes sufficient to recover its capital and operating expenses.
Readiness basis: Classification of evidence in the reviewed profile; strongest documented phase, not full-campus completion. Development described in operator fact sheet; opening not confirmed by reviewed evidence Readiness source →
What the sources establish
- Operator / company disclosure Investment scope. Meta’s fact sheet describes more than USD 800 million of data-center investment in Minnesota, about 100 operational jobs once completed and a future role in its global infrastructure. The document does not confirm a campus opening date, current IT load or final construction cost. Primary source →
- Operator / company disclosure Service and cooling commitments. The sheet identifies Xcel Energy planning and City of Rosemount water and wastewater coordination, with Meta paying full service costs. It describes a planned closed-loop liquid-cooling system using zero operational water. That cooling claim is not evidence of zero total site water use or measured operation. 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 / META | Funds and uses its own infrastructure. | Computing benefits must exceed operating, depreciation and recurring investment costs; no campus product revenue is disclosed. |
| Xcel Energy / XEL | Named energy-planning counterparty. | Identify approved tariffs, asset ownership and funding treatment; paying service costs does not establish utility return. |
| City of Rosemount | Water and wastewater service counterparty. | Service funding is a municipal infrastructure obligation, not a public-stock earnings stream. |
How financially meaningful is it? Analyst interpretation
Our analysis: cost responsibility is a useful de-risking commitment for the community, while it can raise Meta’s all-in project cost. Utility shareholders benefit only under the actual asset, tariff and financing arrangements. Renewable matching and closed-loop design address different issues; neither demonstrates every hour of carbon-free operation or eliminates all water demand. Actual operating reports are needed to compare the design with delivered outcomes.
Internal-compute return depends on attributable product benefits and cost savings, less power, staff, equipment depreciation and maintenance. Add service-infrastructure funding to the initial cash requirement rather than counting it as an operating benefit.
Hypothetical illustration: an assumed USD 800 million capital base depreciated evenly over 20 years produces USD 40 million of annual depreciation; over 10 years it produces USD 80 million. Actual building and equipment lives differ, so this is a sensitivity example, not Meta’s depreciation schedule or Rosemount asset base.
Milestones that would change the assessment
| Milestone | Evidence to watch |
|---|---|
| Opening evidence | Seek a dated operator statement that the site is serving workloads; the fact sheet’s future description is not commissioning proof. |
| Service terms | Verify utility decisions and infrastructure funding scope, separating reimbursement from return-bearing utility investment. |
| Measured resources | Watch site-level energy and water disclosures and distinguish cooling water from domestic or other consumption. |
What could break the investment case?
Our analysis: Delivery can depend on several infrastructure parties. Equipment or liquid-cooling upgrades may raise capital needs. Service costs can exceed early expectations, and resource design claims may not match actual operating conditions or workload density.
What would change our view?
Our analysis: Our confidence would rise with operating confirmation, transparent service terms and measured efficiency. It would fall if infrastructure obligations expand without matching computing benefits or if delivery remains unverified after substantial funding.
What remains unknown Not established in this review
Opening date, current IT MW, hardware suppliers, commissioned cooling configuration, actual water consumption, service tariffs and campus financial contribution remain unestablished.
Project research for information, not a buy recommendation. Financial illustrations use assumptions, not disclosed site results or management guidance.
Company investor information & quarterly statements
Meta Platforms
Meta developer/owner-user; resource commitments not accepted service.
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 →