Rackspace Cloud Starts in Dallas—Two More U.S. Regions Are Still Pending

Rackspace Technology launched Rackspace Cloud in Dallas on August 25, 2026, and its official launch notice identifies the service as a fully managed, multitenant platform powered by Broadcom’s VMware Cloud Foundation 9.1. North Virginia and Chicago are due to follow, but neither location has a published opening date.

That leaves enterprises with one confirmed deployment area at launch: Dallas. The two other U.S. locations are planned expansions, not capacity that customers can treat as currently available for production, geographic redundancy or workload-location requirements.

Dallas is live; two regional openings remain pending

The current-versus-coming footprint is straightforward:

• Dallas: the initially available Rackspace Cloud location.
• North Virginia: a planned expansion without a public opening date.
• Chicago: a planned expansion without a public opening date.

SDxCentral’s independent coverage likewise places the initial VCF 9.1 service in Dallas and characterizes North Virginia and Chicago as expansion plans. Neither of the two launch accounts presents Rackspace Cloud as available across all three locations.

The distinction matters for architecture decisions. Dallas is the only stated location that can be incorporated into an immediate deployment plan; the pending areas cannot yet be assumed to support a secondary production site, regional failover or a particular data-residency design. Performance tiers, capacity levels and service configurations for the later locations also remain undisclosed.

Rackspace manages the foundation, not every customer workload

The service packages VMware capacity without requiring customers to purchase additional hardware or operate the underlying cloud systems. Its published features include pre-staged infrastructure, elastic consumption, automated lifecycle management, multiple performance tiers and continuously managed operations.

The multitenant model combines provider-operated infrastructure with isolation, security and governance controls for customer environments. Public material does not specify the physical allocation model or state which resources, if any, are dedicated to an individual tenant, so the multitenant label alone does not define every infrastructure boundary.

The clearest operational division sits below the workload layer: Rackspace operates the underlying systems and platform lifecycle, while customers choose what they deploy on their allocated capacity. The available material does not provide a complete responsibility matrix for guest operating systems, application management, identity configuration, backups, disaster recovery, tenant networking or application security.

Consequently, fully managed describes the infrastructure and VMware platform functions included in the service; it should not be read as a transfer of every workload, data-protection or compliance obligation to Rackspace. Public pricing, service-level terms and detailed support boundaries were also absent from the launch information.

VCF 9.1 brings VMs, Kubernetes and AI onto one foundation

Rackspace Cloud is intended to accommodate traditional virtual machines and Kubernetes workloads on the same managed platform, with production AI inference included among its stated workload categories. This gives organizations a route to consume VMware capacity without building and maintaining the VCF foundation themselves.

Broadcom’s VCF 9.1 overview describes a common operating model for virtual machines, containers, AI services and data services. The underlying release includes real-time operational observability, expanded Kubernetes scale, zero-touch fleet expansion, AI model and GPU metrics, memory tiering and infrastructure capabilities aimed at AI and database workloads.

That broader VCF inventory should not be mistaken for a Rackspace Cloud service catalog. Features may depend on provider packaging, hardware, licensing or configuration, and native object storage is identified as a technology preview in the VCF 9.1.x line. The Rackspace launch establishes support for the broad VM, Kubernetes and AI categories but does not enumerate every component exposed to Dallas tenants.

The same limitation applies to data services and AI tooling. VCF 9.1 supplies a technical foundation for those workloads, but no Dallas-specific catalog currently distinguishes generally available components from optional or restricted ones. What customers can order will ultimately depend on Rackspace’s service specification rather than the complete feature set of the underlying software.

A Dallas location does not settle sovereignty requirements

A named deployment area, tenant isolation and customer governance controls can help organizations manage workload location. Those properties do not by themselves demonstrate compliance with a particular sovereignty, residency or industry framework.

Such an assessment may also depend on backup and log locations, administrative access, encryption-key ownership, support procedures and transfers between sites. The available service information does not address all of those elements, so a Dallas deployment cannot be treated as automatically satisfying every regulatory or sovereign-cloud requirement.

The confirmed footprint therefore remains narrower than a three-region network: Dallas is operating first, while North Virginia and Chicago remain pending. The next material developments will be firm opening dates and region-specific specifications showing whether the later sites offer comparable capacity and can support the multi-region recovery or workload-location designs enterprises require.

Also read:

• Five Business Technology Bets for 2026—AI Agents Are Still the Weak Link
• OutSystems Adds AI Agents, but Platform Commitment Still Sets the Limit
• The Best Digital Marketing Strategy Starts With Measurement, Not More Channels