Vyre / Compare / AI assistants and agent platforms
ChatGPT team workspaces, Claude for teams and agent builders.
Vyre and AI assistants.
A team AI workspace gives people a strong assistant from one vendor. Vyre gives a team and its agents a shared place to work, on any model, with a person’s yes before anything leaves. Vyre uses these assistants as its models.
Who each is for
AI assistants and agent platforms
Team workspaces such as ChatGPT team plans and Claude for teams give each person a hosted assistant from one vendor, with shared projects and connections to common apps.
Agent builders let a developer define an agent with instructions and tools and run it on the vendor’s platform.
Vyre
Vyre is for a team that wants several people and several agents in one place, working on shared records, tasks and Flows.
It runs on your server and uses the models you already pay for.
What they do well.
Where ai assistants and agent platforms are strong.
- The vendor’s newest models and featuresThe people who build the model also build the assistant around it.
- Nothing to runYou sign up, invite the team and start. The vendor operates it.
- Polished appsChat apps on the web, desktop and phone, with admin controls for the organisation.
- Connections to common appsConnectors let an assistant read from and act in products your team already uses.
- Agent builders for custom agentsA developer can wire tools and instructions into an agent without hosting the model.
Where Vyre is different.
Six things Vyre does its own way.
Any model, one chat
Claude, Codex, Grok and OpenRouter answer in the same chat through your own accounts or keys. Changing provider mid-conversation does not lose the conversation.
Agents have a role and a reach
Each agent has its own job, instructions and the projects it can reach. What it may do is never more than the person who started it.
The work lives beside the chat
Records, tasks, files and Flows sit in the same Space as the conversation, so an agent works on the real thing.
Sessions on your own computer
A session can run on a person’s own computer, in a sandbox with an encrypted workspace, or on the server. The chat shows which.
Sends wait at the Gate
An agent can ask to send. A person approves the exact words with a proof made on their own device.
Credentials stay out of the model
A model sees a placeholder. The real value goes in at the moment of sending, outside the model.
Side by side.
The two approaches, row by row.
The left column describes the kind of tool, from its public documentation. Where a product differs, its own documentation is the one to trust.
| Question | AI assistants and agent platforms | Vyre |
|---|---|---|
| Where it runs | The vendor’s cloud. | A server you own. Sessions run there or on a person’s own computer. |
| Models | The vendor’s own models. | Claude, Codex, Grok and OpenRouter, through your own accounts or keys. |
| Shared work | Shared workspaces for chats and files. | Records, tasks, files and Flows in the same Space as the chats. |
| Who can act | A person prompts. Connectors and agents act inside the product. | People and agents are members with a role and a reach. An agent has no more authority than the person who started it. |
| Repeatable processes | Saved instructions and prompts. Agent builders define workflows in code or configuration. | Flows: stored steps, a person approves each version, every run follows it. |
| Outward actions | Set by each product’s connectors and permissions. | Held at the Gate until a person approves the exact words. |
| Credentials | Connectors sign in with an account. | The Vault. Agents get use only and never read the value. |
| Getting started | Sign up and invite people. | Set up a server you own, then pair the Vyre app. |
How they work together.
Use both, and let each do its part.
- 01A person asks an assistantIn Claude, or any outside AI tool connected over MCP
- 02Vyre checks the callerIt works out who is calling and applies that role’s tool list
- 03Records, Flows and agents actThe work happens in the Space, as the person or agent
- 04The Gate holds what leavesA person approves the exact words
An outside AI tool reaches Vyre through the same door as the app does.
Keep the assistants. Vyre signs in to your own provider accounts and uses them as the models for its agents, so the team keeps the vendor’s models and adds a shared place to work. An outside AI tool connected over MCP can ask Vyre to do work, and the call is checked like any other.
Use the assistant for the thinking and Vyre for the work: the records it reads, the Flow it runs and the yes that lets the result out.
Questions people ask
Does Vyre include its own model?
No. Vyre is free, and you pay your AI providers directly. It runs Claude, Codex, Grok and OpenRouter through your own subscriptions or keys.
Which AI accounts does Vyre work with?
The ones you add. Vyre works with Claude, Codex, Grok and others through your own sign-ins and keys, and one chat can hold more than one.