An infrastructure expansion arriving with Salesforce’s Winter ’27 release changes the deployment options available to two specific categories of customer that have historically faced real constraints on where their Salesforce environment could actually run. Salesforce plans to make Hyperforce available on Google Cloud, and MuleSoft available on Government Cloud Plus and Government Cloud Plus for Defense, later in the Winter ’27 release cycle.
Why Hyperforce on Google Cloud Matters Beyond the Infrastructure Detail
Hyperforce, Salesforce’s own cloud-native infrastructure architecture, has historically run across a defined set of public cloud providers, and its expansion onto an additional major hyperscaler is worth understanding for what it enables rather than treating purely as an infrastructure footnote. Organisations that have standardised their broader cloud strategy on Google Cloud specifically, whether for data residency reasons, existing negotiated commitments, or genuine technical integration with other Google Cloud services, gain a materially more attractive path to running Salesforce natively inside that same cloud environment, rather than needing to bridge a separate cloud relationship purely to accommodate Salesforce.
Why the MuleSoft Government Cloud Expansion Is the More Consequential Change
The MuleSoft availability expansion into Government Cloud Plus and specifically Government Cloud Plus for Defense addresses a genuine, previously binding constraint for organisations in the defence and broader government sector. Integration platform availability inside the specific, accredited government cloud environments these organisations are required to operate within has historically limited how fully an agency or defence contractor could build MuleSoft into its broader Salesforce architecture, and closing that specific gap opens integration patterns that were not previously available to this customer segment regardless of how much budget or organisational appetite existed for them.
What This Means for Organisations Not in Either Category
Even for organisations with no direct government or defence requirement, and no existing Google Cloud relationship specifically, this expansion is worth understanding as a signal of Salesforce’s broader infrastructure investment direction. A vendor actively expanding its core platform’s available deployment surface, rather than consolidating it, generally reflects genuine customer demand pulling that expansion forward, and it is reasonable to expect further hyperscaler and specialised cloud environment expansions to follow a similar pattern over subsequent release cycles.
The Commercial Question Worth Raising Directly
For any organisation genuinely positioned to benefit from either expansion, raising this directly with a Salesforce account team is worth doing proactively rather than waiting for the capability to appear unprompted in a renewal conversation. Confirming the specific rollout timeline for the relevant environment, and whether any commercial terms differ from the equivalent capability running on Salesforce’s existing supported infrastructure, gives an organisation genuine advance visibility into a capability that may materially change its own deployment architecture options.
It is also worth noting that Salesforce’s release notes describe this specifically as a planned rollout landing later in the Winter ’27 cycle rather than something available from day one of the release, which means organisations should confirm the actual availability date directly rather than assuming it lines up with the broader Winter ’27 launch itself.
A 2Data Perspective
Infrastructure expansions like this rarely make headlines the way a pricing change does, but they are exactly the kind of development worth tracking proactively if your organisation sits in either affected category. Waiting for Salesforce to raise it during a renewal conversation means giving up the advance planning time that makes any architecture change easier to execute well.
If you would rather have an independent set of eyes on this specific decision, get in touch with 2Data directly. ISG’s own research practice, which tracks software licensing and vendor management as a distinct specialism, has continued expanding its coverage of exactly this kind of enterprise software commercial complexity is exactly the kind of broader industry context we bring to a conversation like this one.
Conclusion
Salesforce’s planned expansion of Hyperforce onto Google Cloud, and MuleSoft into Government Cloud Plus and Government Cloud Plus for Defense, closes two genuine, previously binding infrastructure constraints for organisations standardised on Google Cloud or operating inside accredited government cloud environments specifically.
Organisations positioned to benefit from either expansion should raise the specific rollout timeline directly with their Salesforce account team now, rather than waiting for the capability to surface unprompted, since early visibility into a genuine architecture option is more useful than discovering it only once a broader renewal conversation is already underway.
