Initial pilot
A defined first capacity block
Illustrative AI-generated imageAI INFRASTRUCTURE | PHASED DEVELOPMENT
AMOR's preferred initial development model targets approximately 1–3 MW of AI compute capacity, allowing technical performance and commercial demand to be proven before larger-scale capital deployment.
Why start in phases
AMOR uses an initial 1–3 MW IT capacity block to limit early capital exposure and validate infrastructure, operating performance and customer demand before a larger commitment. Modular development means adding coordinated capacity blocks; it does not imply a universal container size, rack count or site footprint.
A defined first capacity block
Commit only at approved gates
Electrical · cooling · network
Customer / offtake before scale
1–3 MW pilot requirements
Use this as an initial screening framework—not a finished design. The target is AI IT load; utility capacity, external connectivity, cooling and physical infrastructure must support the complete facility.
illustrative operating facility demand · initial usable-power screen ≈ 1.5 MW
illustrative operating facility demand · initial usable-power screen ≈ 4.5 MW
These figures do not represent total utility or facility demand.
Two physically diverse fibre paths preferred, with scalable carrier access and a credible path to 100G-class external connectivity where customer requirements justify it.
Separate from the internal AI compute fabric.Liquid-cooling ready: CDU architecture, secondary loop, heat rejection, redundancy and later expansion must be evaluated together.
Building or modular space, equipment access, secure perimeter, electrical and cooling areas, with expansion allowance preferred.
Two physically diverse fibre paths preferred, with multiple scalable carrier services and a path through multiple 100G services—and potentially toward 400G-class connectivity—where the workload requires it.
Separate from the internal AI compute fabric.Liquid-cooling ready: multiple CDU or cooling zones, secondary distribution, heat rejection, redundancy and phased capacity growth.
Larger electrical and cooling footprint, staging and heavy-equipment access, secure operations, with significant expansion allowance preferred.
Illustrative initial site-screening targets only. Actual facility power, connectivity, cooling, redundancy and physical requirements depend on compute architecture, workload, customer requirements and site design. No universal PUE or bandwidth-per-MW formula is assumed.
IT load is the electrical demand of computing, storage and networking equipment within the defined IT boundary. Facility load also includes cooling, pumps, CDUs, electrical losses and support systems outside that boundary.
Power usage effectiveness (PUE) is total data-centre energy divided by IT equipment energy over the same measurement period and boundary. The 1.2–1.4 operating-demand multiplier shown here is an illustrative AMOR planning assumption—not a guaranteed measured PUE, an industry-wide requirement or a substitute for utility and electrical design review.
For a 1 MW IT pilot, this example gives 1.2–1.4 MW operating facility demand and an approximately 1.5 MW initial usable-power screen. For 3 MW IT, the example gives 3.6–4.2 MW and an approximately 4.5 MW screen. Redundancy, reserve capacity, operating conditions and the actual design must be assessed separately.
AWS documents 100 Gbps and 400 Gbps dedicated connection options; NVIDIA distinguishes internal compute traffic from customer uplinks. Those sources support available connectivity classes and architectural separation—not a rule linking WAN bandwidth to megawatts. AMOR’s 100G-class and multi-100G examples are conditional readiness targets, subject to carrier availability and customer requirements.
These are public technical references, not endorsements of AMOR or requirements to use a particular vendor.
What can 1–3 MW serve?
The same megawatt can support very different commercial outcomes depending on hardware, utilization, network design, service model and customer requirements. These are potential categories—not promised customers.
Conditional expansion
The pilot should avoid unnecessarily blocking later growth. Expansion remains a separate decision based on additional power, fibre scalability, land, cooling capacity, approvals, customer demand and capital.
Pilot development
Share the documented power, fibre, site-control and development position. AMOR will determine whether a 1–3 MW pilot warrants further review.