At its first Horizon customer and partner event this week, Equinix Inc. argued that the architecture of enterprise artificial intelligence is being reshaped by a simple yet hard-to-answer question: Where should inference run?
For the past several years, much of the AI infrastructure conversation has centered on the supply and cost of accelerated computing. The focus has been on graphics processing units, AI factories, training clusters and the unprecedented capital buildout required to support them. Those remain crucial. But as enterprise AI shifts from experiments to real applications, the more immediate operational challenge is distribution.
Data resides across multiple clouds and enterprise systems. Users, sensors and business processes are dispersed across regions. Models may be proprietary, open source, fine-tuned or delivered as services. AI agents will call other agents, tools and application programming interfaces across organizational and infrastructure boundaries. In this environment, compute is only one component of a system that must be connected, governed and continuously optimized.
That is the premise behind the two announcements Equinix made at Horizon: Equinix Fabric One, an intent-driven, managed any-to-any connectivity service, and Equinix Inference Exchange, a distributed inference offering built with Nvidia Corp. and Together AI Inc.
Combined, they represent an effort to extend Equinix’s traditional role as a neutral interconnection provider into the AI era. The company aims to make its global footprint, dense ecosystem and Fabric platform the place where enterprises not only collocate and interconnect infrastructure but also assemble and operate distributed AI environments.
From connections to outcomes
Fabric One is the more foundational announcement. Equinix describes it as a managed service for connecting distributed enterprise, cloud and AI environments. The key change is the operating model: Rather than requiring customers to design, provision and manage a collection of discrete network services, Fabric One is meant to let them state the business or application outcome they need and have the platform compose the underlying connectivity.
In practical terms, an enterprise might specify that it needs a secure, resilient, low-latency connection among a data source in one metro, an inference provider in another, a cloud-hosted application and a branch, factory or other edge location. Fabric One is intended to orchestrate routing, cloud connectivity, encryption, redundancy and failover as a single managed service.
That is a significant shift from the project-oriented networking model still familiar to many large enterprises. Building a distributed AI workflow today can require separate teams and tools for cloud interconnects, carrier services, security controls, network routing, colocation operations, GPU capacity and application integration. Each additional model provider, cloud region or inference endpoint can add another engineering and governance task.
In his opening remarks, Chris Audie, Equinix’s chief product officer, set the stage for the event when he stated, “For decades, enterprise networks have been built one connection at a time for each partner and provider they depend on. That approach doesn’t scale in a world of distributed AI that demands dynamic, flexible and real-time connectivity.”
Fabric One will use open connectivity specifications developed in collaboration with Amazon Web Services Inc. and Google Cloud, its lead integration partners. The service is expected to enter beta later this year, with general availability planned for 2027, initially in North America.
Historically, Equinix’s value proposition has focused on easier provisioning, but this release goes beyond that. It aims to turn the network into an adaptive control plane for AI-era infrastructure. Customers can submit requests via a portal, APIs, automation workflows, agents or natural-language prompts. The platform then continuously validates the network and manages policies, encryption, resilience and failover.
That model is particularly relevant for agentic AI. A future enterprise application will not necessarily make a fixed call to a single large language model running in a single cloud. It may dynamically coordinate several models and services, retrieve information from multiple data domains, apply policy checks and invoke specialized agents in different locations. In that scenario, the network cannot remain an opaque, static utility. It must become programmable, policy-aware and responsive to the application’s needs.
Why inference changes the equation
Equinix Inference Exchange addresses the complementary problem: how enterprises can bring production inference capacity closer to their data, applications and users without building the full stack themselves.
The offering combines Nvidia Enterprise Reference Architectures and AI infrastructure, Together.ai’s platform, which supports more than 200 open-source models, and Equinix’s global data-center and interconnection footprint. Equinix says the service will support multitenant deployments for shared efficiency and dedicated single-tenant environments for workloads requiring isolated capacity. Availability is planned for the first quarter of 2027.
This announcement matters for inference economics and user experience. Training can be concentrated in massive, centralized clusters because it is a long-running, batch-oriented process. Inference is different. It sits on the live path of an application, customer interaction, operational system or agentic workflow. It can be sensitive to latency, data movement costs, sovereignty requirements and the cumulative cost of every token generated.
During her keynote, CEO Adaire Fox-Martin (pictured, left) made that point by identifying four pressures converging on enterprise information technology: fragmented compute, the rise of machine-to-machine traffic, the challenge of achieving predictable AI returns, and increasingly stringent data sovereignty requirements. “Where compute runs is becoming as important as the compute itself,” she said.
An enterprise does not necessarily need every inference request to reach the largest possible centralized model. In many cases, it needs a model that is sufficiently capable, properly governed, affordable and physically close to the interaction or data source. A manufacturing application may require response times near the factory floor. A customer-facing service may require inference near a metropolitan population center. A regulated financial, healthcare or public-sector organization may need to keep data and inference processing within a specific jurisdiction.
Nvidia CEO Jensen Huang (right) took a break from the G20 summit to pop in on video. He emphasized the same architectural shift during his Horizon discussion with Fox-Martin. “The world of AI is going to be uncentralized, fundamentally uncentralized,” he said, describing AI applications that will orchestrate agents that access data and services across multiple clouds and locations.
Huang also explained the importance of proximity, where compute needs to be close to the “action” — sensors, customers, factories, cell towers, airports or other locations with high data volumes and where response time matters — while prior knowledge and long-term memory can reside farther away. Equinix’s distributed footprint and interconnection fabric are designed to enable enterprises to support both realities simultaneously.
A simpler path to production
The most compelling aspect of the Equinix strategy is not that it eliminates AI complexity. It does not, and no vendor can. Instead, it packages some of the difficult infrastructure decisions into a more consumable, neutral operating model.
Inference Exchange is designed to provide pre-staged, pre-connected Nvidia-based AI infrastructure through Equinix, connected to clouds, networks and AI providers via Equinix Fabric. Together.ai adds model flexibility, including access to a broad catalog of open-source models. That combination matters for enterprises that want to avoid an all-or-nothing choice between proprietary frontier models and do-it-yourself open-model operations.
Huang argued that enterprises will use both. Closed models will remain important for frontier capabilities, he said, while open models increasingly let organizations fine-tune systems, incorporate domain-specific knowledge, meet regulatory or sovereignty requirements, and retain control over strategically important AI capabilities.
For customers, this could reduce the time and coordination burden of moving from an AI pilot to a production distributed deployment. Instead of separately sourcing GPU infrastructure, establishing colocation, arranging cloud and network connectivity, integrating inference services and building operational guardrails, they can use a more integrated platform.
Fox-Martin said Equinix designed Inference Exchange to be “production-ready, fully connected, and built to scale from day one.” She added that the company’s goal is to provide Nvidia compute “pre-staged and pre-connected within Equinix’s ecosystem,” with Together AI offering model choice and avoiding lock-in at the model layer.
That is an attractive proposition, particularly for enterprises whose AI strategy will be heterogeneous by necessity. A bank, manufacturer, retailer or global SaaS provider may use proprietary models for specific tasks, open models for specialized workloads, multiple clouds for different applications, and localized inference for latency or compliance reasons. The strategic risk is not merely vendor lock-in; it is the operational friction of stitching those choices together.
The bigger bet
Equinix’s differentiator is its neutrality and ecosystem density. The company operates more than 280 data centers across 77 metros, provides 230 cloud on-ramps and interconnects more than 10,500 businesses. It also reports that eight of the top 10 AI model providers and nine of the top 10 AI clouds have active deployments on its platform.
Those figures alone do not guarantee that Fabric One or Inference Exchange will become essential enterprise services. The proof will come from execution: the depth of cloud and AI-provider integrations, the maturity of automated orchestration, price transparency, service-level commitments, geographic availability and the ability to make intent-driven networking genuinely simpler without masking critical controls.
But Horizon signaled a notable evolution in Equinix’s story. The company is no longer positioning connectivity as a supporting service beneath cloud and AI. Instead, it is positioning connectivity as the enabler of a distributed, multicloud, multimodel AI strategy.
For enterprises entering the inference era, that is the right problem to solve. The winning AI architecture will not be defined solely by who owns the most compute. It will be defined by who can place the right compute, model and data path in the right location — and adjust that decision as performance, cost, sovereignty and business requirements evolve.
Zeus Kerravala is a principal analyst at ZK Research, a division of Kerravala Consulting. He wrote this article for SiliconANGLE.