How we deploy

The first build in South Oregon takes up to nine months; every site after it is a repeatable ninety days plus local approval time. Nothing on the pad depends on a public utility.

The four phases

Identify, land and license, build and cool, onboard and hand over

Two of the four are ours. The second one belongs to the jurisdiction, and it is the one that varies most between markets — which is exactly why it is quoted separately rather than folded into a single headline duration.

Identify
Site parameters, power, latency and land in under-served US markets. A parcel either clears the published gates or it does not, and that is settled before anyone spends money on it.
Duration varies by market and is published per market once the first one is done.
Land and license
Acquire the parcel, then zoning, environmental and building permits. This is the phase the jurisdiction controls, not Xalant.
Local approval time sits outside every duration quoted on this site.
Build and cool
Pads, conduit and connections, then the factory-integrated modules land on them. Cooling is commissioned with the rack line rather than after it.
Onboard and hand over
Commissioning, acceptance against the design targets, then the workload moves in. AI training, inference, HPC and Web3 nodes are all planned to be carried on the same kit.

The two clocks

The first site, then every site

First build

Up to nine months of controlled build in South Oregon. It is longer because it is the one that proves the kit: the enclosure, the generation package, the gateway pad and the commissioning sequence are all being run for the first time.

Every site after

A repeatable ninety days, plus local approval time. Nothing about the module is redesigned between sites, so what is left is the pad, the connections and the commissioning — and the approval path, which is not ours.

Assumptions

What the duration assumes

A timeline is only meaningful with its starting conditions attached. These are ours.

Land: Under control before the build clock starts
Approvals: Granted — their duration is not in the number
Module: Already in the build queue
Power: On-site generation, no utility connection assumed
Access: All-weather road rated for module delivery
Scope: One site, one module, one commissioning sequence

Exclusions

What is not in the number

Local approval time is the big one, and it is not ours to compress. Everything below sits outside every duration quoted on this site.

Local approval time: Zoning, environmental and building permits are outside the quoted duration. They are set by the jurisdiction and they vary by market.
Interconnection: No grid interconnection is assumed, because nothing on the pad is designed to depend on a public utility. If a site chooses to connect later, that queue is its own programme.
Land acquisition: Getting the parcel under control is phase two, not part of the build clock. A site with land already in hand starts further along.
Long-lead equipment: The duration assumes the module is in the build queue. Ordering it is not.
Availability: No uptime figure is published. Xalant is pre-formation with no live sites, so there is nothing measured to publish and a target would read as a commitment.

Size a site and see the time-to-power tier