Planned physical layer
Units plus shared systems
Potential scope includes multiple DensePod boundaries, shared heat rejection or power plant, network fabric, and explicit commissioning and maintenance boundaries.
DenseStack · planned system · software exploratory
Compose capacity without losing ownership.
DenseStack is the planned name for the layer that composes modular capacity: multiple units or a unit with shared site plant, network, and operating boundaries. A customer-owned operations layer is being explored, but no DenseStack hardware, production software, managed service, or SaaS offering is available today.
Two related layers
DenseStack is deliberately broader than an enclosure. The physical composition and the operations model must agree about ownership, evidence, and change authority.
Exploratory operations layer
Customer-owned, on the customer island
The working direction is telemetry, inventory, residency policy, access evidence, runbooks, and human-approved agent proposals—not a vendor superadmin or silent automation.
Defined posture
Ownership before convenience
The current thesis favors customer control of the operating environment and records. It does not assume DenseDC-hosted multi-tenant operations.
Still open
Architecture, product, and support
Topology, software interfaces, security model, operational staffing, service levels, support terms, pricing, and release criteria require research and explicit build authorization.
Questions a composition plan must answer
- Which systems are shared, which remain unit-local, and who owns each failure domain?
- How do power, cooling, network, and capacity growth change without redesigning the whole site?
- Which telemetry and audit records must stay with the customer, and who can approve a change?
- What can be proposed automatically, what requires a human decision, and what must never be automated?
Readiness note: these questions describe a product thesis, not completed DenseStack software or a delivered multi-unit system.