Liyagent and Salesforce Agentforce, compared
Where each runs, which models they use, what they connect to, how they are priced and when to choose which. A plain comparison for teams weighing Agentforce against a self-hosted agent platform.
- See the structural differences between Agentforce and Liyagent before a demo of either
- Compare how each is priced, with Salesforce's list prices as published
- Decide which fits a team whose work is, or is not, all inside Salesforce
Salesforce Agentforce and Liyagent both run AI agents that act on business data with a person's approval where it matters. They are built on different assumptions, and the right choice follows from those rather than from a feature list. Liyagent is independent of Salesforce. The Agentforce facts below are from Salesforce's own published pages, dated where it matters.
The structural differences
| Salesforce Agentforce | Liyagent | |
|---|---|---|
| Where agents run | Inside Salesforce's cloud, as part of your Salesforce org | On your own infrastructure (self-hosted), or hosted at liyagent.com |
| Which model | Models provided and hosted through Salesforce | Any provider: Anthropic, OpenAI, Gemini, Bedrock, or open models on your hardware through Ollama or vLLM |
| Home system | Salesforce: CRM, Service, Sales and the Salesforce data behind them | No home system. Salesforce is one of 50 connectors beside ServiceNow, Jira, SAP, Workday, Dynamics 365, NetSuite and Microsoft 365 |
| Working in Salesforce | Native: Flows, Prompt Builder, Data 360 | Liya for Salesforce reads records as the person asking, runs Flows, actions and Prompt Builder templates, and holds every write for approval |
| Approvals | Configured in Salesforce's own tooling | Writes wait for a person by default on new connections. Cedar policies per agent, tool and person |
| Evidence | Salesforce's logging | A hash-chained audit log with signed, independently verifiable exports |
| Custom agents | Agentforce Builder, inside Salesforce | Built in the console or the liya CLI, run under the same governance as the built-in agents |
Pricing
Agentforce (Salesforce list prices, USD, as published at salesforce.com/agentforce/pricing on 5 October 2026. Contracted prices may differ):
- Customer-facing agents: $2 per conversation.
- Employee-facing actions: Flex Credits at $500 per 100,000, where a standard action is 20 credits, so about $0.10 per action. Unused credits do not roll over.
- Add-ons for Sales, Service and Field Service: $125 per user per month, with unmetered Agentforce use for employees.
Liyagent is licensed per product and per year, not per conversation or per seat. The model cost is whatever your chosen provider charges, and an open model on your own hardware costs nothing per call. Write to sales@liyagent.com for a quote. The budgets page shows how spend is capped per agent and team.
When to choose which
Choose Agentforce when your agents' work lives in Salesforce, your data may be processed in Salesforce's cloud, and you want the native builder, Flows and Data 360 without running anything yourself.
Choose Liyagent when any of these is true:
- The agent's work crosses systems: a ticket in ServiceNow, the customer in Salesforce, the order in SAP, the invoice in Business Central.
- Data must stay in your network, or the model must be one you pick, including an open model on your own hardware.
- You need one audit trail and one policy model across every agent, not one per vendor.
- Cost per conversation or per action is the wrong shape for your volume.
Both can be true at once: Liya for Salesforce works alongside Agentforce in the same org, through Salesforce's APIs and its hosted MCP servers.
See it
Try it live: Liya on a sample CRM, every change held for your approval, with the audit trail to read afterwards. No sign-up.
Salesforce, Agentforce, Data 360 and related names are trademarks of Salesforce, Inc. Liyagent is not affiliated with, endorsed by or sponsored by Salesforce.