What it is
Salesforce Multi-Framework is a framework-agnostic runtime for building native Salesforce applications in standard frontend frameworks. It reached general availability on 16 July 2026, starting with React, and Salesforce has said Angular support follows. Apps run inside the org rather than beside it, so authentication, security and governance are applied by the platform and there is no token management to write.
Why it matters
Before this, building on Salesforce meant building the way Salesforce required — a proprietary component model your team had to learn and could not hire for. Multi-Framework makes the frontend a normal React codebase while the data model, sharing rules and business logic stay exactly where they are. That turns "decouple the frontend" from a workaround into a supported architecture.
Key components
- Framework-agnostic runtime (React now, Angular announced)
- UI Bundle deployment unit
- Platform SDK for data access
- Salesforce auth, security and governance applied automatically
- Hyperforce org on Summer ’26 or later
How it connects
A Multi-Framework app is packaged as a UI Bundle and reaches users either as an internal app for employees or an external app on an Experience site. It reads and writes through the platform SDK over GraphQL and can invoke Apex where the logic already lives.
Good to know
It is an additional runtime, not a replacement — Salesforce has not announced any end to Lightning Web Components, and existing components keep working alongside it.
Related terms
UI Bundle
The Salesforce metadata type that packages a Multi-Framework app for deployment, declaring in .uibundle-meta.xml which surface it targets.
Salesforce Platform SDK
The client library (@salesforce/platform-sdk) a Multi-Framework React app uses to query and mutate Salesforce records over GraphQL, with no authentication or token management.
Micro-Frontends
An architecture that composes several independently built and deployed frontend bundles instead of one monolithic app — each owning a domain and shipping on its own cadence.
Hyperforce
Salesforce’s public-cloud infrastructure architecture, and the prerequisite for running Multi-Framework React apps.
Headless Architecture
A software design pattern that separates backend logic and data from the presentation layer, letting any frontend — UI, API, agent, or CLI — consume the same business capabilities.
Salesforce Multi-Framework in practice
Articles from the Funnelists Team that put this term to work.
Decouple Salesforce Frontend: Replace Experience Cloud with Your Own React Stack
Solution architects and Salesforce admins can now run full React apps natively on the platform. Learn how Multi-Framework removes Experience Cloud constraints while keeping data, security, and governance inside Salesforce.
Build Scalable Customer-Facing Apps on Salesforce Beyond Experience Cloud Limits
Page view caps, concurrent user limits, and API quotas are what a portal hits first. Headless architectures, React via Multi-Framework, and Agentforce deliver custom branded experiences while keeping Salesforce governance intact.