What it is
Headless 360 is Salesforce’s architectural transformation that, in its own words, "exposes every capability Salesforce has built over 25 years directly as an API, a Model Context Protocol (MCP) tool, or a CLI command." Its stated purpose is to make the browser interface optional, so AI agents can natively plug into Salesforce data, workflows and business logic. The release included over 60 new MCP tools, 30+ preconfigured coding skills, and the Headless Experience Layer.
Why it matters
It is the umbrella the rest of this vocabulary sits under. Multi-Framework is how a human-facing app gets built without the browser being the only way in; MCP tools are how an agent reaches the same capabilities. Both are expressions of one shift — the interface stops being the product surface and becomes one consumer among several.
Key components
- Every capability as an API, MCP tool or CLI command
- 60+ MCP tools
- 30+ preconfigured coding skills
- Headless Experience Layer
- Salesforce Multi-Framework
How it connects
The Headless Experience Layer separates business logic, data and permissions from the screen, so one definition renders across surfaces. Multi-Framework is the runtime that lets those surfaces be built in React.
Good to know
Headless 360 is the platform-level programme; Multi-Framework is the specific runtime a React app uses. The two get used interchangeably and are not the same thing.
Related terms
Agentforce 360
Salesforce's unified AI platform announced at Dreamforce 2025, bringing together Agentforce agents, Data 360, Agentforce Voice, and cloud-specific AI capabilities under one umbrella.
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.
MCP (Model Context Protocol)
Anthropic's open standard for connecting AI models to external data sources and tools. Think of it as a universal adapter for AI.
Salesforce Multi-Framework
A framework-agnostic Salesforce runtime that lets a standard React app run natively on the platform, with Salesforce authentication, security and governance applied automatically.
Headless 360 in practice
Articles from the Funnelists Team that put this term to work.
Salesforce Custom App Development vs Managed Packages: When to Build In-House and When to Package
Building a custom app directly in your Salesforce org and shipping it as a managed package lead to very different costs. This guide breaks down the trade-offs in maintenance, distribution, and long-term costs.
Salesforce Platform SDK Guide for Platform Architects Building React Apps
Platform architects facing React integration challenges on Salesforce can use the Platform SDK and Multi-Framework for native security and GraphQL access without custom OAuth layers.
Salesforce Micro Frontend Patterns for Platform Architects
Salesforce Platform Architects can now embed React, Angular, or Vue apps directly into Lightning pages. Learn the practical patterns, trade-offs, and when to choose this lighter approach over full LWC rewrites.
Why Build-vs-Buy IT Leaders Decouple the Salesforce Frontend for Custom Customer Portals
Build-vs-Buy IT leaders are decoupling the Salesforce frontend to own the customer experience while keeping Salesforce as the secure, automated backend. Here is the decision framework they actually use.
