Who it is for, and what it does well
Bitwarden
People and teams that want a password manager they can self-host.
- Open source. The code is public.
- Self-hosting is an option. Teams can run it on their own server.
- Apps and extensions. Browser extensions and mobile apps.
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 Bitwarden today.
Today
Bitwarden publishes a command line tool and an API. 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*, Bitwarden included.
*Where the vendor provides an API.
Where Vyre fits.
What Vyre does around it.
Vyre does not replace Bitwarden. These are the parts of the work Vyre does around it.
Vault
The Vault seals the credentials your agents and Flows use, and hands them over as use only.
The Gate
A held send that uses a credential waits for a yes.
Keep Bitwarden for the logins your people fill in on the web. The Vault covers what agents and Flows use.
Why that helps.
What a team gets from it.
Both can run on your server. Vyre’s Vault is made for credentials an agent uses without reading.
- 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.
- 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.
- One place for people and agentsPeople and agents are members of the same Space. They share the records, tasks, files and chat, so nobody carries data from one tool to the next.
Side by side
| Question | Bitwarden | Vyre |
|---|---|---|
| What it is | An open-source password manager. | 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 | Bitwarden publishes a command line tool and an API. | 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. | Vault and The Gate. |
| 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 Bitwarden?
No. Keep Bitwarden for the logins your people fill in on the web. The Vault covers what agents and Flows use.
How does Vyre work with Bitwarden?
Bitwarden publishes a command line tool and an API. 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.