Industrialized deployment
Prepare repeatable equipment assemblies, rack integration and selected enclosure systems off-site. Foundations, utility connection, heat rejection and final commissioning still need project-specific engineering.
The Aguasto thesis / Development strategy
Why Modular AI Data Centers?
An alternative path from infrastructure planning to operational compute. Standardized engineering and independently deployable facilities can improve execution flexibility where power, land-use and operating requirements are satisfied.
Why nowMore capacity needs
More capacity needs
more deployment models.
Aguasto is developing modular, high-performance data centers and distributed compute infrastructure for enterprise AI and next-generation inference.
Traditional campuses will remain important. Independent inference replicas and dedicated enterprise workloads can also be evaluated in phased facilities, provided latency, reliability, power and customer requirements support the design. Modularity is a deployment strategy, not proof of readiness.
LBNL's June 2026 report describes bottlenecks in connecting large loads. CBRE's H1 2026 evidence shows continued construction alongside power and approval constraints. Aguasto's response is a development thesis; these reports do not validate a particular Aguasto project.
LBNL Speed to Power · CBRE H1 2026
Local water conditions, land-use scrutiny and equipment lead times can add constraints alongside electricity. Phased financing must still support qualified engineering, procurement commitments and customer demand. A modular enclosure changes selected delivery interfaces; it does not remove these obligations.
Review current Raleigh, FERC/PJM, LBNL and reliability evidence, including unresolved source boundaries and continued hyperscale construction.
Six principles. Real dependencies.
Phased capacity
Additional modules can divide development into executable stages. Each phase still depends on authorized electricity capacity, customer demand, equipment delivery and financing.
Distributed operations
Independent sites can host inference replicas and route requests regionally. Geographically separated GPUs do not become one low-latency NVLink training fabric.
Repeatable engineering
Standardized interfaces and acceptance tests can improve consistency across cooling, rack integration, networking and operations. Site-specific loads and conditions still require validation.
Infrastructure flexibility
Containerized systems can be evaluated for different suitable industrial settings. Physical fit is only one part of land-use, utility, environmental and operating feasibility.
Capital deployment
Phasing can limit the commitment needed for an initial stage. Repeated electrical infrastructure, networking and support teams can increase cost per unit of capacity.
Factory work and site work share an interface.
What can progress in parallel?
Selected enclosure systems, electrical assemblies, rack installation and factory checks can be prepared away from the site. Work should proceed against validated mechanical, electrical, cooling and transport interfaces.
Site permissions, utility studies, foundations, access and heat rejection follow their own dependencies. Incomplete interfaces can move rework from the construction site to the factory rather than remove it.
How does readiness become operational?
Factory acceptance is an input to integrated site testing. Protection settings, loads, thermal behavior, network paths and operating handover must be assessed together before a facility supports a customer service.
Schneider Electric: prefabrication and parallel work · OCP: cooling integration and logistics · Vertiv: startup and commissioning
Factory preparation changes part of the sequence.
Conventional and modular developments both need project approvals, electricity, construction interfaces and integrated commissioning. Selected modular assemblies may be prepared off-site while appropriate site work proceeds. This diagram shows dependencies, not guaranteed durations.
Conventional campus
- Approvals & powerSite permissions, utility studies and authorized service
- Equipment & constructionSite construction and equipment integration follow the project schedule
- CommissioningIntegrated protection, cooling, load and operating tests
Modular development
- Approvals & powerThe same permissions and electrical prerequisites
- Equipment & constructionSelected factory assemblies may proceed alongside suitable site work
- CommissioningEquivalent integrated acceptance tests before service
1. Site & approvals
Land use, environmental assessment, geotechnical design and local permits apply to both approaches.
2. Power & utilities
Utility-authorized capacity, interconnection work and an energization plan remain on the critical path.
3. Factory & site works
Modular equipment preparation may proceed alongside suitable site work, subject to completed interfaces and procurement.
4. Commissioning
Integrated load testing, protection settings, cooling performance and operating handover establish readiness.
| Potential advantage | Requirement that remains |
|---|---|
| Prefabricated equipment | Utility interconnection, land use and site-specific civil works. |
| Phased investment | Repeat infrastructure costs, financing, utilization and customer demand. |
| Independent locations | Regional staffing, network latency, software consistency and failover capacity. |
| Existing electrical equipment | Utility-authorized capacity, protection studies and an approved operating use. |
| Standard cooling interfaces | Actual rack loads, fluid quality, heat rejection, commissioning and maintenance. |
Bring the workstreams together.
Keep their dependencies visible.
Factory preparation, appropriate site work and compute-software preparation can progress separately where their accepted inputs allow it. Every branch still meets physical commissioning and workload acceptance. The intended benefit is a shorter path to usable compute; no Aguasto duration or deployment result is available.
Parallel delivery / Dependency study
Three workstreams. One accepted operating configuration.
Selected activity
Engineering
Qualified specialists reconcile electrical, structural, thermal, fire, network and transport interfaces. Repeatability does not replace professional site-specific design.
- Direct prerequisites
- Site qualification · GPU/OEM architecture validation · Module specification
- Evidence required
- Accepted interfaces, design responsibilities and a configuration-specific engineering package.
- Downstream dependencies
- Permitting · Site works · Electrical & cooling integration · Factory manufacture · Factory equipment testing · Shipment · Equipment installation · Physical commissioning · Hardware procurement · Cluster networking · Performance & service validation · Customer provisioning
Keep clusters local.
Route eligible inference workloads.
Independent facilities can host replicated model-serving configurations. A unified operating platform would monitor health, model versions, capacity allocation and data-location policy before directing a request to an eligible replica. Cross-region routing is an application function; local training and tightly synchronized inference have different network requirements.
Distributed inference / Concept study
Independent clusters, conditional workload continuity.
One site isolated
A separate eligible replica may support continuity after site A is isolated.
B needs compatible model versions, tested routing, approved data location and sufficient spare capacity.
Rack-local connectivity
The configured accelerator/server/rack interconnect. Manufacturer system boundaries and supported parallelism determine its role.
Intra-site scale-out
The local cluster’s network, storage and runtime topology. Multi-node execution requires its own measured acceptance.
Cross-region routing
Application requests to eligible independent model replicas. It does not create a geographically distributed low-latency training fabric.
Single-site reliability
Local power, cooling, hardware, network and operating controls determine a facility’s behavior under the tested fault scope.
Fleet-level availability
Multiple facilities require independently assessed failure domains, shared-service dependencies and maintained operating capacity.
Workload continuity
The customer’s model, spare resources, data policy, routing and accepted recovery behavior must all support a tested transition.
Designed for more
resource-conscious AI infrastructure.
Adaptability and appropriate reuse can reduce some avoidable work. Actual safety, transport limits, replacement needs and lifetime impacts determine whether reuse is suitable. Modular equipment is not indefinitely reusable.
- Evaluate appropriate reuse and avoidable construction waste against actual condition and safety.
- Specify adaptable equipment interfaces and future replacement/transport limits.
- Select qualified cooling and heat-rejection systems for the real climate and hardware envelope.
- Consider local freshwater conditions alongside electricity-related and lifecycle impacts.
- Improve useful GPU work through evaluated software, utilization and operating practices.
- Measure operating outcomes and report verified results when facilities become operational.
From infrastructure to inference.
A conceptual operating architecture. Aguasto's compute and API services remain in development.
- Electrical serviceUtility authorization and protection
- Modular facilitySite works, heat rejection and approvals
- GPU rackPower, cooling and fabric integration
- Serving softwarePinned runtime and hardware compatibility
- Model deploymentLicense, weights, cache and evaluation
- Inference APIAuthentication, quotas and observability
- CustomerWorkload, latency and reliability requirements
A conceptual engineering chain for planned services. Each interface requires project-specific verification.
Enterprise request → Service routingChoose an eligible region using latency, policy, health and available capacity.
Region A
Independent facility
Local GPU racks & runtime
Model replica & local cache
Region B
Independent facility
Local GPU racks & runtime
Model replica & local cache
Region C
Independent facility
Local GPU racks & runtime
Model replica & local cache
Geographic request routing does not join GPUs into one NVLink fabric. Failover needs compatible replicas, spare capacity and a defined data-handling policy.
Electrical service supports the facility. The facility supports GPU racks, network paths and serving software. Model deployment and application interfaces depend on tested operations, security and capacity planning at every layer.
Read the full architectureCapital and operating trade-offs
Smaller phases can reduce the capital committed before the next development decision. They can also repeat equipment, networking and operational support that a larger campus shares. The appropriate design depends on measured workload needs and a project-specific cost model—not modularity alone.
About Aguasto