If you’ve been paying attention to the announcements coming out of Dreamforce this week, then you’ve likely heard a lot of new product and tool names. Within Salesforce’s AI product portfolio, it can be difficult to distinguish between the different offerings, especially with the new announcements of AIforce and Salesforce’s Enterprise AI Harness.
Is AIforce Headless 360 rebranded? Is the Enterprise AI Harness different from the Einstein Trust Layer? What’s the difference between AIforce, Headless 360, and the Enterprise AI Harness? Let’s take a look.
What Is AIforce?
AIforce is Salesforce’s flagship announcement from this year’s Dreamforce conference. It essentially acts as a dynamic, custom interface layer that plays a significant role in “replacing” the traditional UI.
According to a statement from the company, AIforce empowers “anyone to build their own UI”.
AIforce adds a layer to Salesforce’s Agentic Enterprise architecture, bringing the context of Data 360, the application and semantic intelligence of Customer 360, and Agentforce to any AI interface.
So, What Does It Actually Use?
As we understand it so far, AIforce appears to consolidate Claudeforce, Slackforce, Agentforce Coworker, and the Headless Toolkit.
Claudeforce, first announced last month during Salesforce’s Q2 ‘27 earnings call, allows users to access Salesforce’s intelligence in a hosted MCP server within Claude, with 37 prebuilt sales skills.
Slackforce combines several tools – Slack CRM, Slack Code, and most recently, Slack Surfaces. The goal of the tool is to bring the context of Salesforce into Slack. Slack Surfaces, in case you missed it, allows users to pull live context and data from Salesforce, Slack, and other tools to create interactive, live interfaces in Slack.
Agentforce Coworker, announced in May, is designed to be “your new AI teammate […] inside every search bar”. It connects to agents in all areas of business – across platforms – and brings you the answers you need, all in one place.
Lastly, the Headless Toolkit refers to the architecture that exposes every element of the Salesforce platform, providing builders and developers with MCPs, APIs, plug-ins, skills, and developer tools to build customized AI experiences on top of Salesforce’s architecture.
What Is Headless 360?
Headless 360, first revealed at this year’s TDX conference, was a layer within Salesforce that allows everything on the platform to become an API, MCP tool, or CLI command, all usable by agents. It included more than 60 new MCP tools and 30 preconfigured coding skills.
Is AIforce Rebranded Headless 360?
Salesforce has confirmed that Headless 360 has been rebranded to AIforce.
“As of September 4, 2026, Headless 360 has been rebranded to AIforce,” the Help page says. “During this transition, you may see references to Headless 360 in our application and documentation. While the name is new, the functionality and content remain unchanged.”
What Is the Enterprise AI Harness?
The Enterprise AI Harness, also known as the Trusted Enterprise AI Harness, is what Salesforce is calling a “trusted foundation around AI” that brings together what agents need to understand the business, reason and plan, and take action. It means that businesses don’t have to manage those capabilities separately for every agent or AI experience.
The Harness comes with six “trusted capabilities”: Context, Agency, Action, Governance, Security, and Models. Above it sits the AI Control Plane – a single dashboard for seeing every agent running across your org, what it’s allowed to do, and what it’s costing you.
Is the Einstein Trust Layer Still Relevant?
According to Salesforce, the Einstein Trust Layer is still the official name for Salesforce’s secure AI architecture. There is no documentation or announcement showing that it has been rebranded as the Trusted Enterprise AI Harness.
The Einstein Trust Layer exists as a specific, narrower set of security and privacy controls that sit between Salesforce’s generative AI features and the underlying LLM. The Enterprise AI Harness is a much bigger, composable architecture meant to govern the entire agentic enterprise, not just one prompt at a time.
Final Thoughts
Salesforce’s renaming habit and confusing marketing tactics have become part of the company’s reputation over the years, and understanding the difference between all of these tools and features can be difficult!
A lot of Salesforce’s renaming/rebranding decisions are oriented around creating hype for stakeholders and enterprise buyers, and during this Dreamforce period, this is particularly true. Hopefully this article makes it easier to distinguish between these tools, although if you check back next week or next month, we can’t promise it won’t change again.
