omnia vs agentforce

Agentforce is built for agents inside Salesforce, and Omnia for agents whose tools are everywhere else.

Omnia carries the user’s identity to every tool, wherever it lives, and checks each call. Agentforce runs the agent in the user’s context inside Salesforce, and once it calls your billing system or your own services, that gets harder.

A customer asks the agent to move their payment date. Billing is your own service.
on omnia

The customer’s identity travels with the request through the agent into the billing call. A CEL rule checks that the account in the arguments is theirs, and the audit log records whose authority the call ran on. docs

on agentforce

Salesforce’s architecture guidance for calling external APIs notes that user identity is lost by default, and propagating it is a MuleSoft gateway pattern. their docs

The user’s identity reaches every tool

OIDC or your gateway authenticates the caller, and the identity travels through the agent to every tool, MCP server and remote agent. Policy decides on it, per call. docs enterprise

Agentforce: Authenticated sessions run in the user’s context inside Salesforce; for external APIs, identity is lost by default. source

Stepped rollout and automatic rollback

Traffic moves to the new version in steps, and a customer mid-conversation stays on the one they started with. Promotion waits on the metrics, and a drop rolls it back. docs enterprise

Agentforce: Traffic splitting between versions is an A/B Testing API pilot; you promote the winner. Automatic rollback isn’t documented. source

Telemetry that streams to you

Spans stream live over OpenTelemetry to the collector you already run. Prometheus metrics come alongside, and the span inventory is documented. docs

Agentforce: A beta Session Trace OTel API you call per session, for sessions from the last 72 hours, with Data Cloud required. source

At a glance

Topic Omnia Agentforce, per its docs
Simulated users, multi-turn yes Against real tools, adversarial included. docs documented Testing Center personas. source
Voice simulation yes Barge-in, overlap, dead air. docs documented Supported in Testing Center. source
Adversarial testing yes Callers probing for policy bypass. docs not documented Not documented. source
Quality gate on deploy yes The suite decides. docs documented Gates can block deployment until a suite passes. source
Automatic rollback yes On the metrics. docs not documented Not documented. source
Runs in your infrastructure yes Your cluster, or AgentCore, Google or Foundry. docs not documented Salesforce Hyperforce. source

Common questions

How is Agentforce priced?
Salesforce publishes Flex Credits, per-conversation and per-user options. Omnia runs on your infrastructure with no meter: free while you build, the core free in production, and an enterprise licencelicense per environment per year from £30,000.
Can an Omnia agent work with Salesforce data?
Yes. Salesforce APIs and MCP servers are tools like any other, with the end user’s identity carried to the call.

Put your own agent through the gate.

Install Omnia in your cluster and run it free while you build.

Agentforce claims are from Salesforce’s published documentation, checked 22 October 2026. Spot something out of date? Tell us.