Salesforce and Google Cloud Unify Hyperforce: What the Dreamforce 2026 ISV Program Overhaul Means for Channel Partners
At Dreamforce 2026 in San Francisco on September 15, Salesforce delivered two announcements that together represent the most significant restructuring of its partner ecosystem in nearly two decades. The first: Salesforce will migrate its Hyperforce infrastructure to run on Google Cloud, with North America customers moving in Q4 2026 and general availability in the region targeted for November. The second: Agentforce 360 — Salesforce’s full agentic AI layer — is now open to ISV partners, enabling them to build and distribute agentic applications through AppExchange on a shared infrastructure foundation. For channel leaders, the implications of both announcements compound each other in ways that demand immediate strategic review.
Taken together, these moves signal a deliberate repositioning of Salesforce from a platform with a partner programme to a shared infrastructure play where the platform itself becomes the distribution vehicle. Channel partners — ISVs, SIs, and managed service providers alike — will need to reassess their go-to-market assumptions accordingly.
Hyperforce Moves to Google Cloud Infrastructure
What Changes for Existing Salesforce Customers in North America
The Salesforce announcement describes a phased migration beginning Q4 2026 for US customers, with GA across North America in November. For existing enterprise Salesforce deployments, the immediate operational implication is largely transparent: Hyperforce was already designed for portability across hyperscalers, so customers running on the current infrastructure should not expect service disruptions. The more significant shift is architectural. Salesforce AI agents and Google Gemini Enterprise will be able to reason on shared data without custom integrations between the two platforms — a capability that eliminates an entire class of middleware and integration work that SIs and ISVs have historically monetised.
Channel partners with services revenue built around Salesforce-to-GCP integration projects should take note: the value proposition of that work narrows substantially once the two platforms share a common data substrate.
Why Google Cloud — and What It Signals About Hyperscaler Alliances
The Salesforce-Google alignment is strategically deliberate rather than opportunistic. Google Cloud brings Gemini Enterprise into the agent reasoning layer; Salesforce brings 160,000 companies and a distribution network that Google Cloud alone cannot match. For ISVs and SIs building on Salesforce, this creates a new co-sell dimension: Salesforce Commerce Cloud products will be purchasable directly through Google Search and AI Mode from fall 2026, opening a consumer-adjacent distribution channel that has no precedent in the CRM ecosystem. Partners who understand how to position for co-selling with cloud vendors will be better positioned to capture this opportunity before it becomes standard practice.
Agentforce 360 Is Now Open to ISV Partners
Salesforce described this as “the most significant expansion of the Salesforce Platform for ISV partners in 18 years.” The claim is not marketing hyperbole. Until now, ISVs building on Salesforce could extend the platform but could not embed the full agentic AI layer as a foundation for their own products. Agentforce 360 changes that: ISVs can now build complete agentic applications on AppExchange, with Agentforce 360 as the underlying runtime rather than a feature they need to replicate or integrate around.
The Agentforce 360 ISV programme gives partners access to the same agentic infrastructure Salesforce uses internally, which substantially lowers the engineering cost of building AI-native AppExchange applications. ISVs no longer need to maintain separate agent frameworks or negotiate data access agreements with Salesforce — the shared data substrate handles that at the platform level.
The New Salesforce Partner Marketplace App
Alongside the Agentforce 360 opening, Salesforce launched a new Partner Marketplace app that automates core go-to-market mechanics for ISVs: order-to-cash, private offers, and real-time App Analytics. The distribution numbers attached to this marketplace are not incidental — 160,000 companies, 5,000 ISVs, 7,000 SIs, and 20 million Trailblazer community members. As Channel Insider noted in its Dreamforce coverage, this positions AppExchange as a serious commercial marketplace rather than a catalogue, closing the operational gap with AWS Marketplace and Azure Marketplace that has historically made Salesforce distribution feel less automated than hyperscaler alternatives.
Order-to-Cash Automation and App Analytics Access
The operational shift here is significant for ISVs operating at any meaningful scale. Order-to-cash automation eliminates the manual provisioning and billing reconciliation that has made AppExchange distribution operationally expensive relative to hyperscaler marketplaces. Private offers enable custom pricing for enterprise deals without breaking the standard marketplace transaction flow. Real-time App Analytics give ISVs visibility into how their products are being used across customer tenants — data that has historically been difficult to access at the AppExchange layer. For ISVs building ISV cloud marketplace listing strategy across multiple platforms, the AppExchange is now a first-tier option rather than a secondary channel.
Commerce Cloud Meets Google Search: The Co-Sell Dimension
One element of the announcements that has received less attention than the infrastructure and partner programme changes is the Commerce Cloud distribution shift. Salesforce Commerce Cloud products will be purchasable directly in Google Search and Google AI Mode from fall 2026. For channel partners, this creates a new category of co-sell motion: ISVs whose products extend Commerce Cloud now have a path to consumer-visible distribution that did not previously exist in the B2B CRM space. The practical implications for GTM planning depend heavily on partner product category, but any ISV whose AppExchange product touches Commerce Cloud functionality should be modelling the co-sell economics now rather than after GA.
What ISVs Need to Do Now
Technical Requirements to Get Marketplace-Ready on the New Stack
The Agentforce 360 ISV programme opens a significant engineering opportunity, but getting marketplace-ready on the new stack requires preparation that goes beyond updating AppExchange listings. ISVs need to evaluate how their current data access architecture interacts with the shared Hyperforce-on-GCP substrate, assess whether their existing agent logic can be refactored to run on Agentforce 360’s runtime, and validate that their metered billing implementation is compatible with the Partner Marketplace App’s order-to-cash automation. ISVs that need to rebuild core platform integrations or develop agentic capabilities from scratch may benefit from engaging a custom development partner who can accelerate the technical readiness work while internal teams focus on product strategy. The integration with Partner Marketplace App’s entitlement and provisioning layer also deserves scrutiny — the automation only delivers its efficiency gains if the ISV’s fulfilment logic is compatible with AppExchange auto-provisioning requirements.
The Economics of Building on Agentforce 360
The shift from building agentic capabilities independently to building on Agentforce 360 as a platform changes the ISV cost structure in ways that are not yet fully visible. Platform licensing, revenue share, and entitlement costs will determine whether the distribution advantages of AppExchange justify the economic terms. ISVs should model these economics carefully before committing their product roadmap to Agentforce 360 as the primary runtime, particularly for use cases where the agent framework could alternatively be built and operated independently. The cloud hyperscaler marketplace playbook for AWS and Azure Marketplace is a useful reference point: the pattern of platform dependency versus distribution advantage is structurally similar, and the lessons about margin compression at scale apply directly.
Analyst Perspective: Why This Is the Most Significant ISV Program Change in 18 Years
Salesforce’s own characterisation of the Agentforce 360 opening as the most significant ISV programme change in 18 years invites scrutiny, but the structural logic holds. The last time the Salesforce platform shifted this fundamentally for ISVs was the introduction of the Force.com platform itself, which moved the competitive dynamic from “build on Salesforce” to “build with Salesforce.” Agentforce 360’s opening to ISVs makes a comparable shift: from ISVs extending Salesforce functionality to ISVs building agentic applications where Salesforce infrastructure is the foundation rather than the surface. The Hyperforce-on-GCP announcement amplifies this: shared infrastructure means shared data gravity, and data gravity at Google Cloud scale changes the competitive calculus for every ISV that currently maintains separate data pipelines between Salesforce and GCP environments. Channel leaders should not wait for November GA to begin planning — the architectural decisions that will determine marketplace success in 2027 need to be made now.