Headless Salesforce, Built in React
Build the frontend in React. Keep the data, security model, and business logic on Salesforce.
Scope My Headless BuildOverview
Salesforce stopped requiring you to build the frontend its way.
Salesforce Multi-Framework reached general availability on 16 July 2026. It is a framework-agnostic runtime that lets a standard React application run natively on the platform — with Salesforce authentication, security, and governance applied automatically, and no token management to write.
That makes headless Salesforce a supported architecture rather than a workaround. The interface is a normal React codebase your team can hire for. The data model, sharing rules, and business logic stay exactly where they are.
We design and build those applications. The frontend is React on the platform SDK; the delivery framework underneath is App Kit, which is how we build rather than something you license. What you receive is a running application in your own org.
What is headless Salesforce?
Headless Salesforce is an architecture where the user interface is built and deployed independently of Salesforce's own rendering layer, while Salesforce continues to own the data, security model, and business logic. The frontend becomes a standard web application talking to the platform through governed APIs.
What is Salesforce Multi-Framework and when did it ship?
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. It requires a Hyperforce org on the Summer ’26 release or later.
Can I build a Salesforce app in React?
Yes. Since Multi-Framework reached GA in July 2026, React is a supported way to build applications that run natively on the Salesforce platform. You write standard React and deploy it as a UI bundle inside your org, with Salesforce authentication, security, and governance applied automatically.
What is the Salesforce platform SDK and what surfaces does it route to?
The platform SDK (@salesforce/platform-sdk) is the client library a React app uses to query and mutate records over GraphQL, invoke Apex, and read user context — with no authentication or token management required. Bundles route to employee-facing apps on the salesforce.app domain, to customer-facing Experience targets, and into the App Launcher.
How do I run a micro-frontend architecture on Salesforce?
A micro-frontend architecture on Salesforce composes several independently built and deployed UI bundles rather than one monolithic application. Each bundle owns a domain, ships on its own release cadence, and targets the surface it belongs on — an internal app, an Experience site — while sharing one org’s data and permission model.
How do I get a headless Salesforce app built?
Book an intro call. We scope the surfaces, data contracts, and permission boundaries first, then build the React application and deploy it into your org. App Kit is the delivery framework we build on, so the engagement produces your application — not a licence for ours.
What's Included
Surface & Architecture Design
We map which surfaces the application needs — internal app, Experience site, App Launcher entry — and decide where one bundle ends and the next begins before any code is written.
React Application Build
A standard React codebase, built to run natively on Multi-Framework. No proprietary component model, and a stack your team can hire for and maintain after handover.
Platform SDK Data Layer
Records queried and mutated over GraphQL through @salesforce/platform-sdk, with Apex invoked where the logic already lives. No bespoke auth layer and no token management.
Security Model Alignment
The application inherits your existing sharing rules, profiles, and permission sets. A headless frontend changes how the interface is delivered, not who is allowed to see what.
Why Funnelists for Headless Salesforce?
Our Process
Surface Mapping
We establish which users are served on which surfaces, and what each one needs to read and write. This is where a micro-frontend split is decided, or ruled out.
Data Contract
We define the GraphQL queries, mutations, and Apex entry points the application depends on, and confirm them against your sharing model before the build starts.
Build
The React application is built against your org, deployed as UI bundles, and reviewed on real data on the surfaces it will actually run on.
Deploy & Handover
We deploy into your org and hand over the codebase with the architecture documented, so your team can extend it without us.
Frequently Asked Questions
Do I need to migrate my existing Lightning Web Components?
No. Multi-Framework runs alongside what you already have, so existing components keep working and nothing has to be rewritten to adopt React. Most engagements start with one new surface rather than a migration, which keeps the first release small enough to judge on its merits.
What are the prerequisites for headless Salesforce?
A Hyperforce org on the Summer ’26 release or later, with React development enabled in Setup. Multi-Framework is supported in production orgs, sandboxes, scratch orgs, and Developer Edition orgs, so the work can be proven in a sandbox before anything reaches production.
Does a headless frontend weaken my Salesforce security model?
No, and this is the main reason to build headless on the platform rather than outside it. The application runs inside your org and inherits your sharing rules, profiles, and permission sets. Data access is governed by Salesforce, not reimplemented in an external application you now have to secure yourself.
Can a headless Salesforce app serve customers as well as employees?
Yes. Employee-facing applications run on the salesforce.app domain, and customer-facing applications deploy to an Experience target. The same React codebase and data layer can serve both, which is usually what makes the architecture worth adopting rather than building two separate frontends.
Is Lightning Web Components going away?
Salesforce has not announced any end to Lightning Web Components, and Multi-Framework is presented as an additional runtime rather than a replacement. What changed is that React became a supported option. Funnelists builds in React; if your requirement is LWC work, we are not the right fit.
What does a headless Salesforce build cost?
It depends on how many surfaces the application spans and how much of the business logic already exists in your org. We scope it on an intro call and quote against a defined surface list rather than quoting a range that would mean nothing before that conversation.
App Kit is the connector-driven framework we build these applications on. If you want the technical depth on the foundation itself — how connectors, surfaces, and backends fit together — that is where it lives.
App Kit — the delivery framework →