Sites

The pipeline, by code and status.

The ledger

Sites are published as codes and statuses. Engineering, host, and commercial specifics are shared with qualified partners under NDA.

Site development pipeline: site code, state, and status
SiteStateStatus
KY-01KentuckyDEVELOPMENT

Hosts & landowners

Your interconnection is an asset. Put it to work.

  • Revenue from capacity that sits idle a full shift every day.
  • Compute runs opposite your shift. Operations continue uninterrupted.
  • Sealed containerized units on the existing site, behind the existing meter.
  1. 01 Inquiry
  2. 02 Site assessment
  3. 03 Agreement
Start a site conversation

Utilities

Predictable load on existing infrastructure.

  • Storage-buffered load behind existing meters.
  • No new interconnection requests.
  • Compute demand anti-correlated with host demand by design.
  1. 01 Inquiry
  2. 02 Site assessment
  3. 03 Agreement
Talk to AMUN

Communities & government

Local investment without new transmission.

  • Container-scale footprint on sites already in industrial use.
  • No new transmission corridors.
  • Compute on infrastructure the community already hosts.
  1. 01 Inquiry
  2. 02 Site assessment
  3. 03 Agreement
Reach the team

Compute customers

Capacity ahead of the queue.

  • Reserved GPU-hour capacity on 1–3 year terms.
  • MW-scale, behind the meter, on existing interconnections.
  • Deployment timelines set by hardware, not by the interconnection queue.
  1. 01 Inquiry
  2. 02 Site assessment
  3. 03 Agreement
Ask about capacity

Suppliers & EPC

Standardized, repeatable deployments.

  • One design, deployed repeatedly.
  • Vendor qualification for units, storage, and site works.
  • A pipeline across three states.
  1. 01 Inquiry
  2. 02 Site assessment
  3. 03 Agreement
Qualify as a vendor