01 / Additive expansion
More of the same cell inside a designed envelope: another accelerator node on the same fabric, another PDU circuit in the reserved row, another NVMe shelf on the same storage machine. The drawings already have a place for it.
NP-XPN/What we build / Expansion
Growth is an architecture evolution, not a node count.
Adding capacity inside a designed envelope is additive. Changing the fabric, the cooling loop, the storage machine, or the hall is a transition. Day-1 names those points. It does not promise unlimited scale.
We do not sell a slogan that scales two DGX nodes to eight. We say how far Day-1 grows without a redesign, and what measurement opens the next investment.
Plant sequence stays Site → Power → Cooling → Compute → Network → Structured cabling & passive infrastructure → Storage → Platform → Operate. Site is the hall we occupy. Expansion is how that accelerator plant grows without pretending the first cell is infinite, and without NeuronPlant becoming the DC.
NP-XPN-ADD/Additive vs transition
How far Day-1 grows without a redesign
Day-1 is a plant with named headroom, not a rack that happens to work. Write the first transition before the first PO. Then the additive path is honest.
- Accelerator count the fabric, PDU, and loop can take without a recable or a new CDU.
- Storage throughput and metadata the chosen machine can take before it becomes a different product.
- Pathway, MPO, and switch-position reserve that the next leaf can land on.
- Platform cell (CPU workers, registry, identity) that does not have to move onto accelerator nodes as the fleet grows.
- Facility: floor load, peak kW, heat, clearance, and the next cage or row of the hall we occupy, or a match to another hall. Not a campus NeuronPlant pours.
NP-XPN-GT/Expansion gates
Compute, storage, fabric, platform, facility.
Each gate has a measurement. When the envelope is full, the next spend is a transition, not another node.
NP-XPN / Gates
What measurement opens the next investment.
Five gates. Not unlimited scale. Additive while the envelope holds. A transition when it does not.
02 / Architecture transition
The envelope is full. East-West compute changes class. Cooling moves from air to liquid. Storage splits. The hall we occupy cannot take the next kW. That is a new architecture, or a different hall supplier, not a purchase order for two more nodes. NeuronPlant does not pour a new campus to keep the slogan.
01 / Compute
HBM, concurrency, or job queue time. The next node still fits the fabric, PDU, and loop, or it does not.
Measure: Utilisation and wait, not a wish for more GPUs. GPU is the common case. TPU and other ASICs use the same gate.
02 / Storage
Throughput, IOPS, metadata, or protection window. Capacity full is often the last signal, not the first.
Measure: Bytes moved and files created under the real job, against the envelope written at Day-1.
03 / Fabric
Oversubscription, optics class, leaf positions, or a plane that can no longer stay isolated.
Measure: Congestion and blast radius on East-West compute, storage/data, North-South, and management/OOB. Port count is not the gate.
04 / Platform
Control-plane load, registry, identity, RAG services, or CPU workers saturating while accelerators wait.
Measure: Whether production Kubernetes still has a CPU plane. Do not grow the fleet by parking services on GPU nodes.
05 / Facility
Normal versus peak kW, floor load, heat, A/B, PDU circuits, clearance, pathways. Rack U left is not power left.
Measure: What the hall we occupy can take. If it cannot, match a hall partner or custom-system supplier. NeuronPlant does not become the DC.
NP-XPN-D1/Two Day-1 strategies
Minimum Day-1 versus a future-ready foundation.
CapEx now versus disruption later. Both are honest when the money path is visible. Unlimited scale is not on the form.
01 / Minimum Day-1
Lower first invoice. Buy what runs the first job.
The first transition arrives sooner: recable, new loop, new storage machine, or a hall that cannot take the next cell.
When: The workload is bounded, the hall is a hard cage, and the customer accepts a written stop.
02 / Future-ready Day-1
More first money in trunks, pathways, PDU reserve, switch positions, CPU workers, and cooling that the next cell can join.
Additive growth stays additive longer. The transition, when it comes, is a named gate, not a surprise outage.
When: The fleet will grow, the hall can take a foundation, and disruption costs more than copper and water now.
NP-XPN-MNY / Money path
The money path stays visible.
Minimum Day-1 and future-ready Day-1 are both honest if the customer sees the same CapEx, disruption, and next-gate cost we see. Integrity before a steered BOM still applies: we do not hide the cheaper first invoice that forces a redesign.
Unlimited scale is not an option on the form.
Intake names the stance. Start a Project.
NP-XPN-ENG/Products vs engineering
Products are not the architecture. Coupled constraints are.
An AI factory is not DGX plus a switch plus storage plus Kubernetes. It is constraints that couple. Engineering those dependencies happens before procurement.
Plant chain
Model → accelerator → network → storage → power → cooling → rack → facility → ops → cost
Change the model class and the accelerator, fabric, loop, and hall move with it. GPU is the common case. TPU and other ASICs still travel this chain.
Data chain
Data → ingest → RAG → inference → KV → capacity
Change the corpus, the embedding, or the session length and the storage machine, the serving plane, and the KV hierarchy move with it. A vector SKU does not size that chain.
Fabrics on Capabilities. Structured cabling reserve on Cabling. RAG and KV on Applications. Production Kubernetes on Runtime.
NP / Intake
Tell us what you need to achieve with AI.
One accountable delivery partner from AI requirement to a delivered factory: site, power, cooling, compute, fabric, structured cabling & passive infrastructure, storage, platform, procurement, and handover. You do not need a vendor list or a hall name first. The hall is a supplier.