Who it is for, and what it does well
Make
Teams that want to design branching scenarios across many apps without writing code.
- A canvas for complex scenarios. Branches, routers and data mapping are drawn and read as a picture.
- Many ready-made app modules. A wide library of connections.
- Scenario history. Each run can be inspected afterwards.
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 Make today.
Today
A scenario can call a Flow’s path, and a Flow’s web step can call a scenario’s webhook. 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*, Make included.
*Where the vendor provides an API.
Where Vyre replaces it.
What Vyre does natively.
Vyre does these parts of the job natively, so a team can drop a seat or a step. Make stays the better fit for what it was built for.
Flows
Flows run stored steps with branches, and a person approves each version before it runs.
Records
The data a Flow works on is a record kept in the same Space, not a payload passed along.
Agents
A judgment step goes to an agent instead of a fixed rule.
Keep Make for the connections to apps Vyre does not package yet, and keep any scenario that already works.
Why that helps.
What a team gets from it.
A scenario is cheap to build. Vyre adds an approved version and a Gate on what leaves.
- 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.
- 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.
- Fewer subscriptions and less copy-pasteOne Space covers parts of a job that took several tools, so there are fewer logins and fewer places to keep in step.
Side by side
| Question | Make | Vyre |
|---|---|---|
| What it is | Builds multi-step automations on a visual canvas. | 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 | A scenario can call a Flow’s path, and a Flow’s web step can call a scenario’s webhook. | 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. | Flows, Records and Agents. |
| 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 Make?
For some parts of the job, yes. Keep Make for the connections to apps Vyre does not package yet, and keep any scenario that already works.
How does Vyre work with Make?
A scenario can call a Flow’s path, and a Flow’s web step can call a scenario’s webhook. 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.