08/28/2026
Neocloud and AI factory operators need to think about the network automation layer from the beginning, while the network is still being designed. Once customers and workloads are live, changing the operating model gets a lot harder.
AI cloud environments are constantly changing. Customers come and go, GPU pools are resized, capacity is reallocated, and hardware is replaced. Without an automation layer designed into the architecture from the start, operators will have to modify existing configurations and scripts or introduce automation underneath infrastructure that’s already carrying customer traffic. That creates risk in a live environment that can lead to deployment delays or outages.
We’ve seen this firsthand. Many operators come to Netris after building their initial AI infrastructure without network automation and multi-tenancy in the architecture, but by then, they’re dealing with the technical debt of changing a live network without disrupting customer workloads.
There’s a better approach.
The Netris NAAM (Network Automation, Abstraction, and Multi-Tenancy) platform is purpose-built for GPU clouds and AI factories. Building NAAM into the architecture early means the same operating model used to deploy the network is there to operate it through Day 2 and beyond.
Read our latest blog that explains why the network automation layer needs to come first.
https://netris.io/blog/ai-infrastructure/build-the-network-layer-first/