Who it is for, and what it does well
Webflow
Designers and marketing teams that want to build and publish custom sites visually.
- Design control. Layout and style are built visually, close to the code.
- A CMS. Content collections for pages and posts.
- Hosting included. The vendor serves the site.
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 Webflow today.
Today
Webflow publishes a Data API for sites and content. 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*, Webflow 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. Webflow stays the better fit for what it was built for.
Sites
Sites put a folder of files, a repo or a built site online. An agent builds it, previews it privately and asks for one yes.
The Gate
Going live is a held act with a version you can roll back.
Vault
A site gets only the secrets you grant it, one by one.
Keep Webflow if your designers build in its editor. Vyre publishes sites that agents or developers build as files.
Why that helps.
What a team gets from it.
An agent builds and previews the site, and nothing is public until you say yes.
- 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.
- 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.
Side by side
| Question | Webflow | Vyre |
|---|---|---|
| What it is | A visual website builder and host. | 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 | Webflow publishes a Data API for sites and content. | 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. | Sites, The Gate and Vault. |
| 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 Webflow?
For some parts of the job, yes. Keep Webflow if your designers build in its editor. Vyre publishes sites that agents or developers build as files.
How does Vyre work with Webflow?
Webflow publishes a Data API for sites and content. 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.