Composable infrastructure is an approach that abstracts compute, storage and networking into shared pools so software can assemble what a workload needs through an API and return it when done. It lets IT provision resources on demand instead of building fixed stacks per application.
This page is for infrastructure and platform leaders. It covers how composable infrastructure works, how it differs from converged and hyperconverged systems, the key parts, and where to begin.
HPE explains that composable infrastructure works by abstracting enterprise resources and pooling them so they can be managed by an API. Compute, storage and networking are drawn from the pool when an application needs them, and returned to it when the software is no longer needed.
Resources are abstracted from their physical locations and presented as pools. A request through the API builds the infrastructure an application needs from those pools. Because the request is code, the same definition can be repeated, reviewed and versioned, which is why composable infrastructure is closely tied to infrastructure as code.
Standards help here. DMTF describes Redfish as simple and secure management for converged, hybrid IT built on common web services standards, and the DMTF site lists a Redfish composability white paper. SNIA describes Swordfish as an extension to Redfish that manages storage equipment and storage services.
| Question | Converged and hyperconverged | Composable |
|---|---|---|
| Resource model | Simplified, packaged infrastructure solutions | Pools of abstracted resources |
| Framing | Grouped by HPE with other simplified infrastructure solutions | By API request that builds from the pool |
| Workload mix | Per HPE, composable lets IT keep physical workloads alongside virtual and container ones | Physical, virtual and container together |
HPE groups converged and hyperconverged systems with other simplified infrastructure solutions and contrasts composable infrastructure with them on that last point.
Agents that provision or resize infrastructure through an API act on real systems and real cost. Each request needs limits, an owner and a record of why it was made. That turns infrastructure access into a governed decision. ElixirClaw, XenonStack's AI agents computing platform, is where teams build and run such agents.
To map one decision your agents make about infrastructure, and the data and policy it depends on, book a Context Workshop. See what happens in the workshop.
It is infrastructure whose compute, storage and networking are pooled so software can assemble what a workload needs through an API.
No. HPE contrasts the two: composable infrastructure lets IT keep physical workloads in the same environment as virtual and container workloads.
HPE explains that pooled resources are managed by an API, which builds infrastructure from the pool and returns it when the software is retired.
Because compositions are requests made through an API, they can be written as code, versioned and reviewed like any other code.
DMTF describes Redfish as management for converged, hybrid IT. SNIA describes Swordfish as an extension to Redfish for storage.