Do I have to be on Salesforce to use monō?

No. monō is system-agnostic and sits on top of the stack you already run, Salesforce included. It adds agents without asking you to move your system of record.

Will monō tie me to a platform?

No. Because it is model-agnostic and runs on your systems, you can change models and tools underneath without a re-platform. The work is yours, inside your tenant.

Where does customer data live?

In your own cloud. monō is inference-only, so the data never leaves your perimeter to train or build anyone else's product.

When is Agentforce the better call?

When Salesforce is your centre of gravity and you want agents native to its model and interface, Agentforce is the natural fit.

How does monō handle data outside Salesforce?

It works across the core, the ledger and the tools around the CRM. Agents act on the whole stack, not only the Salesforce object model.

Does it get sharper over time?

Yes, inside your tenant only. Memory compounds across your accounts, people and history, and never crosses to another customer.

An honest comparison

monō vs Salesforce Agentforce

Agentforce keeps you on Salesforce. monō works on top of whatever you run.

Our honest position

Agentforce is a strong choice if your world is Salesforce and you want agents tightly inside it. monō is model-agnostic and system-agnostic, it sits on top of the core, CRM, ledger and tools you already run, and keeps your data in your cloud.

Dimension	Salesforce Agentforce	monō
System scope	Best inside the Salesforce platform	Sits on top of any stack
Data residency	Salesforce cloud	Your cloud, inference-only
Model choice	Provider-tied	Model-agnostic, swap freely
Lock-in	Deepens platform commitment	No re-platform; swap the engine
Governance	Within the platform	Built-in eval + monitoring across all work
Cost to run	Per-conversation / consumption pricing on platform	Harness efficiency + BYO keys, no per-conversation markup
Compounds over time?	No memory that compounds across your tools and teams	Yes, one memory across your tiles, people and time, inside your tenant

System scope

Salesforce Agentforce: Best inside the Salesforce platform

monō: Sits on top of any stack

Data residency

Salesforce Agentforce: Salesforce cloud

monō: Your cloud, inference-only

Model choice

Salesforce Agentforce: Provider-tied

monō: Model-agnostic, swap freely

Lock-in

Salesforce Agentforce: Deepens platform commitment

monō: No re-platform; swap the engine

Governance

Salesforce Agentforce: Within the platform

monō: Built-in eval + monitoring across all work

Cost to run

Salesforce Agentforce: Per-conversation / consumption pricing on platform

monō: Harness efficiency + BYO keys, no per-conversation markup

Compounds over time?

Salesforce Agentforce: No memory that compounds across your tools and teams

monō: Yes, one memory across your tiles, people and time, inside your tenant

Cost-to-run is illustrative, same outcome, materially fewer tokens; with your own API keys, your rates, no markup. All marks belong to their owners.

Coding agent, raw

monō harnessup to 70% fewer tokens

Same task, same outcome, a fraction of the tokens. Illustrative.

No FUD

When they're the right call.

Salesforce is your system of record and you intend to stay all-in.
You want agents native to the Salesforce data model and UI.
You’re comfortable with vendor-hosted data and provider-tied models.

If you’re committed to Salesforce as the centre of gravity, Agentforce is the natural fit.

The architecture difference

Three decisions they can't retrofit.

Sovereign by architecture

Inference-only. Your cloud, your keys, the data never builds anyone else's product.

Model-agnostic

Frontier, open-source, fine-tuned, swap models without rewrites.

Your own API keys

Your lab accounts, your negotiated rates. We never mark up your tokens.

In depth

The fuller picture.

What Agentforce is good at

Agentforce puts agents tightly inside Salesforce. If Salesforce is your system of record and you intend to stay all-in, native agents on that data model are a strong, well-supported choice. They speak the Salesforce object model fluently. They live where your sales and service teams already work.

Why model and system choice matter

monō sits on top of whatever you run: the core, the CRM, the ledger and the tools around them. It keeps your data in your own cloud and stays model-agnostic, so you can swap the engine as the frontier moves without re-platforming. You add autonomous agents across the business without deepening commitment to a single suite.

FAQ

Questions, answered straight.

Do I have to be on Salesforce to use monō?: No. monō is system-agnostic and sits on top of the stack you already run, Salesforce included. It adds agents without asking you to move your system of record.
Will monō tie me to a platform?: No. Because it is model-agnostic and runs on your systems, you can change models and tools underneath without a re-platform. The work is yours, inside your tenant.
Where does customer data live?: In your own cloud. monō is inference-only, so the data never leaves your perimeter to train or build anyone else's product.
When is Agentforce the better call?: When Salesforce is your centre of gravity and you want agents native to its model and interface, Agentforce is the natural fit.
How does monō handle data outside Salesforce?: It works across the core, the ledger and the tools around the CRM. Agents act on the whole stack, not only the Salesforce object model.
Does it get sharper over time?: Yes, inside your tenant only. Memory compounds across your accounts, people and history, and never crosses to another customer.

See it on your own use case.

Your use case, live on the platform, beside whatever you're evaluating.