Headless 360 to AIForce to SIForce
If you have struggled to keep up with Salesforce product names this year, you are not alone. In roughly six months, the same core capability has gone by three different names. Here is what happened, what actually changed, and what deserves your attention.
The timeline in brief
- April 2026: Headless 360. Announced at TrailblazerDX, Headless 360 opened up the Salesforce platform through APIs, MCP tools and CLI commands. For the first time, teams and AI agents could work with Salesforce capabilities outside the browser-based CRM interface.
- September 2026: AIforce. At Dreamforce, Salesforce folded Headless 360 into a broader agentic integration layer under a new name: AIForce.
- October 2026: SIforce. Less than a month later, CEO Marc Benioff announced that: “AIforce is officially SIforce.” This is in alignment with the US government’s request to retire the term “AI” (artificial intelligence) and replace it with “SI” (super intelligence) .
What it means for your business
The evolution from Headless 360 to AIforce represented a significant shift, expanding initial API, MCP tool, and CLI command capabilities into a comprehensive agentic integration layer across platforms like Claudeforce, Slackforce, and Agentforce Coworker. In contrast, the recent transition from AIforce to SIforce introduces no functional changes, pricing adjustments, or licensing updates. However, because these rebrands occurred in rapid succession, organisations should expect naming drift, as Headless 360, AIforce, and SIforce may all appear across documentation, release notes, Setup menus, and contracts for some time.
What does deserve your attention
The name is the least interesting part of this story. The capability behind it, letting AI agents and external tools act on your Salesforce data through APIs and MCP, is a real shift in how your org is accessed. Whatever it is called this month, we recommend reviewing:
- Access and permissions. Know which AI tools and integrations can reach your org. Use dedicated integration users and permission sets scoped to only the objects and fields they need (least privilege).
- Monitoring and governance. Make sure agent and API activity is visible and auditable, for example with Event Monitoring and Transaction Security Policies, so you can see and control what automated actors do.
- Limits and performance. Headless and agent-driven traffic counts towards your API and platform limits. Plan capacity before usage grows.
- Internal alignment. Add a simple “also known as” note to your internal documentation, training and architecture diagrams so teams are not confused by three names for one product.
How Gen25 can help
Salesforce naming will keep moving; your architecture should not have to. Gen25 helps organisations focus on what matters: designing secure, scalable ways to bring AI agents and headless integrations into Salesforce, and making sure they are governed properly from day one.
Unsure what SIforce means for your security posture or long-term product roadmap? Get in touch with the Gen25 team - we will help you stay confident, secure, and clear on what is relevant for your business.
