Field notes / British rural infrastructureConcept series 001 · November 2026
An alternative scale for AI infrastructure

Keep the fields.
Power the future.

What if sovereign AI infrastructure could live alongside British agriculture—not instead of it? A proposal for modest, farm-hosted compute and a closed-loop thermal system that puts waste heat to work.

02 / MODULES HEAT USER FIELD STUDY / NOT TO SCALE
Working landscape / modest intervention
Small by design.
Serious by intention.
02Modular containers
Conceptual configuration
01Working farm
Preserved primary use
∞?No endless energy loop
Physics first, always
01 / A different premise

Infrastructures of place,
not extraction.
The future of British AI needn't flatten the countryside to find somewhere to live.
02 / How the system might work

Compute above ground.
Intelligence below it.

Two compact modules form the visible part of the installation. An insulated thermal network links the servers to useful agricultural heat demand, a heat pump where required, and a carefully engineered ground loop for thermal exchange.

FarmFort / GeoLoop — conceptual thermal section
Mobile view: swipe the section drawing sideways.
Cross-sectional design sketch of a two-container farm AI centre and geothermal ground loopAt the surface there are two AI infrastructure containers, a greenhouse, and a cooling fallback. Below the ground are multiple buried loops, connected to heat exchangers and a farm heat circuit. Winter prioritises useful farm heat; summer illustrates surplus heat rejection subject to ground capacity. COMPUTE PLANT 01 / SOVEREIGN COMPUTE02 / THERMAL PLANT03 / FARM HEAT USERBACKUPREJECTION HEAT EXCHANGERINDEPENDENT CIRCUITS SUBSURFACE THERMAL EXCHANGE GROUND LOOP CONFIGURATION AND TEMPERATURES SUBJECT TO SURVEY PRIORITY: USEFUL HEAT PRIORITY: SAFE HEAT REJECTION

Winter operation: Prioritise greenhouse or building heat where there is real demand. A heat pump may be needed to raise the temperature. The ground loop provides additional exchange where appropriate.

Heat transferGround circuit
A / The visible footprint

Two modules, not a campus.

Indicative 40-foot containers for compute and plant. The actual compound, access, security, electrical equipment and buried infrastructure will need more space.

B / The useful output

Heat is not a nuisance.

Liquid-cooled hardware can make thermal capture more practical. Greenhouses, drying processes and nearby buildings are possible users—provided their temperatures and demand match.

C / The physical limit

The ground is not infinite.

Closed-loop geothermal systems exchange heat with soil or rock. Seasonal storage might be possible; continuous heat injection can warm the ground and reduce cooling performance.

03 / Numbers before narratives

Waste heat is real.
Free energy isn't.

Almost all energy used by IT equipment ends up as heat. But how much can be captured and made useful on a particular farm? That depends on operating temperatures, cooling equipment, demand, heat-pump design and the weather.

The model is deliberately simple. Change the indicative IT load and the percentage of recovered heat a farm can actually use. Watch the remaining heat that still needs a safe destination.

Not a perpetual loop. The ground loop is an engineered heat exchanger, not an unlimited thermal battery. A reliable fallback cooling path is essential. These figures exclude auxiliary electricity and heat-pump gains.
Working model / illustrative only

A day in the field

24 HOURS / CONSTANT LOAD
100 kW
25 kW250 kW
65%
0%100%
2,400kWh / day IT electricity
≈ heat generated
1,092kWh / day potentially
put to local use
1,092 kWh used1,308 kWh remaining

Assumptions: 100% of IT electricity eventually becomes heat; 70% of that heat is potentially recoverable as a useful thermal stream; the “farm use” slider is a percentage of recoverable heat. 1,680 kWh/day is potentially recoverable at the selected IT load. “Remaining” includes uncollected heat and recovered heat not put to use; it must be safely rejected or otherwise managed. Actual results require site-specific thermal engineering.

Practical anchor / what the heat might serve

Give a farmer one number they can picture.

At the default model setting — 100 kW continuous IT load and 65% use of recoverable heat — the page shows 1,092 kWh/day of potentially useful heat. That is enough to suggest a serious greenhouse, crop-drying or building-heating load, but not enough to promise a specific area without thermal design and weather data.

1,092kWh/day potentially used
at the current sliders
Grid firstMain likely bottleneck
before containers
MeasuredNo heat-use claim without
a real site model
Early-stage ask / who should reply

Looking for a small, credible first coalition.

This concept becomes real only if the right people lean in early. The first version needs a host site, a thermal mind, and a compute reality check — not a giant press release.

  • One host farm with a plausible year-round heat use case.
  • One thermal engineer to challenge the loop, temperatures and controls.
  • One compute infrastructure partner to pressure-test power, cooling and workload fit.
  • One policy or funding ally willing to back a properly measured demonstrator.
04 / More than server space

Three returns.
One working landscape.

The project only makes sense if it delivers practical outcomes to the people whose land hosts it, and if a business case survives the engineering reality.

01 — LAND

Farms stay farms.

Farmers retain agricultural use and negotiate fair hosting terms. The installation should complement the landscape, not become the reason it disappears.

02 — SYSTEMS

UK-controlled compute.

Locally governed infrastructure with appropriate security, provenance and workload choices. Distributed nodes may suit some uses—not every AI training workload.

03 — COMMUNITY

Value stays closer.

Explore useful heating, local services and operational income, with measurable benefits and meaningful community engagement—not vague promises.

Engineering reality check

Distributed nodes bring their own costs: electrical grid upgrades, resilient fibre, cooling, maintenance, physical security, planning consent, insurance and operating staff. Smaller footprints do not automatically mean cheaper or lower-carbon compute.

05 / From proposition to proof

One site. One season.
Measured properly.

Rather than asking for a national rollout on faith, build the evidence to know whether a distributed farm-hosted node deserves to exist.

Gate 01 / Discover

Find the farm.

Willing host, plausible heat user, ground conditions, an electrical connection and a fibre route. No container purchase before this work.

Gate 02 / Engineer

Design the plant.

Choose compute workloads, size the heat exchangers and ground loop, establish backup cooling and obtain planning, safety and cost reviews.

Gate 03 / Run

Instrument everything.

Meter IT energy, usable heat, auxiliary power, ground temperatures, cooling reliability, noise, farm impact and economic outcomes.

Gate 04 / Decide

Publish the truth.

Compare actual costs and heat use with the original assumptions. Replicate only if the outcomes justify it, and identify workloads it cannot serve.

Evidence before expansion.Success is not measured in containers deployed. It's measured in viable service, useful heat, resilient operations and a farmer who benefits.
A question for engineers, farmers and policy-makers

What if we built smaller, but thought bigger?

A farm-first British compute demonstrator. Two containers. A properly designed thermal loop. A commitment to measure what actually works.

Looking for
  • One host farm for a measured first demonstrator.
  • One thermal engineering partner.
  • One compute infrastructure partner.
Discuss a demonstrator
Independent early-stage engineering concept. No claim of a funded or operational pilot.