Evidence before
everything.
Independent research into existing and proposed data centres across England, Scotland, Wales and Northern Ireland.
Public understanding, not persuasion
HyperscalerWatch does not advocate for or against data centres, individual developments, operators, applicants or community groups. We explain documented benefits, infrastructure needs, environmental considerations and community perspectives according to their relevance and supporting evidence. We do not impose equal positive and negative coverage or adopt anyone’s campaigning or promotional language.
Developer predictions, technical estimates, authority findings and public representations are different kinds of evidence. An objection or supporting statement is not automatically a finding. We describe the issues without unnecessary personal details of private respondents. Missing information implies neither wrongdoing nor an absence of impacts.
Our editorial policy applies to all research and automated summaries. The same verification standards apply to every project. Any future funding arrangements or potential conflicts of interest must be disclosed.
Corrections and research history
Project pages show dated research updates and sources. Corrections and withdrawals retain prior versions privately; the public history shows when the published research changed. Prepare a correction or suggest missing evidence, or email [email protected]. Reports are research leads and must pass the established evidence checks before a supported correction is published automatically.
The atlas combines source-backed existing facilities and automatically published UK developments. A versioned evidence policy checks sources, location precision, capacity definitions and duplicates. Coverage is incomplete; missing facts remain unknown.
What you are looking at
The public atlas focuses on UK locations. Coverage is growing and is not comprehensive. International records are retained privately for future research, but do not appear in public searches, maps or totals. Profiles distinguish an operating site from a proposal or a separate expansion.
Some existing facility and timeline data are adapted from Epoch AI under CC BY 4.0. The downloads do not include site coordinates: pins use uniquely matched GeoNames locality coordinates, also under CC BY 4.0. They show approximate cities, not verified building positions. Transformations include normalized fields and dated status/capacity estimates; neither publisher endorses this atlas. Records with unresolved geography, overlapping campuses or inconsistent dates remain outside the public dataset.
Autonomous developments, transparent evidence
UK proposals can appear while planning is submitted or approved. Neither stage establishes construction or operation. One authoritative primary source can support a clearly stated fact. Unsupported or contradictory candidates remain outside the public atlas; routine human approval is not required.
Selected UK development facts are adapted from Data Centre Watch under CC BY-SA 4.0, with original planning and developer evidence checked separately. Each adapted project record carries the same licence, attribution and source links. Existing Epoch records retain their own CC BY 4.0 terms. Company roles are explicit: an applicant is not automatically an operator or hyperscaler tenant.
Maximum site demand is shown separately from IT load. Proposed values never enter operational totals. Locality pins are approximate and include accuracy notes. Automated changes retain previous values and can be corrected or retracted when evidence changes.
Development mode is separate from the public database. Every demonstration fixture links to the public demonstration specification, released under CC0-1.0. It is provenance for the demo, not independent evidence.
Power needs a definition
Operational IT load and proposed IT load are separate observations attached to development phases. We do not substitute a planning announcement for operational capacity, or add proposed capacity to operational totals. Unknown values are shown as unknown. All demo figures are explicitly estimated. Production imports also distinguish site/grid power from IT load. Epoch’s projected IT figures are future total capacity, not additional capacity, and remain estimates. Its total facility-power observations are not treated as grid connection ratings. Chip owners and compute users are not silently relabelled as facility owners, operators or tenants. Timeline dates and operational status are Epoch estimates, not independent confirmation by HyperscalerWatch.
A source for every claim
The production data contract requires field-level claim citations, source URLs, reuse licenses, retrieval timestamps and verification states. Multiple sources may disagree; review must preserve that disagreement rather than silently overwrite an observation. Demonstration, unverified, corroborated and verified are distinct states.
Geography with appropriate precision
Coordinates carry a precision designation: city or site for reviewed imports, illustrative for development fixtures. Site-level coordinates require a traceable source and a successful evidence check.
Postcode searches use Postcodes.io and ONS data under the Open Government Licence. They select a nearby rectangular area, extending about 40 kilometres in each direction; they do not measure an exact radius or change project coordinates. Northern Ireland postcode lookup is unavailable because its postcode data has different reuse conditions. Use a town name or the Northern Ireland region filter instead.
Explanations connected to the evidence
Project explanations use versioned editorial rules to select related observations and retain their source identities. Forecasts stay forecasts, different development phases stay separate, and unknown water or electricity use is not filled with an estimate. Inline references open the full observation and its original document. Detailed evidence is collapsed initially to make the main account easier to read.
The map uses public-domain Natural Earth boundaries and GeoNames place labels under CC BY 4.0. Newsreader and Public Sans are supplied locally under the SIL Open Font Licence. No commercial basemap account is required.
Ingestion, separated from exploration
CSV and JSON imports validate approved reuse terms, field-level evidence and duplicate candidates before writing to SQLite. Import history retains accepted and rejected input records. Public requests only read published data; ingestion runs through a separate local command. No ingestion runs inside public page requests. Separate maintenance workers read permitted feeds and primary pages, recording source failures and coverage gaps.
Map attribution
Country boundaries are from Natural Earth (public domain), rendered locally with MapLibre GL JS. Boundary depictions do not express a position on territorial claims. Source geography is generalized and unsuitable for navigation.
Always public
All public functionality is free, with no advertising, subscription prompts or required login. This initial release has no analytics or tracking cookies.