Baseline design targets
This page defines the baseline technical targets we design toward. These are design targets and operational standards; they are not a claim of currently deployed capacity.
Designed-for vs planned
Section titled “Designed-for vs planned”- Designed-for: what the facility and operating model is engineered to support.
- Planned: phased delivery sequencing based on permitting, procurement lead times, and customer demand.
Baseline targets (high level)
Section titled “Baseline targets (high level)”- Reliability target: Tier III-aligned approach with N+1 redundancy.
- Inference posture: latency-aware region selection and predictable network performance.
- Cooling posture: liquid-ready paths for high density, staged upgrades.
- Security posture: physical + logical controls designed in from day one.
- Operations posture: commissioning-first delivery, runbooks and telemetry as part of “done.”
Power (electrical)
Section titled “Power (electrical)”- Topology: designed for maintainability and staged commissioning.
- Redundancy: N+1 targets across critical power components.
- Commissioning: acceptance tests defined and executed before expansion phases.
Cooling (thermal)
Section titled “Cooling (thermal)”- Liquid-ready design: support for high-density upgrades without redesign.
- Resilience: redundant loops and control systems aligned to uptime targets.
- Efficiency: predictable OPEX focus, measured via telemetry.
Networking (latency and throughput)
Section titled “Networking (latency and throughput)”- Fabric: non-blocking design principles for east-west traffic.
- Connectivity: carrier diversity and regional routing strategy.
- Inference priority: avoid surprise latency by designing for network paths, not just location.
Security (physical + logical)
Section titled “Security (physical + logical)”- Physical security: layered access control, monitoring, and controlled zones.
- Tenant separation: environment separation as a first-class requirement.
- Auditability: operational logging and access logging designed in.
Operations (how “done” is defined)
Section titled “Operations (how “done” is defined)”- Commissioning-first: we validate before scaling.
- Telemetry: monitoring is part of the deliverable, not an add-on.
- Change control: maintenance windows, rollback posture, documented procedures.
Next: facility architecture reference at /reference/configuration/.