Who it is for, and what it does well
Wix
Small businesses and individuals who want to build a site with an editor and add features from an app market.
- An editor for everyone. Drag-and-drop editing.
- An app market. Add features without code.
- 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 Wix today.
Today
Wix publishes developer 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*, Wix 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. Wix stays the better fit for what it was built for.
Sites
Publish a site that an agent or developer built, with its own domain, a private preview and rollback.
The Gate
Going live is a held act.
Vault
A site gets only the secrets you grant it, one by one.
Keep Wix if the editor suits your team. Vyre fits a site built as files and published from your Space.
Why that helps.
What a team gets from it.
The site is built, previewed and published from the same place as the rest of the work.
- 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.
- 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.
- 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.
Side by side
| Question | Wix | Vyre |
|---|---|---|
| What it is | A website builder with hosting. | 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 | Wix publishes developer 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. | 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 Wix?
For some parts of the job, yes. Keep Wix if the editor suits your team. Vyre fits a site built as files and published from your Space.
How does Vyre work with Wix?
Wix publishes developer 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.