Who it is for, and what it does well
Salesforce
Larger sales and service organisations that build on a configurable platform.
- A deep platform. Objects, workflows and apps can be built on it.
- A broad ecosystem. A large partner and app marketplace.
- Enterprise administration. Roles, audit and governance for big teams.
Vyre
The agentic command center for AI-native teams: people and agents work in one Space on a server you own.
Industry-neutral. You shape the records, and Flows, Playbooks and a Gate run the work.
Works with Vyre.
How Vyre connects to Salesforce today.
Today
Salesforce publishes REST and other APIs. A person adds a Connection in the Vault that declares the host, how the key is sent and which operations read, draft, change, send, spend or delete. A Flow then calls the service from a web step, or a custom module wraps it.
Where the vendor publishes an MCP server, a person can add it for agents to use.
Coming in 0.5.2
A packaged Integration, so the Connection and its operations arrive ready-made.
Vyre can be extended by integrating your Zoho, QuickBooks, RingCentral and the rest of your software stack*, Salesforce included.
*Where the vendor provides an API.
Where Vyre fits.
What Vyre does around it.
Vyre does not replace Salesforce. These are the parts of the work Vyre does around it.
Records
Working records and stages for a team that does not need the whole platform.
Agents
Agents that prepare the follow-up from a record.
Flows
Flows with an approved version for each repeated step.
Salesforce is a platform, and Vyre does not replace it for an organisation built on it. Vyre works beside it as the place where agents prepare the work.
Why that helps.
What a team gets from it.
Keep the system of record. Add a place where agents do the preparation and a person approves.
- Agents do the workAn agent takes the task and finishes it, hands it on or marks it stuck with a reason. A person is not moving data between tools by hand.
- Every outward action approvedAn email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes.
- Rules decide, not a modelA Flow follows stored steps and a person approves each version, so the same input takes the same path every run. A model is one step you place on purpose.
Side by side
| Question | Salesforce | Vyre |
|---|---|---|
| What it is | A CRM and platform for sales, service and custom apps. | A shared working layer for people and agents: records, tasks, Flows, documents, sites and a Gate. |
| Where it runs | Hosted by the vendor. | On a server you own. |
| Connecting to the other | Salesforce publishes REST and other APIs. | A Connection in the Vault and a Flow web step or custom module. Coming in 0.5.2: a packaged Integration. |
| Parts of the job in Vyre | Set by the product. | Records, Agents and Flows. |
| Outward actions | Set by how the product is configured. | Held at the Gate until a person approves the exact words. |
The left column comes from the product’s public documentation or describes the kind of product. Where it differs, the vendor’s own documentation is the one to trust.
Questions people ask
Does Vyre replace Salesforce?
No. Salesforce is a platform, and Vyre does not replace it for an organisation built on it. Vyre works beside it as the place where agents prepare the work.
How does Vyre work with Salesforce?
Salesforce publishes REST and other APIs. In Vyre, a person adds a Connection in the Vault that declares the host, how the key is sent and which operations read, draft, change, send, spend or delete. A Flow then calls the service from a web step, or a custom module wraps it. Coming in 0.5.2: a packaged Integration, so the Connection and its operations arrive ready-made. Integrations work where the vendor provides an API.