| On-demand self-service | Every resource has an API: accounts, identity, networks, databases. Vending lines such as Account Factory already exist. | APIs exist for compute (vSphere, OpenStack, KubeVirt), but network, firewall, IP addresses, DNS and storage sit behind tickets. The factory needs a source of truth and an API façade over every one of them. | NetBox or Nautobot, Ansible, OpenTofu providers, Crossplane providers, Cluster API providers for vSphere, OpenStack and Metal3 |
| Broad network access | A global backbone, managed load balancers, DNS and certificates on request. | VLANs per site, firewalls with change windows, load balancers as appliances. The network has to become a policy the factory enforces instead of a ticket it waits for. | MetalLB, Cilium or Calico network policy, cert-manager, external-dns |
| Resource pooling | Multi-tenant by construction. Isolation is an account boundary. | Dedicated hardware per team, licenses per socket, snowflake clusters. The factory has to create the pool: a virtualization layer, and tenancy inside clusters. | KubeVirt, OpenStack, vCluster, Capsule, Kamaji, namespaces with quotas |
| Rapid elasticity | Capacity appears in seconds and leaves the bill when released. | Capacity arrives on a truck. Lead time has a floor set by procurement, so the factory keeps inventory: warm pools, buffer stock, reservations and forecasts. | Metal3, Tinkerbell, Ironic, MAAS, Cluster API, SandboxWarmPool |
| Measured service | A billing API, tags, and cost allocation down to the resource. | No meter. Cost is a depreciation line in a spreadsheet. The factory has to build metering and showback before cost attribution can be one of its outputs. | OpenCost with on-premises pricing, Kepler, Prometheus |