03 / Bridge capacity
A delayed facility. A parallel path.
Put a bridge-capacity plan alongside the permanent build. Start with the site, the power, and the time between readiness dates.
The application
Two workstreams. One site plan.
Factory work and site preparation run in parallel. The interfaces determine the schedule.
- 01
Prepare the site
Confirm the prepared pad, power feed, and interconnection. Separate verified site facts from planning assumptions.
- 02
Build off-site
Factory build and burn-in happen alongside site preparation. The complete module arrives on one truck and is craned onto the prepared pad.
- 03
Commission, then scale
Commission through a remote sequence and expand pod by pod. Redeployment paths and bridge-period contract terms are agreed privately.
Reference specification
A complete module. A defined reference.
Pod 32 provides a concrete basis for an engineering discussion. Readiness remains a site-specific target.
Explore the technology| Compute | 32 Supermicro HGX B300 nodes |
|---|---|
| GPUs | 256 NVIDIA B300 |
| Racks | 4 |
| Operating load | 645 kW |
| System memory | 128 TB |
| Storage | 983 TB raw NVMe per module |
| Fabric | Rail-optimized 400G Ethernet |
| Fabric throughput | Configurable 3.2 or 6.4 Tbps per node |
| Cooling | Direct-to-chip liquid, redundant CDUs |
| Site water | No site water requirement |
| Tenancy | Single-tenant bare metal |
Schedule study
Find the window.
Compare readiness assumptions before discussing a site-specific bridge plan.
Planning assumptions / Months from today
Illustrative bridge window
9 monthsBetween assumed bridge readiness and permanent-facility readiness.
Method: permanent-facility readiness minus the longer of site and module readiness, with a minimum of zero. All dates share today as their starting point. This planning model is not a deployment commitment. Targeted to be operational within roughly three months of pre-payment, confirmed site by site.
Engineering and operations
Plan around what is known.
Factory, site, integration.
A 24-stage test program follows the module from factory build through site commissioning and integration.
Witnessed acceptance.
Named gates F-1 through F-7 carry witnessable evidence into handoff, including measured NCCL fabric-performance pass bars.
A site-specific schedule.
Targeted to be operational within roughly three months of pre-payment, confirmed site by site. Factory build and burn-in run in parallel with site preparation.
Start a conversation
A little context. A useful call.
Three short questions, then choose a time. No project names or sensitive details needed.
Question 1 of 3
Your role
Only broad answer categories are recorded. Keep sensitive project details for the conversation.
Book without the questions Open Cal.com in a new tabFurther detail
Before we talk.
How is the schedule estimate calculated?
The illustrative bridge window is the time until your permanent facility is ready minus the longer of site preparation and factory readiness, with zero as the minimum. Inputs are planning assumptions in months, not deployment commitments.
How fast can bridge capacity be live?
Targeted to be operational within roughly three months of pre-payment, confirmed site by site. Factory build and burn-in run in parallel with site preparation.
What site work is needed?
A prepared pad and a power feed. The module arrives complete on one truck, is craned onto the pad, and is commissioned remotely.
Can the capacity move later?
Modules arrive complete on one truck and are craned onto a prepared pad, so redeployment paths exist when the permanent site comes online. Exact redeployment and contract terms are defined privately.
Is the calculator a deployment commitment?
No. It compares schedule assumptions only. Site readiness, interconnection, logistics, commissioning, and the final deployment plan require engineering review. Commercial terms are discussed privately.