PUBLIC RECORDS
WATER × POWER × OWNERSHIP
PUBLIC INFRASTRUCTURE, MAPPED
Where compute lands.
What it takes. Who builds it.
Start with the world, then switch to the deeper U.S. file. The map combines 4,722 U.S. records with 0 community-mapped observations in the global discovery layer. Search company, country, state or region, and local area. Water, power, owners, and builders stay separate until a source connects them.
Open the world mapTWO THINGS TO KNOW
A water-stress dot is not a water bill. It describes the surrounding area. It does not tell us whether a facility uses drinking water, reclaimed water, a well, a river, or closed-loop cooling.
A flag is a reason to check the record, not a verdict. Listed MW are not meter readings. Generator MW are not electricity use. Missing water data means no public figure was found—not zero use.
APPROVAL WATCH / A
Track the instrument.
Keep the scope.
Government decisions now have their own searchable event ledger. Planning permission, an air permit, a capacity award, or a water decision stays in its exact lane—never silently promoted to “the whole project is approved.”
Open Approval Watch →- Official starter events
- 13
- Authority routes
- 95
- Country playbooks
- 12
- Baseline checked
- 2026-08-31
WHAT IS IN THE DATABASE
Worldwide reach.
Uneven depth.
The U.S. directory covers all 50 states, DC, and Puerto Rico. The global discovery layer beyond that depth file spans 0 resolved jurisdictions using openly licensed community mapping. The U.S. layer carries the deeper water, power, ownership, and pipeline research.
Database note: U.S. directory snapshot August 2026; global OSM extract loading; Cloud Draw build 2026-08-31; Cloud Draw updated 2026-08-31. One row may be a building, point, phase, project, or campus. These are source records—not a property census.
WORLD + U.S. MAP / 01
Start wide.
Then narrow down.
This combines two different source layers. Blue points are global OSM discovery observations beyond the U.S. depth file; the U.S. uses the deeper national directory and High Falls research.
Loading U.S. and global map layers…
SELECTED RECORD
GA
Spalding Investments · High Falls Road
Georgia · Planned · Medium-High water stress
- Type
- Campus
- Company profile
- No primary-source corporate profile yet
Operator label; ownership not proven - Listed capacity
- No public figure found
Planning figure · not meter draw - Actual draw
- Not public in this directory
- Lifecycle
- Planned
- Water figure
- No public figure found
No facility figure found - Water source
- Municipal supply is proposed or expected; no public source mix found
- Cooling
- Closed loop · county required
A closed-loop water cooling system is required by the county zoning conditions; fill and makeup demand are not published - Utility
- Spalding County Water Authority service area
- Allowance
- No published site-level EPD withdrawal cap located
- Grid region
- Not listed
- Power source
- Related public power evidence is linked above; its scope may be portfolio-wide or regional
- Inside the watershed feeding High Falls
- No public facility-level daily water figure found
Approximate campus location within the Upper Towaliga HUC10; not a parcel survey. The county conditions require closed-loop cooling. That is not the same as zero total water use.
GLOBAL DISCOVERY INDEX / W1
Search the open world layer.
This is the starting index beyond the U.S. depth file: 0 OpenStreetMap observations across 0 resolved jurisdictions or map units. Search it by company, jurisdiction, state or region, and city or local area. Every row links to the original OSM element.
What this count means: a mapped point, building, or campus—not one verified operating company asset. Global water, power, owner, and contractor fields remain open until a source is attached.
PLANET COVERAGE REGISTER / W2
Coverage register
not available.
Cloud Draw will not substitute an observed-only list under a completeness headline. The discovery rows can still load, but this register stays explicitly unavailable until the full map-unit ledger is present.
0 shown
No jurisdiction matches this coverage filter.
Zero means no matching observation in this source extract—not no data center. Admin-0 labels are geographic routing entries, not a statement that every area is universally recognized as a country.
SOURCE EXPANSION REGISTER / W3
More sources.
Kept separate.
No public database can prove that every private, sovereign, edge, leased-suite, planned, or recently changed facility is present. These lanes show what is live, what can lawfully come next, and what requires permission.
OpenStreetMap via QLever
Mapped data-center points, buildings, campuses, and lifecycle tags with an original element link.
Community coverage is uneven; one campus can create several observations and an absent row proves nothing.Natural Earth 10m admin-0 map units
Country, dependency, disputed-area, and other admin-0 labels used to make zero-source jurisdictions visible.
A geographic label is routing context, not a facility registry or a position on sovereignty.OpenStreetMap submarine cables and landing stations
Community-mapped undersea telecom lines and cable landing station observations with original element links.
Coverage and tags are uneven; routes are discovery geometry and do not prove title, live service, exact alignment, spare fiber, or commercial availability.Government cable licence and marine-permit adapters
Country-specific licences, assignments, landing permissions, marine permits, legal parties, conditions, and approval events.
There is no single global approvals feed; exact wet routes, stations, and security-sensitive fields may be withheld from public inspection.TeleGeography geocoded submarine cable data
A stronger global cable and landing-point catalog with named systems, reported status, RFS, length, owners, suppliers, and generalized routes.
The public interactive map cannot be embedded or scraped into Cloud Draw; current raw JSON and GeoJSON require an annual commercial licence.Carrier and marketplace serviceability connectors
Route-level supplier catalogs, serviceability, rate cards, RFQs, capacity checks, and private quotes where a provider grants access.
A carrier footprint is not proof of available strands, and a private quote must remain private unless publication is explicitly authorized.Wikidata data-center entities
Named facilities, coordinates, aliases, operators, dates, identifiers, and linked citations under CC0.
Sparse community-maintained secondary evidence; each candidate still needs current project or operator proof.GLEIF Registration Authorities List
A machine-readable path to official business registers and validation authorities across jurisdictions.
It identifies registration paths, not data-center sites, operating status, property ownership, or utility accounts.Overture Maps Places
Global place candidates with coordinates, names, source lineage, confidence, and regular releases.
The current taxonomy has no data-center category, so name-pattern candidates require review and cannot be treated as facilities.PeeringDB
Public interconnection and colocation facility records with organizations and network presence.
Not bulk-ingested: current acceptable-use terms restrict reproduction, storage, bulk transfer, mapping, and commercial use without permission.COUNTRY PLAYBOOKS / C1
One country.
One rulebook.
The map can switch instantly. Research depth cannot. Each country gets its own route through legal identity, planning, water, power, builders, and publication checks before a discovery point becomes a verified project.
Canada
Federal discovery plus province-by-province water, power, assessment, registry, and local-planning adapters.
Jurisdiction shapeFederal assessment covers designated projects and federal lands; provinces and territories control most water, utility, environmental, corporate, and planning records.
Resolve the federal or provincial incorporation path before assigning a legal owner.
Accept: Corporations Canada, provincial registries, filings, and project-proponent records.Check the federal registry, then the responsible provincial assessment system and municipality.
Accept: IAAC project files, provincial approvals, zoning, development, and building records.Route by province or territory; record licence maximums separately from reported withdrawals.
Accept: Provincial licences, Ontario PTTW, Alberta Water Act records, and municipal service files.Route by provincial utility or system operator; keep requests, allocated capacity, tariffs, and supply distinct.
Accept: IESO, Hydro-Québec, BC Hydro, provincial regulators, and utility filings.Join a contractor only through a named project, phase, permit, or procurement document.
Accept: Owner, builder, municipal, and provincial project records.Label the province-specific rule used and any confidential large-load field left unavailable.
Accept: Adapter version, jurisdiction, source date, matching fields, and explicit gap.THE PLANET, IN BATCHES / C2
Expand without flattening the rules.
The open world layer remains available everywhere. Structured depth moves only after the country adapter names its authorities, identifiers, document types, update cadence, matching tests, and publication gaps.
Build provincial/state routers, run identity matching, and attach the first project-level water and power files.
Use national entry points, then branch to state, regional, municipal, water, and grid authorities.
Document each national grid, environment, water, corporate, and local-planning system before ingest.
Prioritize jurisdictions with public project registers and document unavailable fields instead of guessing.
Apply each national and devolved adapter before attaching project-level identity, planning, water, grid, builder, or reporting records.
Branch Australia by state, territory, market, and network; keep Singapore planning, utility, building, and policy evidence as separate tracks.
STATES / 02
Where the records are.
These bars count active directory rows and leave out cancellations. One campus can have several rows. Select a state to put only those records on the map.
COMPANIES / 03
See the whole portfolio.
Search 1,345 operator labels and map every matching row. We have completed primary-source corporate profiles for 26 large or closely watched portfolios. The rest stay marked as open research.
An operator label is not a deed. It does not prove who owns the parcel, holds the water account, or controls every point. We leave those fields open until a primary source answers them.
Search operators across every country →0 matching companies
No companies match these filters.
CRYPTO-MINING LOAD / M1
Find the mines.
Keep the caveats.
This screen catches U.S. directory records tied to operators with sourced Bitcoin-mining businesses. It does not assume that every campus owned by a mixed-use company is still mining.
0.6–2.3%
EIA’s preliminary range for crypto mining as a share of U.S. electricity consumption.
What the purple layer means. A primary source connects the operator to Bitcoin mining. It does not prove the workload, owner, power contract, fuel, or meter draw for every directory row carrying that operator label.
Power stays labeled. Listed MW is directory capacity. The fuel shown below is the state generation leader for context—not the facility’s electricity contract. Direct, behind-the-meter, and contracted sources need their own documents.
0rows · 0 MW listed
Scroll horizontally to read every column →
No mining-linked operator labels match these filters.
COVERAGE + COMPARISON
No one has a live, complete mine list.
EIA’s federal survey was discontinued, company portfolios keep changing, and global hashrate maps estimate geography rather than enumerate facilities. These are the methods we use and compare.
Federal 2024 baseline. EIA identified 137 facilities, but did not publish a current complete row-level national inventory.
Open method ↗Source of the U.S. directory rows screened here. Its listed MW may describe a building, phase, campus, or design—not actual draw.
Open method ↗Country-level hashrate estimates based on mining-pool data. Useful global context, but not a facility inventory.
Open method ↗An independent, source-cited U.S. compute map that includes crypto mining under different inclusion and record-matching rules.
Open method ↗BUILDER DESK / B1
Who is building the sites?
Construction companies are rarely named in a facility directory. This desk adds them only when a contractor, owner, or project document names the relationship. Search the builder, operator, project, state, country, or capacity.
Named does not mean exclusive. A project page may identify a general contractor or joint venture without listing every trade partner. Confidential clients stay confidential.
Search every sourced builder tie →18 sourced projects
Lebanon data center campus
Meta · Lebanon, Indiana
- Capacity
- 1 GW campus announced by Turner
- Scale
- About 4 million sq ft · more than $10B
- Timeline
- Construction announced in February 2026
Mortenson names Turner and Faith Technologies as collaborators. Turner describes itself as one of the contractors. This does not identify every trade contractor.
Richland Parish data center
Meta · Richland Parish, Louisiana
- Capacity
- Capacity not stated on contractor page
- Scale
- 2,250-acre project site
- Timeline
- Work began in late 2024; operational target by 2030
DPR identifies a joint venture with Turner and Mortenson. The page names the project owner and construction team, but not every subcontractor.
M1 data center
Digital Realty · Ashburn, Virginia
- Capacity
- 6 MW phase one · 36 MW full buildout
- Scale
- 230,000 sq ft
- Timeline
- Completed November 2018
DPR says Digital Realty selected it for the prototype hyperscale building. The 36 MW figure is critical power at full occupancy, not a public utility meter reading.
WA13
Vantage Data Centers · Quincy, Washington
- Capacity
- 64 MW IT space across five phases
- Scale
- 550,000 sq ft · 17-acre footprint
- Timeline
- Final two phases turned over in fall 2025
The contractor page identifies the client and delivered IT capacity. It does not show the facility’s actual draw at a specific date.
Phoenix data center
Aligned Data Centers · Phoenix, Arizona
- Capacity
- 62 MW first phase · expandable to 120 MW
- Scale
- 550,000 sq ft across three buildings
- Timeline
- Completion date not stated on the project page
Skanska identifies Aligned as the client and construction management as its service. Capacity is design context, not a meter reading.
B009 data center upgrade
IBM · Boulder, Colorado
- Capacity
- No IT-load figure stated
- Scale
- 100,000 sq ft
- Timeline
- Date not stated on the project page
The contractor page names IBM, describes live-site upgrade work, and reports removal of three 1,750 kW generators. Removed generator nameplate is not facility demand.
FIN02 expansion
atNorth · Espoo, Finland
- Capacity
- 45 MW gross capacity across the full facility
- Scale
- 11,200 m² expansion
- Timeline
- Started April 2026; completion expected Q3 2027
Skanska names atNorth as its client and distinguishes the expansion scope from the 45 MW gross capacity of the whole facility.
Zürich campus building ZRH12
Vantage Data Centers · Winterthur, Switzerland
- Capacity
- 8 MW
- Scale
- Three-story ground-up building
- Timeline
- Construction progress documented in October 2025
DPR names Vantage as the client. The 8 MW figure describes the planned building, not measured consumption.
Live data-center floor fit-out
Confidential colocation client · Singapore
- Capacity
- No comparable MW stated in the cited project source
- Scale
- One floor in a four-story live facility
- Timeline
- Completion date not stated on the project page
The contractor and place are public; the customer is not. Cloud Draw leaves the owner confidential rather than attempting to infer it.
DUB1 campus first two phases
Vantage Data Centres · Profile Park, Dublin
- Capacity
- 52 MW critical IT load · 100 MVA generation plant kept separate
- Scale
- 22 acres · one 32 MW facility + one 20 MW facility
- Timeline
- Main-contractor appointment announced April 2024; current project page documents initial-phase delivery and continuing work
Sisk is the main contractor. Sensori is named for MEP, security, data, BMS, two multi-fuel generation-plant buildings, and BESS work. The 52 MW critical IT load is not the 100 MVA generation-plant capacity, actual consumption, or actual output.
DB3 / DB4 / DB5 data-center campus
Confidential multinational client · Dublin
- Capacity
- 50 MW headline · 47 MW itemized across the three phases
- Scale
- DB3 16 MW · DB4 13 MW · DB5 18 MW
- Timeline
- Completed over three phases across six years; calendar dates not stated
The client remains confidential. Sisk states 50 MW total, while the phase figures on the same page add to 47 MW. Cloud Draw preserves both claims and does not reconcile the discrepancy.
Docklands data-center campus first building
Ada Infrastructure · Royal Docks, London
- Capacity
- 70 MW first building · 210 MW stated campus capacity
- Scale
- First of three 70 MW data-center buildings
- Timeline
- Shell and core due mid-2028; first-building occupation targeted by end of 2028
McLaren is contracted for the first building's shell and core, campus infrastructure, and a future district-heating interface—not the entire technical fit-out. The stated MW are planned building and campus capacity, not actual draw.
LON01B2 Brent Cross
Pure Data Centres · Brent Cross, London
- Capacity
- 70 MW new facility · 90 MW total campus capacity
- Scale
- 23,186 m² · 249,572 sq ft
- Timeline
- Expected practical completion Q2 2029
Glencar is appointed for the West Cold Shell: substructure, superstructure, envelope, and roofing. It is not presented as the full-campus or technical-fit-out contractor. Capacity is planned, not metered demand.
Amsterdam 48 MW data center
Confidential global lease provider · Amsterdam
- Capacity
- 48 MW design capacity
- Scale
- 41,500 m² · turnkey PCSA, early works, CSA, MEP, and commissioning scope
- Timeline
- Started December 2025; completion target not stated
The source identifies the client only as a Global Lease Provider, not a legal entity. Cloud Draw keeps it unnamed. The 48 MW is design capacity, not actual load.
LEW Green Data Center
LEW TelNet · Augsburg
- Capacity
- 1.8 MW IT capacity
- Scale
- More than 600 racks · 1,900 m² server area
- Timeline
- Built in 2024
GOLDBECK names LEW TelNet and the 1.8 MW IT capacity. Its 100% renewable-energy operating claim is not a meter reading, an actual consumption figure, or proof of a facility-specific generator.
Singapore data-center campus
Meta · Tanjong Kling, Singapore
- Capacity
- No public facility MW figure on the builder sources
- Scale
- About 170,000 m² · 1.8 million sq ft · S$1.4B
- Timeline
- Broke ground in 2018; construction topped out March 14, 2022
Fortis names Meta as the client. Current Meta materials still use once-completed language, so Cloud Draw does not infer an operating date. Renewable-project MW figures are not this facility's capacity or draw.
Singapore Woodlands data center
Global Switch · 7 Woodlands Height, Singapore
- Capacity
- 22 MW operator-listed facility capacity
- Scale
- Six stories · ten data suites
- Timeline
- Contract award announced May 18, 2018; current operator portfolio lists the facility
Gammon names Global Switch and the construction scope but does not state MW. The 22 MW comes from Global Switch's current portfolio and is not a meter reading or actual draw.
B2 data center
NEXTDC · Fortitude Valley, Queensland
- Capacity
- 6 MW design / facility capacity
- Scale
- 8,200 m² current page · 7,500 m² completion sheet
- Timeline
- Completed in 2018 after a 46-week project
FDC names NEXTDC and a 6 MW conversion. The current page lists 8,200 m² while the completion sheet lists 7,500 m²; Cloud Draw preserves both source figures. Six MW is not measured draw.
THE KNOWN QUEUE / 04
Who says they are building what.
This is the public queue, not a promise. Compare every operator label and state, then put the data-center pipeline beside the power projects and grid additions that have their own source.
MW needs a label. Directory MW can describe a building, phase, campus, or planned design. It is not actual draw. One campus can have several rows, phases can overlap, and missing MW is not zero.
Supply stays separate. EIA generator additions, utility plans, PPAs, onsite plants, backup generators, and load forecasts are different measures. We do not add them together.
…facility rows + power documents
U.S. DEPTH · CURRENT SNAPSHOT
Growth, listed power, and the grid context beside it.
This desk makes lifecycle, listed MW, dominant state power mix, ISO/RTO region, and exact power-evidence relationships searchable. It does not turn separately sourced numbers into a facility electricity bill.
Search power classes and facilities →DEVELOPMENT PROFILE / G1
Development stage in the current U.S. directory.
Record count and sum of listed capacity; this is a current snapshot, not a historical time series.
A row may be a building, phase, project, or campus. Listed MW is not metered demand. Rows without MW are excluded from capacity sums—not treated as zero. A dated evolution line will appear only after at least two sourced directory snapshots exist.
STATE MIRROR / G2
Data-center queue beside scheduled grid additions.
A state comparison of two separately sourced measures. The sides are not linked supply.
Independent directory scale: 0–0 MWIndependent EIA schedule scale: 0–0 MW
Loading directory rows…
Directory MW is listed facility capacity. EIA MW is preliminary scheduled net-summer generating capacity or storage power capacity. EIA additions are not reserved for data centers, and the two sides should not be added or subtracted. The global discovery layer is excluded because comparable MW and power fields are not researched there.
Open the exact-value table
| State | Selected rows | Listed capacity | Lifecycle MW breakdown | MW coverage | EIA generation | EIA storage | Scheduled power breakdown | 2024 dominant mix | Map |
|---|
SEARCHABLE POWER CLASSES / G3
Keep every power relationship in its own lane.
These document classes are exact. Their MW values describe different measures, directions, and scopes, so this desk never totals them.
onsite_primesupply · facility / campusColossus 2 permanent onsite plant
SpaceXAI / xAI · Southaven, Mississippi
1,200 MW- Relationship
- Onsite prime generation
- Fuel
- Combustion turbines; fuel is not stated on the cited operator update
- Source scope
- One operator campus; this is generation nameplate, not a public facility draw figure
- Timing
- Permanent plant under construction; 69 temporary mobile turbines scheduled for removal by July 2027
Named generation intended for normal onsite service. Nameplate is not facility draw.
emergency_backupbackup · facility / campusProject Raspberry emergency generator fleet
Google / Helio Capital LLC · Daleville, Botetourt County, Virginia
≈326 MW- Relationship
- Emergency backup generation
- Fuel
- Ultra-low sulfur diesel or renewable diesel / HVO
- Source scope
- Three-building planned campus; about 326 MW of listed electric generator sets, excluding fire-pump engines
- Timing
- Minor NSR application received May 13, 2026
Emergency nameplate kept outside normal power supply.
portfolio_onsitesupply · portfolioEquinix–Bloom onsite fuel-cell portfolio
Equinix + Bloom Energy · 19 U.S. IBX data centers in six states
100+ MW- Relationship
- Onsite portfolio generation
- Fuel
- Solid oxide fuel cells; feedstock is not specified in the cited 2025 release
- Source scope
- Portfolio total; not allocated to individual facility rows without site-level documents
- Timing
- Portfolio exceeded 100 MW in February 2025
Generation reported across a portfolio. Do not assign its total to one facility.
offsite_contractcommercial · contract / portfolioGoogle–Kairos advanced nuclear agreement
Google + Kairos Power · U.S. sites to be selected
Up to 500 MW- Relationship
- Offsite contracted generation
- Fuel
- Advanced nuclear
- Source scope
- Grid supply agreement; not onsite generation and not assigned to one data center
- Timing
- First SMR targeted for 2030; additional deployments through 2035
A commercial matching or delivery arrangement, not automatically a facility fuel mix.
offsite_contractcommercial · contract / portfolioGoogle–TVA–Kairos Hermes 2 project
Google + TVA + Kairos Power · Oak Ridge, Tennessee / TVA grid
50 MW- Relationship
- Utility-delivered contracted generation
- Fuel
- Advanced nuclear
- Source scope
- TVA-grid supply for Google data centers in Montgomery County, Tennessee, and Jackson County, Alabama
- Timing
- Power targeted beginning in 2030
A commercial matching or delivery arrangement, not automatically a facility fuel mix.
offsite_contractcommercial · contract / portfolioGoogle–Elementl early-stage nuclear sites
Google + Elementl Power · Three potential U.S. sites; locations undisclosed
1,800+ MW- Relationship
- Early-stage offsite development
- Fuel
- Advanced nuclear
- Source scope
- Three potential sites at 600 MW or more each; Google has an option for commercial offtake
- Timing
- Elementl target: significant capacity online by 2035
A commercial matching or delivery arrangement, not automatically a facility fuel mix.
offsite_contractcommercial · contract / portfolioCrane Clean Energy Center restart
Microsoft + Constellation · Londonderry Township, Pennsylvania
835 MW- Relationship
- Offsite power purchase agreement
- Fuel
- Nuclear
- Source scope
- Grid generation matched to Microsoft data-center electricity in PJM; not onsite production
- Timing
- 20-year PPA; Constellation later accelerated restart work toward 2027
A commercial matching or delivery arrangement, not automatically a facility fuel mix.
offsite_contractcommercial · contract / portfolioClinton Clean Energy Center PPA
Meta + Constellation · Clinton, Illinois
1,121 MW- Relationship
- Offsite power purchase agreement
- Fuel
- Nuclear
- Source scope
- Plant output and clean-energy attributes; not onsite production or one facility’s draw
- Timing
- 20-year agreement beginning June 2027; includes a 30 MW uprate
A commercial matching or delivery arrangement, not automatically a facility fuel mix.
utility_plansystem supply · utility territoryGeorgia Power 2028–2031 certified capacity portfolio
Georgia Power / Georgia PSC · Georgia Power retail system; includes out-of-state PPAs
9,885 MW- Relationship
- Utility certified capacity resources
- Fuel
- Mixed portfolio: gas combined cycle / combustion turbines, batteries, solar plus batteries, and PPAs; not one fuel or generator
- Source scope
- Georgia Power retail and regional resource portfolio responding to large-load growth; it is not dedicated to one operator
- Timing
- Commercial-operation dates run from November 2027 through December 2030; certification orders issued in December 2025
System planning or procurement; not dedicated to a data center unless the source says so.
regional_load_forecastload · utility / regionDominion Virginia data-center load forecast
Dominion Energy Virginia / Virginia SCC record · Dominion Virginia service territory
1,972 → 7,239 MW- Relationship
- Regional metered-load forecast
- Fuel
- Utility system portfolio; no dedicated facility generation assigned
- Source scope
- Customer-class regional load, not one campus and not generation nameplate
- Timing
- 1,972 MW metered data-center load in 2023; 7,239 MW projected for 2035
Expected demand, not generation and not a facility meter reading.
DEMAND OUTLOOK / P1
Published scenarios.
Not a crystal ball.
The global and U.S. projections below come from the IEA and Lawrence Berkeley National Laboratory. The U.S. pipeline card is our own arithmetic on directory rows with listed capacity. It is a pressure scenario—not a forecast of what will actually connect.
415 → 945 TWh
2024 estimate to 2030 base case · Just under 3% of global electricity in the base case.
IEA base case. It is an electricity-demand scenario, not a facility count or guaranteed outcome.Open IEA source ↗176 → 649 TWh
2023 historical to 2030 reference · 11.8% reference case; 9.5–15.3% scenario range.
The 2023 historical value is from LBNL’s 2024 report; the 2030 reference and range are from the 2025 update published in June 2026.63,006 + 282,998 MW
63,006 MW on 1,237 of 3,567 operational rows plus 282,998 MW on 561 of 1,058 planned or construction rows.
Not every row will be built; phases can overlap; listed capacity is not actual draw; rows without MW are excluded.WATER NUMBERS / 05
Water figures with a source.
This first national layer uses Google’s reported 2024 U.S. location totals. A location may include several buildings. We do not copy the same total onto every facility row.
POWER NUMBERS / 06
Follow the power.
Start with the facility, then move outward: listed load, any public onsite or contracted generation, the grid region, and the state’s generation mix. Each step has its own scope and source.
What generates electricity here?
Do not read this bar as a facility contract. It is the state’s 2024 in-state generation mix. Imported power, a serving utility’s portfolio, a PPA, and onsite generation can all differ.
Colossus 2 permanent onsite plant
SpaceXAI / xAI · Southaven, Mississippi
1,200 MW- Actual draw
- No single-facility figure found
- Fuel / technology
- Combustion turbines; fuel is not stated on the cited operator update
- Status
- Under construction
- What is planned
- Permanent plant under construction; 69 temporary mobile turbines scheduled for removal by July 2027
- Scope
- One operator campus; this is generation nameplate, not a public facility draw figure
The operator says the 1.2 GW plant will use 41 permanent turbines and references a March 2026 Clean Air Act permit. This atlas does not treat that statement as a regulator-issued permit document.
Operator original disclosure · open original document ↗FACILITY RECORDS / 07
The rows behind the dots.
Search the directory, narrow the scope, then open the original record or send a row back to the map.
9 matches Showing 9
HIGH FALLS CASE FILE / 08
Start local. Check the receipts.
Cloud Draw started with Atlanta and the Upper Towaliga watershed. These four records show the standard for the national work: name the number, name its scope, and link the document.
GOOGLE · DOUGLAS COUNTY, GEORGIA
1.21 MGDBig draw. Mostly reclaimed.
Google reports 444.1 million gallons withdrawn in 2024. It says 98.3% was reclaimed wastewater. The site discharged 77.2 million gallons and consumed 366.9 million.
Open report ↗META · STANTON SPRINGS, GEORGIA
106K GPDA reported actual, not a guess.
Meta reports 146 megaliters withdrawn in 2024—about 105,700 gallons per day. The company says the site uses municipal water, not groundwater.
Open data index ↗QTS · FAYETTEVILLE CONSTRUCTION
30.2M GALThe meter failed. The bill came later.
County records show two connections were back-billed after their use had not been captured since July 2024. QTS said the water was used during construction and that operating cooling would be closed loop.
Open county record ↗EDGED · ATLANTA
0 COOLING WATERZero for cooling. Not necessarily zero.
Edged says its Atlanta campus uses no water for cooling. The company does not publish total domestic or process water for the site.
Open company statement ↗OTHER USEFUL MAPS / 09
Open these too.
No public project has every facility, meter, permit, power contract, and ownership record. These tools cover different parts of the picture. Cloud Draw links them here so you can compare methods and find the gaps.
DC Map
What it adds: Open U.S. facility locations, project status, listed capacity, grid data, risk, and water-stress screening.
What it does not prove: Its national rows do not provide a facility water bill or site power meter.
Open project ↗02Data Center Map
What it adds: A long-running operator and service-provider directory with a published counting method.
What it does not prove: A commercial listing still needs to be checked against permits and utility records.
Open project ↗03Cloudscene
What it adds: Operator rankings based on portfolio density, networks, fabrics, and cloud connections.
What it does not prove: A market ranking is not a permit, water, or meter record.
Open project ↗04Baxtel
What it adds: Facility inventory, development tracking, site plans, procurement, and company research.
What it does not prove: Useful market tracking. It is not a public water ledger.
Open project ↗05DC Byte
What it adds: Analyst-maintained coverage of self-build, hyperscale, and colocation portfolios.
What it does not prove: Much of the detail requires a subscription, and source documents are not the main product.
Open project ↗06datacenters.world
What it adds: A global, map-first directory with a stated methodology and API.
What it does not prove: A global location map is not a facility water or power audit.
Open project ↗07PNNL / DOE Data Center Atlas
What it adds: Open footprints, municipal water service areas, grid and fiber layers, and growth scenarios.
What it does not prove: Infrastructure proximity is context—not proof of a facility contract or meter.
Open project ↗08Baker Institute infrastructure map
What it adds: Facilities shown beside generation, transmission, fiber, prices, water stress, and public sentiment.
What it does not prove: Nearby infrastructure does not prove a facility contract or ownership relationship.
Open project ↗09WaterByCounty
What it adds: County screening with USGS water data, EPA discharge permits, OSM, and PNNL sources.
What it does not prove: County pressure is not a facility water audit.
Open project ↗10Ceres · Drained by Data
What it adds: A cumulative direct-and-electricity water-risk framework and regional case study.
What it does not prove: A pressure model cannot replace a campus meter, contract, or withdrawal permit.
Open project ↗11Compute Atlas
What it adds: An open, source-cited U.S. map of compute sites, capacity, friction, power projects, subsidies, and civic impacts.
What it does not prove: Its scope and inclusion rules differ from this directory, so counts should not be merged without record matching.
Open project ↗12OpenStreetMap data centers
What it adds: The open, community-maintained global observations used for Cloud Draw’s outside-U.S. map layer.
What it does not prove: Coverage is uneven and one campus can be represented by a site, building, point, or several of them.
Open project ↗HOW TO READ THIS / 10
The fine print.
In plain English.
Water terms are not interchangeable. Withdrawal comes in. Discharge goes back. Consumption is the portion not returned to the same immediate system. Google’s daily figures are annual 2024 totals divided by 366.
Stress describes the area, not the facility. It does not prove local withdrawal, drinking-water use, or responsibility for a shortage.
Closed loop does not mean zero water. It describes cooling. A site can still use water for filling, makeup, domestic service, and construction.
No public figure is not zero. It means the linked record has no facility-level daily number or source mix.
A row is not always a campus. It may be a building, phase, project, or campus. The totals count records, not surveyed parcels.
Operator is not the same as owner. A company label does not prove parcel ownership, contract control, or responsibility for a utility account.
Planned means planned. Projects pause, change, and get cancelled. Check the linked record and local filing for current status.
A utility permit is not automatically a site allowance. We show an allowance only when a source ties it to the facility or clearly defines the service relationship.
MW needs a label. Listed capacity, meter draw, backup generation, onsite generation, a power contract, and a utility plan are different numbers. We do not add them together.
A state fuel mix is context, not a facility claim. EIA Table 5 shows what generated electricity inside the state in 2024. It does not identify the serving utility, imported electricity, a private PPA, or what passed through one facility meter.
“Related power document” is intentionally broad. It can mean a facility record, an operator portfolio agreement, a state utility plan, or a regional load forecast. The document card names that scope before it names the megawatts.
The global layer is a discovery index. It contains OSM observations, not a complete operating registry. Country and region labels are derived from Natural Earth; local-area labels name whether they came from an OSM tag or a nearby-place fallback.
A builder name needs a project document. Cloud Draw does not assign a contractor from proximity, reputation, or an unnamed market announcement. Joint ventures and confidential clients stay labeled as the source presents them.
Outlooks are scenarios. IEA and LBNL electricity figures describe modeled demand ranges. Cloud Draw’s pipeline arithmetic sums only directory rows with listed MW and does not assume every project connects.
The database is meant to grow. It currently combines the U.S. directory, the open global discovery layer, 23 Google water locations, 26 sourced company profiles, project-specific builder records, and the High Falls case files. New permits, utility filings, and company reports can be added without changing the basic rules.