Who it is for, and what it does well
n8n
Technical teams that want a node-based workflow tool they can run themselves.
- Self-hosting is an option. The same workflow tool can run on a server you control.
- Code where you need it. Nodes can run code, so a technical team is not boxed in.
- Many integration nodes. A broad library of connections.
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 n8n today.
Today
A workflow can call a Flow’s path, and a Flow’s web step can call a workflow’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*, n8n 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. n8n stays the better fit for what it was built for.
Flows
Flows run on the same server as the records, with a person approving each version.
Vault
A Flow uses a login from the Vault and a model never sees the value.
Agents
Agents are members of the Space and take tasks a Flow hands them.
If n8n already runs on your server and links your apps, keep it. Vyre sits on top as the place the work and the approvals live.
Why that helps.
What a team gets from it.
Both can run on your server. Vyre adds the records, the agents and the Gate around the workflows.
- Data on your own serverRecords, files and the history of every decision stay on a server you own. Sealed fields show an agent a placeholder.
- 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.
Side by side
| Question | n8n | Vyre |
|---|---|---|
| What it is | Builds workflows with nodes, hosted or on your own server. | A shared working layer for people and agents: records, tasks, Flows, documents, sites and a Gate. |
| Where it runs | Hosted by the vendor, or self-hosted. | On a server you own. |
| Connecting to the other | A workflow can call a Flow’s path, and a Flow’s web step can call a workflow’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, Vault 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 n8n?
For some parts of the job, yes. If n8n already runs on your server and links your apps, keep it. Vyre sits on top as the place the work and the approvals live.
How does Vyre work with n8n?
A workflow can call a Flow’s path, and a Flow’s web step can call a workflow’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.