OS and HMLR geometry, UPRNs, Planning Data, transport, flood, ecology, heritage and policy.
Know which data-centre sites deserve diligence.
siting.io turns a site boundary and operational brief into an explainable early qualification. It tests compute load, connection programme, power quality, cooling, water, fibre, resilience, planning and delivery evidence before land, connection and technical diligence costs escalate.
One actual site.
A complete operating envelope.
The map retains the real Manor Farm geography. The controls restore the wider product idea: compute and energy demand, target years, phasing, power stability, cooling and water, network diversity, land readiness and resilience all change the qualification.
The Secretary of State allowed the appeal and granted permission on 10 June 2026, subject to conditions. Approval does not prove grid, technical or commercial delivery.
Open the decision →Scores change with the brief. Source counts show the current inventory mapped to each domain.
The decision is narrow.
The system behind it is not.
The MVP returns one qualification decision, but it draws on a broader specification across seven domains. The labels below distinguish what is interactive now, what is evidenced in the Manor Farm case and what remains specified for the roadmap.
Energy & grid
Seventy datasets.
Nine evidence clusters.
The inventory is already substantial, but it is not yet an England-wide production pipeline. Its geographical bias is exposed directly: 34 sources cover South East England, 27 London and 9 the UK excluding Scotland.
Depth exists before national consistency.
This is useful evidence, not a weakness to hide. The production architecture combines the current operator-rich layers with a national geometry and policy core, then adds customer-supplied offers, title and studies.
DNO forecasts and power flows, water evidence, local policy, fibre, heat and market signals.
Connection offers, title, route surveys, power-quality studies, programme and commercial intent.
Rules before weights.
Evidence before confidence.
The map is one evidence surface. The product is the tested relationship between a parcel, an operational envelope, 43 potential capabilities and evidence of unequal quality.
Frame the operating envelope
Combine real geometry with load, years, ramp, cooling, water, power quality, resilience, latency and land assumptions.
Site + operational briefAssemble the evidence fabric
Join national, operator, case and customer evidence while preserving source dates, resolution, coverage and licence.
Facts + lineage + gapsTest gates, then trade-offs
Resolve hard programme conflicts first, then compare seven domain signals and run scenario sensitivities.
Rules + MCDA + sensitivityIssue a decision record
Return a circulable judgement with reason codes, assumptions, confidence, missing evidence and targeted next studies.
Decision + audit trailActual sources.
Different levels of certainty.
Public data can establish geographic and policy context. It cannot, by itself, prove network headroom, title, consent or technical deliverability.
Map boundary and scheme footprints were digitised from the public drawings for this prototype. They are indicative display geometries. OpenStreetMap is used with attribution; a production product would use an appropriately hosted OSM-derived tile service.
The queue is large.
Deliverability is not.
NESO's 2026 demand call covered 152 data-centre phases. Only 32% had secured off-takers, while 81% were open to phased, ramped or non-firm routes. Developer intent and deliverability are not the same thing.
NESO demand call for input →Extensive specification.
Honest product stage.
siting.io has a 43-feature specification, a mapped 70-dataset inventory and a 13-area benchmark design. This website demonstrates the operating-envelope logic against one real public case. It does not yet constitute a national data pipeline, verified engineering model, customer pilot or evidence of willingness to pay.
Review the decision, not just the interface.
The next useful evidence is expert challenge of this memorandum against what was knowable at the time, followed by a design partner and a measured pilot.