How GigaTown works

The breakthrough is the architecture between the systems.

Energy plants, data centers, greenhouses, reservoirs, homes, and public institutions already exist. GigaTown arranges their commercial, physical, and civic interfaces so each can make the others more valuable.

Three architectures

A connection only works when all three layers agree.

Physical

Energy, heat, water, land, logistics, and buildings must connect at the right grade, location, timing, and reliability.

Commercial

Every asset needs an accountable owner, customer, tariff or funding path, operating duty, and allocation of risk.

Civic

The host community helps shape public boundaries, service expectations, local participation, and durable shared value.

GigaTown North concept view into a FarmCo greenhouse with rows of crops in summer
NorthCold, firm power, useful heat, and year-round growing.
GigaTown South concept showing mountain water storage, solar infrastructure, agriculture, town, compute, and industry
SouthWater, elevation, solar resources, agriculture, and staged development.

Portfolio system

Design the flows and the feedback together.

This is not a one-way chain. Community priorities and productive demand change what infrastructure should be built; operating data and resource limits change how the region grows.

The resource cascade

Use the right resource at the right grade.

A useful output is not automatically a useful input. Temperature, pressure, chemistry, distance, timing, reliability, regulation, and cost determine whether a connection is real.

Energy quality matters

Low-temperature recovered heat can serve greenhouses, warm-water networks, or efficient buildings. It should not be credited as though it can perform high-temperature industrial work without an additional energy source.

Water quality matters

Water systems remain isolated where public health, crop protection, operations, or regulation require it. An exchanger can transfer energy without mixing fluids.

Reliability matters

Beneficial users are customers, not required safety infrastructure. A thermal utility must still reject heat independently when a greenhouse, public pool, or industrial customer is unavailable.

Designed boundaries

Integration does not mean one owner or one pipe.

Clear interfaces make a connected system governable.

Each regional company, cooperative, utility, or public entity receives explicit assets, customers, meters, operating duties, and risks. Physical loops can exchange energy while remaining separated. Private development and public administration remain distinct.

Independent operation is non-negotiable.Normal operation, emergency operation, shutdown capability, final heat rejection, and regulated safety functions cannot depend on a voluntary community or agricultural customer.

The civic operating system

Community participation changes the design.

Housing supply, public services, local enterprise, agricultural continuity, public assets, utility quality, construction impacts, and governance are not side effects to address after the engineering is finished.

They are inputs that shape phasing, ownership, corridors, tariffs, service agreements, and the public bargain.

“The community should be stronger because we are here.”

Regional adaptation

The method stays consistent. The system changes with the place.

North begins with cold, firm power, useful heat, and winter agriculture. South begins with irrigation, solar resources, elevation, water resilience, and a separate public district.