Summary

  • AXG and Digital Realty have announced a hosted private-infrastructure offer for systems integrators and managed service providers across 31 markets.
  • The public responsibility split is clear at a high level: the channel partner owns the customer and service layer, AXG finances and manages the technology assets, and Digital Realty supplies the facility and connectivity surface.
  • A monthly charge and no upfront infrastructure capex do not make the model fully elastic: AXG says it owns the assets, commonly works on multi-year terms and is not designed for workloads that scale rapidly up and down.
  • The 31-market figure is a route-to-market envelope, not evidence of named customers, installed capacity, accepted service, utilisation or realised savings.

One invoice can make four operating systems look like one product. The integrator keeps the customer account and application outcome. AXG buys, finances and manages the servers, software and support. Digital Realty supplies the building, power, cooling and interconnection. The customer decides which workload moves and whether the delivered service passes acceptance. That is the useful way to read the partnership announced by AXG and Digital Realty on 17 September—not as a single cloud substitute, but as a chain of control with a simplified commercial front.

The offer is aimed at global systems integrators and managed service providers. According to the announcement, they can take hosted private infrastructure to customers in 31 markets spanning North America, EMEA, Asia-Pacific and Latin America. The integrator retains solution design, managed services, orchestration and the application layer. AXG handles technology procurement, financing, deployment and lifecycle management. Digital Realty contributes data-centre space, power, cooling, connectivity and ServiceFabric. The pitch is one harmonised agreement, a predictable monthly recurring charge and no upfront infrastructure capital expenditure.

That architecture can solve a real coordination problem. A channel partner wanting to sell private AI, edge capacity or a cloud-repatriation project normally has to align hardware supply, software licences, financing, local contracting, deployment, support, a colocation site and network access. AXG says it can contract and invoice across more than 50 countries, while Digital Realty offers a global estate and interconnection platform. Combining the two could shorten procurement and make a repeatable offer easier to take into several jurisdictions.

But the number 31 describes where the channel may sell, not what has been ordered. The announcement names no end customer, contract value, rack count, megawatts, server inventory, activation date, accepted capacity or billable run-rate. It supplies no market-by-market schedule showing which facility, carrier, cloud on-ramp, ServiceFabric endpoint, sovereign-control option or support regime is available for a particular order. A presence in a market is therefore a necessary option, not a deployed customer system.

Monthly pricing does not remove the asset clock

The commercial form deserves close attention because it sits between leasing, managed infrastructure and private cloud. AXG's own offering material says AXG owns the assets throughout the contract. Billing is generally triggered by installation or activation, terms are commonly three to five years or longer, and private-cloud examples often assume four to six years. Termination for cause or convenience is shaped per engagement; end-of-term choices can include extension, refresh or month-to-month treatment. AXG also says the model is not intended for workloads needing fully consumption-based, rapid scaling up and down.

In other words, monthly billing changes the cash-flow shape and the owner of record. It does not abolish the economic life of the equipment. Someone still bears the cost when demand is lower than forecast, a GPU generation ages faster than expected, software licensing changes, a facility migration is delayed or the customer exits early. AXG may hold title to the machines, but the contract determines how much of utilisation and residual-value risk is transferred, priced or returned to the customer and integrator.

This is why “no upfront capex” is not the same as “no commitment”. A buyer needs the base charge, minimum term, activation trigger, refresh rights, early-termination formula, removal cost and data-portability obligations. Without those terms, comparing the monthly fee with a cloud bill or an owned system is incomplete.

Private economics begin with the workload

The partnership identifies private AI, edge deployments, neo-cloud capacity and cloud repatriation as use cases. The economic case can be strong where demand is stable and utilisation is high. Uptime Institute's examination of 37signals makes precisely that bounded point: the company's high utilisation supported cheaper owned or colocated infrastructure for its workload, while unexpected storage and other cloud costs helped motivate the move. It was a specific workload and operating model, not a universal proof that private infrastructure wins.

Microsoft Research provides the counterweight. Public cloud creates value through elasticity, pay-as-you-go access and converting capital expense into operating expense, although its measurements also found many customers did not dynamically resize assigned resources. S&P Global/451 Research frames repatriation as workload mobility within a hybrid estate rather than a mass exit from cloud. Its different survey denominators also show how easily the trend can be overstated.

The relevant calculation is therefore not public versus private in the abstract. It is the hourly and lifetime demand curve of a particular workload, including idle headroom, migration labour, interconnection, operations staff, licences, compliance controls, failure recovery, refresh cycles and exit. Dedicated hardware can outperform when utilisation is durable. Elastic public capacity remains valuable when demand is uncertain, bursty or short-lived.

A platform capability is not an accepted order

Digital Realty describes PlatformDIGITAL as a place to deploy, connect and control critical infrastructure, with ServiceFabric, campus and metro connectivity, cross-connects, internet exchange and IP bandwidth among the connectivity surface. Those capabilities can materially reduce the distance between private equipment, carriers and cloud services. They do not establish that every named product, route, counterparty and service level is available at every relevant facility.

For a real deployment, the evidence chain starts with a service schedule: selected facility, available power, permitted rack density, ordered hardware, software entitlement, carrier endpoints, cross-connects, routing design, residency controls and support coverage. It continues through delivery, installation, commissioning and customer acceptance. Only then does “available in a market” become operating infrastructure.

The announcement is therefore meaningful, but its meaning is narrower than its footprint. AXG and Digital Realty have assembled a plausible distribution and delivery architecture for channel-led private infrastructure. They have not published a deployment ledger. The next unit of proof is not a larger country count. It is a named or auditable customer order that shows who was responsible, when the system was accepted, how it was used and what happened when requirements changed.

Sources