Headless Platform Development
Engineers bring their own front end.
React and Vue developers far outnumber LWC developers. API-first surfaces let a team build the experience it wants on the platform’s data and security.
Headless 360 launches at TDX as a core strategy
SFDC Developers: headless architecture, June 2026Situation
A customer’s front-end team wanted a branded checkout in React on Salesforce data. They knew React, GraphQL and their own design system, and hit a wall between the platform and the skills they had.
Task
Make the platform composable: API-first, any design system, security inherited rather than rebuilt.
Action
Design for the engineer who never opens Setup.
GraphQL as the front door
lightning/graphql with optional fields, so a query survives a field the user cannot see.
Security travels with the data
Custom interfaces inherit sharing and field-level security.
Hybrid by design
Lightning where it fits, headless where a team wants its own stack, both on the same actions.
Result
Headless 360 is a core platform strategy.
Business
Nearly 1T API calls across Core in a quarter; customers hire from the wider web talent pool and still ship on the platform.
Product
GraphQL as the front door, security inherited rather than rebuilt, Lightning and headless on the same actions.