# NeuronPlant

> We Build AI Factories. One Partner. Design Authority and Delivery. The Entire AI Factory.

This file is a short map. Full technical corpora live at /llms/{collection}.txt, on the HTML topic pages, and in /llms-full.txt organized by collection. Prefer MCP or JSON over scraping HTML.

NeuronPlant is the design authority and the single accountable delivery partner for an AI factory. You bring the AI requirement. NeuronPlant engineers the architecture, can purchase the required equipment against that architecture, coordinates suppliers, integrates, validates, and hands over the factory. We do not build the data center. The hall operator supplies and operates the room.

NeuronPlant is the design authority and the single accountable delivery partner for an AI factory. NeuronPlant engineers the architecture, can purchase the required equipment against that architecture, coordinates suppliers, and delivers the GPU, TPU, and ASIC plant. The hall operator supplies and operates the room. Sequence: Site → Power → Cooling → Compute → Network → Structured cabling & passive infrastructure → Storage → Platform → Operate. Site in that line is the hall we occupy, not a campus we pour. Not an NVIDIA Cloud Partner. NVOnline packs are named, not reprinted. Customer names and customer specifications publish only after written approval (same gate as /customers).

## MCP

- [MCP server](https://neuronplant.com/api/mcp): Streamable HTTP, read-only, no auth. Cursor config is on https://neuronplant.com/mcp.
- [MCP connect page](https://neuronplant.com/mcp): tools, resources, and client snippets.
- [MCP server card](https://neuronplant.com/.well-known/mcp.json)
- [Structured JSON](https://neuronplant.com/api/knowledge): full catalog index.

## Site map

- [Homepage](https://neuronplant.com/): Buying-story homepage. From AI requirement to a delivered AI factory. One customer journey: Requirement → Facility Fit → Architecture → Procurement → Coordination → Deployment → Validation → Handover. Nine plant layers are canonical. System view lives on /what-we-build#system-view, unnumbered. Header actions: Start a Project and Become a Partner.
- [What we build](https://neuronplant.com/what-we-build): Nine plant layers of the accelerator cell including structured cabling & passive infrastructure, the AI platform, operate / monitor, and Expansion / Day-1. Site is the hall we occupy.
- [Capabilities](https://neuronplant.com/capabilities): How each plant layer is delivered. Facility as constraints of the hall we occupy, rack PDUs as a spec job, fabric decision (converged vs dedicated), Quantum and Spectrum-X families with cited SuperPOD names, storage sized as a requirement, operate / monitor, and cited model profiles for sizing. Not NP as a data-center general contractor.
- [AI factories](https://neuronplant.com/ai-factories): Factory templates NeuronPlant can deliver for private AI, training, AI-as-a-Service, sovereign, and hall-scale plants, plus how we read the public NVIDIA DSX campus map.
- [Models](https://neuronplant.com/models): NVIDIA-cited model and platform references from the public NIM support matrix.
- [NVIDIA DSX](https://neuronplant.com/dsx): How we read public NVIDIA DSX campus docs when a hall partner or customer program needs that language. NVOnline packs named only. No partnership claim. Not a campus NeuronPlant builds.
- [Structured cabling & passive infrastructure](https://neuronplant.com/cabling): Structured fiber, copper, polarity, test records, and the plant built for tomorrow.
- [Growth is an architecture evolution, not a node count.](https://neuronplant.com/expansion): 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.
- [Applications / Platform](https://neuronplant.com/applications): AI platform layer after the accelerators exist: serving, RAG services, NIM / runtime integration, and the data path from sources to workload. Large serving includes a KV hierarchy (HBM → RAM → NVMe → remote). Runtime / operate is Docker, Kubernetes, and observe.
- [Runtime / Operate](https://neuronplant.com/runtime): Docker images, Kubernetes 3+3 cell, VM-capable masters, production plane (CPU vs accelerator workers, registry, secrets, identity, RAG services), Fluent Bit as the example log shipper. Durable names, not a SKU catalog.
- [Projects](https://neuronplant.com/projects): Factory records by sector. Includes a cautionary structured-cabling failure, not a win.
- [Customers](https://neuronplant.com/customers): Named only after written approval. Until then, sector and region.
- [Insights](https://neuronplant.com/insights): Short technical notes. Constraints first.
- [About](https://neuronplant.com/about): Why the firm exists: design authority and single accountable delivery partner from AI requirement to a delivered factory. Not a DC contractor. Plus the integrity stance. Company collection also holds partners, partner intake, and customers.
- [Partners](https://neuronplant.com/partners): Two kinds of partners behind a NeuronPlant delivery. Technology: OEMs and platforms that make the accelerator plant (the stack). Delivery: integrators, operators, and hall/colo suppliers who provide the room (who ships a layer). The customer still buys one project from NeuronPlant. NeuronPlant is not the colo. No NVIDIA or Lenovo logo wall. No NCP claim.
- [Become a partner](https://neuronplant.com/become-a-partner): Engineering intake to qualify as Technology or Delivery, then by layer (including hall), supply, geography, and NVIDIA/DSX relationship.
- [Client portal preview](https://neuronplant.com/portal): Preview of the customer's project environment: status, architecture, facility, suppliers, procurement, milestones, documentation, and handover. Not live. Does not authenticate. Not the product. Not a hall marketplace. No invented customers or project records.
- [MCP server](https://neuronplant.com/mcp): How to plug the published factory record into Cursor, Claude Desktop, and other MCP clients.
- [llms.txt](https://neuronplant.com/llms.txt): Machine-readable index of routes and knowledge collections for agents.

## Knowledge collections

- [Site routes](https://neuronplant.com/llms/route.txt): Important pages and what they contain. (https://neuronplant.com/)
- [Plant layers](https://neuronplant.com/llms/system.txt): Site, power, cooling, compute (GPU, TPU, other ASICs), network, structured cabling & passive infrastructure, storage, platform, operate. (https://neuronplant.com/what-we-build)
- [NVIDIA platforms](https://neuronplant.com/llms/platform.txt): NVIDIA DGX B200 / NVIDIA DGX B300 nodes and NVIDIA DGX GB200 NVL72 / NVIDIA DGX GB300 NVL72 racks, cited from public NVIDIA pages. (https://neuronplant.com/models)
- [NVIDIA switches](https://neuronplant.com/llms/switch.txt): Quantum InfiniBand and Spectrum-X Ethernet families, then cited SuperPOD names for those jobs. (https://neuronplant.com/capabilities#nvidia-switches)
- [Storage by workload](https://neuronplant.com/llms/storage.txt): Training, RAG, inference, and HPC mixes as different machines. Large inference also has a KV / prefix cache tier. (https://neuronplant.com/capabilities#storage)
- [DSX campus](https://neuronplant.com/llms/dsx.txt): How we read public NVIDIA DSX campus layers for a hall partner or customer program. Not a campus NeuronPlant builds. NVOnline packs named only, not reprinted. (https://neuronplant.com/dsx)
- [Factory templates](https://neuronplant.com/llms/factory.txt): Private AI, training, AI-as-a-Service, sovereign, and large-scale factories NeuronPlant can deliver. (https://neuronplant.com/ai-factories)
- [Design decisions](https://neuronplant.com/llms/decision.txt): Why this fabric, cooling, storage, sequence, or plant. Rationale in writing. (https://neuronplant.com/mcp)
- [Plant notes](https://neuronplant.com/llms/insight.txt): Short technical notes on NVL72, power/cooling, fabrics, structured cabling, and steered RFPs. (https://neuronplant.com/insights)
- [Cited models](https://neuronplant.com/llms/model.txt): NVIDIA NIM support-matrix profiles used to size nodes vs racks. (https://neuronplant.com/models)
- [Structured cabling & passive infrastructure](https://neuronplant.com/llms/cabling.txt): Fiber, MPO/MTP, patch panels, pathways, copper, polarity, test records. (https://neuronplant.com/cabling)
- [AI platform](https://neuronplant.com/llms/pipeline.txt): Serving, RAG services, NIM / runtime integration, and the data path from sources through ingest, train or RAG, Docker/Kubernetes, KV / prefix cache, operate / observe, handover. (https://neuronplant.com/applications)
- [Delivery records](https://neuronplant.com/llms/project.txt): Anonymized factory records. No invented customer names. (https://neuronplant.com/projects)
- [Customer specifications](https://neuronplant.com/llms/customer-spec.txt): Held behind the same written-approval gate as named customers. (https://neuronplant.com/customers)

## Optional

- [llms-full.txt](https://neuronplant.com/llms-full.txt): concatenated published knowledge, grouped by collection.
- [NVIDIA public sources](https://neuronplant.com/models): cited, not restated as NeuronPlant measurements.
- Held customer specs: sector and region only until written approval.