vyre / site

# Vyre, in full

Vyre is the agentic command center for AI-native teams. Our mission is to help every professional services team become AI-native. People and agents share chats, records, tasks, files and automations (Flows) on a server the team owns, and anything that leaves the team waits for a person's yes. Open source (Apache 2.0), self-hosted, any model: Claude, Codex, Grok and OpenRouter through your own subscriptions or keys. Reach it from the Vyre app on a Mac, on Windows, on a phone, or in a browser.

Release 0.5.1. Updated 2026-10-23. Source: https://github.com/vyre-ai/vyre. Licence: Apache 2.0.

## What it is
- People and agents in the same chats. @ a teammate or an agent, # a record, a file or a project. Anyone in the Space can make an agent and share it with a person or a role as use-only or full.
- Agents wake on a task and finish it: the agent ends the task as done, hands it on, or marks it stuck with a plain reason. Each agent and each project has an AGENTS.md instructions file.
- One group chat across providers. Claude, Codex, Grok and OpenRouter answer in the same chat through the sign-ins and keys you add. Give agents different jobs: a team that does the work, one model that reviews, one that plans.
- Flows run the same way every time. A trigger (a person, a schedule with business hours and holidays, a record change, a stage, a form, a link or a watcher), then steps: find, create, update, find-or-create, wait for a time, a date or an event, ask, assign, call a connected service, run an agent. A person approves a Flow before it runs, and each run has its own page.
- Playbooks are project templates: stages, the tasks in each stage, who does each task, and when a stage counts as done. Each kind of work can run as its own track, with its own Playbook and Flows over shared records.
- Records: contacts, projects, tasks and your own record types, with fields in named groups, tags, saved views, Excel or CSV import, and CSV export from the web app. Fields marked sealed show an agent a placeholder, never the value.
- Documents fill your own Word templates from a record and the records linked to it, as Word or PDF. Signing sends a document for signature from a record; the signer needs no account, and the signed copy files back on the record.
- Files: agent folders and Space folders, Shared with me, Office previews and earlier versions, plus linked Google Drive and Dropbox folders read through each person's own account.
- The Vault holds passwords, API keys, logins with one-time codes, cards, notes and SSH keys, in groups, shared as Can use or Can edit. Agents use a credential without seeing it.
- A project's site: an agent builds a site, previews it at a private address, and puts it live on one yes from you. Sites is not a place in the sidebar.
- Needs you is one place for approvals, asks and stuck tasks. Teams get roles, per-project seat levels and invites with a role.
- Everything that leaves your server (an email, a payment, a deletion, a published page) waits at the Gate for a person to approve the exact words. An agent can ask and cannot approve.
- Architecture: see https://vyre.run/architecture/ and https://vyre.run/docs/project/ARCHITECTURE.
- The four pillars in depth: https://vyre.run/vault/ (sealed credentials, use-only grants, leases), https://vyre.run/records/ (custom types, links, link hops in tokens, sealed fields), https://vyre.run/flows/ (triggers, approved versions, the runner, holds) and https://vyre.run/agents/ (instructions, memory, access, waking on a task).

## Vyre Computer
- Vyre Computer is how an agent uses a browser, a desktop or an app when no cleaner way exists: https://vyre.run/computer/. It tries the site's own interface first and the screen last. Logins are filled by the Vault, so the model never sees a password. Anything that sends, posts or pays waits for a person.
- Vyre for Chrome drives the Chrome you already have open, signed in as you: https://vyre.run/computer/chrome/. It runs two ways. Standalone, it is an MCP server plus a Chrome extension for Claude Code with no Vyre server (command: vyre-chrome; build it from https://github.com/vyre-ai/vyre/tree/main/local/hands-chrome-mac/standalone). Native, it is the same code inside Vyre on a Mac, where a held send becomes a card in Needs you. The Vault fill extension (modules/vault-extension) fills logins, passkeys and one-time codes from your Vault in Chrome, Arc, Edge, Brave and Firefox.
- How Chrome control works is written as an engineering document at https://vyre.run/computer/architecture/: a read is tried through the site's own API call (learned from the page's traffic, called from inside the page with your login); the page is the fallback; DevTools and a screenshot come after. It remembers each site's structure (never a value) and reuses it. An agent posts its plan first. A send, post or payment is held and re-checked against the page before it goes. Esc stops everything. Every session writes a masked local log.
- Computer use today: one front door (computer.use) over your Chrome, your Mac (through the accessibility tree) and a computer of each agent's own on your server (a desktop, Chrome and a terminal, with a home folder that survives restarts); a Vault sign-in the agent never sees; take-over by a person; a computer you lend to a Space runs its sessions in a sandbox with an encrypted workspace.
- Next (direction, not dates): one Chrome extension that signs in like a device of yours (0.7), Chrome control for chats (0.7), a chat in the browser side panel (0.7), Screen Share on every device, driving a connected computer from your phone, agents borrowing a computer from the Space's pool, and a Chrome profile per agent.

## Vyre by kind of firm (pages under https://vyre.run/for/)

Each page follows one client from inquiry to closed work for an invented firm, and names the Vyre pieces behind every step. The firms and the sample data are invented.

### Law firms: https://vyre.run/for/law-firms/
1. Inquiry comes in
2. Screening and conflict check
3. Consultation
4. Engagement letter signed
5. Matter opens from a Playbook
6. Deadlines from a trigger date
7. Documents and client updates
8. Closing and billing hand-off
Tracks (Playbooks): Personal injury, Estate plan. Agents: Intake, Drafting, Reviewer, Updates. Apps named: Clio, Lawmatics, Practice tools, Zoho, RingCentral, Google Workspace, Microsoft 365, Dropbox, DocuSign.

### Accounting firms: https://vyre.run/for/accounting-firms/
1. Inquiry and scoping
2. Proposal and engagement letter
3. Client onboarding
4. Document collection
5. Monthly close Playbook
6. Tax season tracks
7. Review and delivery
8. Billing and renewal
Tracks (Playbooks): Monthly close, Individual return, Business return. Agents: Intake, Chaser, Preparer assistant, Reviewer. Apps named: QuickBooks, Xero, Karbon, Zoho, RingCentral, Google Workspace, Microsoft 365, Dropbox, DocuSign.

### Consulting firms: https://vyre.run/for/consulting-firms/
1. Inquiry comes in
2. Research and scoping
3. Proposal
4. Statement of work signed
5. Engagement from a Playbook
6. Weekly status
7. Change requests
8. Final report and renewal
Tracks (Playbooks): Diagnostic, Program, Retainer. Agents: Research, Proposal, Reviewer, Status. Apps named: Zoho, QuickBooks, Xero, RingCentral, Google Workspace, Microsoft 365, Dropbox, DocuSign.

### Marketing and creative agencies: https://vyre.run/for/marketing-agencies/
1. Inquiry comes in
2. Discovery and brief
3. Proposal and statement of work
4. Onboarding
5. Campaign Playbook
6. Creative review rounds
7. Client approval
8. Reporting and renewal
Tracks (Playbooks): Social retainer, Paid media, Website build. Agents: Intake, Content, Reviewer, Site. Apps named: Zoho, RingCentral, Google Workspace, Microsoft 365, Dropbox, DocuSign, QuickBooks, Ad and analytics platforms.

### Real estate brokerages: https://vyre.run/for/real-estate-brokerages/
1. Lead comes in
2. Qualification
3. Agreement signed
4. Transaction from a Playbook
5. Key dates from the contract date
6. Documents and client updates
7. Closing
8. Follow-up
Tracks (Playbooks): Listing side, Buyer side. Agents: Responder, Coordinator, Reviewer, Content. Apps named: Zoho, RingCentral, Google Workspace, Microsoft 365, Dropbox, DocuSign, Transaction and listing tools.

Connecting a stack: Vyre can be extended by integrating your Zoho, QuickBooks, RingCentral and the rest of your software stack*. *where the vendor provides an API. Today: a Connection plus a Flow service step, or a custom module. Coming in 0.7: packaged Integrations (Clio, Lawmatics, GoHighLevel and DecisionVault are the first planned).
- Architecture: see https://vyre.run/architecture/ and https://vyre.run/docs/project/ARCHITECTURE.md.

## Docs
- [Docs home](https://vyre.run/docs/): every guide, reference page and architecture page, in the same design as this site
- [docs/llms.txt](https://vyre.run/docs/llms.txt): every docs page as a link to its Markdown; https://vyre.run/docs/llms-full.txt has them all in one file
- [index.json](https://vyre.run/docs/index.json): every command, tool, event, config key and concept, with the page that explains it
- [Architecture, the front door](https://vyre.run/docs/project/ARCHITECTURE.md): how Vyre is built, with a table of contents into every architecture page
- [Map your business onto Vyre](https://vyre.run/docs/for-agents/MAP-YOUR-BUSINESS.md): the method an AI agent follows to turn a business into members, records, Flows, agents and Gate rules
- [Development rules](https://vyre.run/docs/project/DEVELOPMENT-RULES.md): the rules every change follows
- [Roadmap](https://vyre.run/docs/roadmap.md) and [plans by version](https://vyre.run/docs/roadmap/README.md)
- Every docs page is also its raw Markdown at the same path with .md, for example https://vyre.run/docs/architecture/overview.md

## Where it runs
- Server: Linux with Docker Compose 2.24 or newer, or a Mac that stays on. Installed in /srv/vyre by one line, curl -fsSL vyre.run/i | sh, which the Vyre app shows. Images are pulled by digest after their signatures are checked. Updates are signed with a pinned key; a box refuses unsigned, tampered or older releases. Stable never takes a prerelease.
- Mac: the Vyre app in its own window, from the GitHub release (Vyre-aarch64.dmg or Vyre-x86_64.dmg). Not yet signed with an Apple Developer ID, so it opens once with Open Anyway. Needs macOS 14 or newer.
- Windows: Vyre, a tray app with an Alt+Space panel, installed with VyreSetup.exe from the GitHub release. Not Authenticode-signed yet, so Windows asks for "More info", then "Run anyway". Signs in with the Space, your username and your password, or Continue with GitHub. The server does not run on Windows yet.
- Phone: the Vyre app, sideloaded (the Android APK from the release, or an iPhone build installed with Xcode), signed in with the Space, your username and your password, or Continue with GitHub, with Face ID or a fingerprint. A removed phone wipes itself.
- Network: built in. Nothing to install or sign in to; the relay carries a connection when a direct path is not possible.

## Install
1. Install the app from https://github.com/vyre-ai/vyre/releases/latest: Vyre-aarch64.dmg or Vyre-x86_64.dmg on macOS, VyreSetup.exe on Windows. Both are sideloaded (not signed with a store identity yet).
2. Open the app. Sign in with the Space, your username and your password, or Continue with GitHub. Save the recovery code.
3. Choose Join a space, or create one on a Linux machine or a computer that stays on. Records live in Vyre's own store. 8 GB of memory is recommended and 4 GB is the least.
4. To add a server, run the one line the app shows on it, as yourself: `curl -fsSL https://vyre.run/i | VYRE_CODE=<code from the app> sh`. The server installs Vyre and pairs itself. There is no setup page to paste a code into.
5. On your phone: Vyre-android.apk from the release on Android (sideloaded); iPhone has no App Store app yet. Open Vyre on the phone and sign in with the Space, your username and your password, or Continue with GitHub.

## What it costs
Vyre is free and open source. You pay your AI providers (Claude, Codex, Grok, OpenRouter) on your own subscriptions or keys. Your data lives on your devices and on servers you or your team run. Vyre doesn't hold it.

## Where your data lives
Records, chats, files and the vault stay on your server and your computers. vyre.run holds your name's DNS record and runs the relay (relay.vyre.run), which carries phone pairing, end-to-end encrypted. Prompts go to your AI provider the way they would from that provider's own app.

## Releases
- 0.5.1 (out now): first-time setup adds a server before the vault, Vyre uses less memory, and the docs show code examples correctly.

## How Vyre compares
Each page below describes approaches. About another product it says only what that product’s own public documentation says, and otherwise it describes the kind of tool. Vyre can be extended by integrating your Zoho, QuickBooks, RingCentral and the rest of your software stack*. *Where the vendor provides an API. Packaged Integrations are Next, in 0.7.

### Vyre and automation tools: Zapier, Make and n8n (https://vyre.run/compare/automation-tools/)
Zapier, Make and n8n connect apps. Vyre keeps the work, the people and the agents in one place and runs Flows over them. The two fit together well, and this page shows where each is the better tool.
- Who automation tools are for: Zapier, Make and n8n are workflow automation tools. A trigger in one app starts actions in others. They suit operations, marketing and technical teams that want to link the apps they already use, often without writing code.
- What they do well: A large catalogue of app connections. Each of the three offers a wide library of ready-made connections to other products. Fast for a single link. One trigger and one action can be running in minutes. Visual builders. People who do not write code build and read automations on a canvas. Run history. Each shows what ran and what failed, and teams that run them every day know how to read it. Choice of hosting. Zapier and Make are hosted services. n8n can also be run on your own server.
- Where Vyre is different: Flows start from your work. A Flow can start when a record is created or changes, when a record enters a stage, on a schedule, from a form, or when something new arrives in a mailbox or folder. A person approves a version. Editing a Flow makes a new version. A person approves it before it runs, and a saved test that fails blocks the approval. You can go back to an earlier version. Judgment is one step you place. A Flow follows its steps the same way each run. When a step needs judgment, you hand it to an agent, which finishes the task, hands it on, or marks it stuck with a reason. Sends wait at the Gate. A Flow that emails a customer holds the message until a person has read the exact words and approved them. An approved Flow version can carry one yes for named destinations and limits. The Flow has the approver’s reach. A Flow runs with no more authority than the person who approved it, and every step is checked the way a person’s own action is. Credentials stay sealed. A Flow or an agent uses a login from the Vault. The value is put in at the moment of sending and a model never sees it.
- How they work together: Keep the automations that work. A Zap, scenario or workflow can call a Vyre Flow’s path when something happens in an app, and the Flow takes over with the records, the agents and the Gate. A Flow’s web step can call an automation tool’s webhook when you want its connection to an app Vyre does not yet package. A useful split: let the automation tool carry data between apps, and let Vyre decide what the team does with it and who says yes.
- Comparison:
  - Where it runs. Automation tools: Zapier and Make are hosted by the vendor. n8n is hosted or self-hosted. Vyre: On a server you own.
  - What starts work. Automation tools: A trigger in a connected app. Vyre: A person, a schedule, a record change or stage, a form or inbound call, or something new in a mailbox or folder.
  - What it works on. Automation tools: Data passed from one app to another. Vyre: Records, tasks and files kept in the same place as the Flow.
  - Judgment steps. Automation tools: Many include AI steps. Vyre: An agent step you place on purpose. A task it cannot finish is marked stuck, with a reason.
  - Changing a live automation. Automation tools: Set by each tool. Vyre: An edit is a new version. A person approves it, and an earlier version can be restored.
  - Outward actions. Automation tools: Set by how each automation is built. Vyre: Held at the Gate until a person approves the exact words.
  - Credentials. Automation tools: Held in each tool’s own connection store. Vyre: The Vault. Agents get use only and never read the value.
  - Ready-made app connections. Automation tools: A large catalogue. Vyre: A connection to any service that has an API, used from a Flow’s web step. Coming in 0.7: packaged Integrations.
  - Cost. Automation tools: Set by each vendor. Vyre: Vyre is free and open source (Apache 2.0). You pay your AI providers directly.

### Vyre and work management tools: Notion, ClickUp, Asana, Monday (https://vyre.run/compare/work-management/)
Notion, ClickUp, Asana and Monday help a team plan and track work. Vyre adds agents that take tasks, a Gate on what leaves, and a server you own. Many teams will use both.
- Who work management are for: Notion, ClickUp, Asana and Monday are hosted workspaces for planning and tracking work. They hold tasks, boards, timelines, documents and dashboards. They suit teams that want one shared place to see who is doing what and when.
- What they do well: Views people already know. Boards, lists, calendars and timelines, refined over many years. Templates and a familiar interface. A new teammate or an outside client often knows the tool already. Docs and wikis next to tasks. Notion in particular puts pages, databases and notes in one workspace. Reporting dashboards. Portfolio and workload views for managers. A large ecosystem. Integrations, templates and a community of people who can help.
- Where Vyre is different: Agents are members. An agent has a job, instructions in its own AGENTS.md, the projects it can reach and a share of the Vault. A task assigned to it wakes it. It finishes the task, hands it on, or marks it stuck. Records of any shape. Beside tasks, a Space holds contacts, organizations, projects and record types you define, linked in any web, with boards by stage, calendars and dashboards. Playbooks run each kind of work. A Playbook lists the stages and tasks of one kind of job and who does each: a person, a role or an agent. It goes live when an owner approves it. Flows between the stages. Where a Playbook sets the stages, a Flow does the actions between them, and a person approves each version. Sends wait at the Gate. An agent that finishes a task cannot email the client on its own. The Gate holds the message until a person approves it. Your data on your server. Records, files and history are kept on a server you own. Sealed fields show an agent a placeholder.
- How they work together: Keep the board your team already reads. Where the vendor provides an API or an MCP server, a connection lets a Flow read or update it, and a person can add the MCP server for agents to use. Vyre then holds the records, the agent work and the approvals, and the planning tool shows the status. Teams that want one place for everything can run the work in Vyre alone: tasks, Playbooks and boards by stage are all there.
- Comparison:
  - Where it runs. Work management: Hosted by the vendor. Vyre: On a server you own.
  - Unit of work. Work management: Tasks, items, pages and databases. Vyre: Tasks, plus records of any type you define, linked to each other.
  - Who does the work. Work management: People. Most of these tools now include AI features that help inside the tool. Vyre: People and agents, both as members. An agent takes a task, then finishes, hands on or marks it stuck.
  - Process. Work management: Project and board templates. Vyre: Playbooks: stages, tasks and who does each. An owner approves one before it goes live.
  - Automation. Work management: Built-in rules and automations. Vyre: Flows: stored steps, a person approves each version, every run follows it.
  - Views. Work management: Boards, lists, calendars, timelines and dashboards. Vyre: Boards by stage, calendars by date and dashboards over any record type.
  - Documents. Work management: Pages and docs inside the tool. Vyre: Your own Word templates filled from records, with signing for people who have no account.
  - Outward actions. Work management: Set by how each automation is built. Vyre: Held at the Gate until a person approves the exact words.
  - Sensitive fields. Work management: The tool’s own permission settings. Vyre: Sealed fields show an agent a placeholder, and fields can be hidden from named roles.

### Vyre and AI assistants: team workspaces and agent platforms (https://vyre.run/compare/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 ai assistants and agent platforms are for: 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.
- What they do well: The vendor’s newest models and features. The people who build the model also build the assistant around it. Nothing to run. You sign up, invite the team and start. The vendor operates it. Polished apps. Chat apps on the web, desktop and phone, with admin controls for the organisation. Connections to common apps. Connectors let an assistant read from and act in products your team already uses. Agent builders for custom agents. A developer can wire tools and instructions into an agent without hosting the model.
- Where Vyre is different: 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.
- How they work together: 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.
- Comparison:
  - Where it runs. AI assistants and agent platforms: The vendor’s cloud. Vyre: A server you own. Sessions run there or on a person’s own computer.
  - Models. AI assistants and agent platforms: The vendor’s own models. Vyre: Claude, Codex, Grok and OpenRouter, through your own accounts or keys.
  - Shared work. AI assistants and agent platforms: Shared workspaces for chats and files. Vyre: Records, tasks, files and Flows in the same Space as the chats.
  - Who can act. AI assistants and agent platforms: A person prompts. Connectors and agents act inside the product. Vyre: 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. AI assistants and agent platforms: Saved instructions and prompts. Agent builders define workflows in code or configuration. Vyre: Flows: stored steps, a person approves each version, every run follows it.
  - Outward actions. AI assistants and agent platforms: Set by each product’s connectors and permissions. Vyre: Held at the Gate until a person approves the exact words.
  - Credentials. AI assistants and agent platforms: Connectors sign in with an account. Vyre: The Vault. Agents get use only and never read the value.
  - Getting started. AI assistants and agent platforms: Sign up and invite people. Vyre: Set up a server you own, then pair the Vyre app.

### Vyre with practice software and CRMs: Clio, Karbon, HubSpot (https://vyre.run/compare/practice-software/)
Practice management and CRM suites are built for one job and do it well. Vyre does not replace them. It adds a working layer beside them, where people and agents do the intake, drafting, follow-up and review, with a yes before anything goes out.
- Who practice software and crm suites are for: Clio is practice management for law firms. Karbon is practice management for accounting firms. HubSpot is a CRM with marketing and sales tools. Each is a hosted system built for its field. They suit firms and teams that want one dependable record of clients, work and communication.
- What they do well: Built for one profession or function. The record types, terms and screens match how the field works. A system of record. Clients, work, communication and history sit in one dependable place that the whole firm uses. Established ecosystems. Each has partners, integrations and people who know it well. Years of fit with daily practice. They reflect how firms in that field actually run their day. Vendor support and a hosted service. The vendor runs it, updates it and answers questions.
- Where Vyre is different: A working layer, not a replacement. Vyre does not aim to replace your billing or your system of record. It holds the working records and the agent work around them. Agents do the preparation. An agent can read a new enquiry, draft a reply from your price list or fill a document, and then stop for a person. Documents from your templates. Your own Word templates are filled from a record and its linked records, and a model does not retype them. Signing needs no account for the signer. Sends wait at the Gate. Anything that goes to a client, a payment or a deletion waits until a person has read the exact words and approved them. Your server holds the working data. Records, files and the history of every decision stay on a server you own. Sealed fields keep the most sensitive values away from agents. Shaped to your business. Define record types and fields in your own words, link them, and give each kind of work its own Playbook and Flows.
- How they work together: Vyre can be extended by integrating your Zoho, QuickBooks, RingCentral and the rest of your software stack*, and the same goes for Clio, Karbon and HubSpot. The suite stays the system of record. Vyre reads from it, does the preparation, and writes back once a person has said yes. *Where the vendor provides an API. Integrations as packaged modules are Next, in 0.7. Today a person adds a connection and a Flow uses it from a web step, or a custom module wraps the service.
- Comparison:
  - What it is for. Practice software and CRM suites: Clio: legal practice management. Karbon: accounting practice management. HubSpot: CRM, marketing and sales. Vyre: A shared working layer for people and agents, with records you shape, Flows, Documents and Signing, Sites and a Gate.
  - Where it runs. Practice software and CRM suites: Hosted by the vendor. Vyre: On a server you own.
  - Specialised to a profession. Practice software and CRM suites: Yes, to the field each was built for. Vyre: Industry-neutral. Kits supply starter record types and Flows.
  - Agents. Practice software and CRM suites: Many include AI features inside the product. Vyre: Agents are members of the Space and work across its records, tasks and files.
  - Documents. Practice software and CRM suites: Document features vary by product. Vyre: Your Word templates filled from records, signing with no account for the signer.
  - Outward actions. Practice software and CRM suites: Set by how each product and automation is configured. Vyre: Held at the Gate until a person approves the exact words.
  - Connecting to the suite. Practice software and CRM suites: Native to the suite. Vyre: Today: a connection plus a Flow web step, or a custom module, where the vendor provides an API. Coming in 0.7: packaged Integrations.

### Vyre and Zapier (https://vyre.run/compare/zapier/)
- What Zapier is: Connects apps with triggers and actions. Operations and marketing teams that want to link the apps they already use, often without writing code.
- What it does well: A very large catalogue. Ready-made connections to a wide range of products. Fast for one link. One trigger and one action can run within minutes. Visual and familiar. People who do not code build and read automations.
- Works with Vyre today: A Zap can send a request to a Flow’s path, and a Flow’s web step can call a Zap’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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Flows. A Flow starts from a record, a stage, a schedule or a form, so the work and the automation sit in one place. Agents. A step that needs judgment goes to an agent, which finishes the task or marks it stuck. The Gate. A Flow that emails a customer holds the message until a person approves it. Keep Zapier for the long tail of apps that Vyre does not package yet. Let it carry data between apps and let Vyre decide what the team does with it.
- Why that helps: Rules decide, not a model. A 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 approved. An 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 agents. People 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.

### Vyre and Make (https://vyre.run/compare/make/)
- What Make is: Builds multi-step automations on a visual canvas. Teams that want to design branching scenarios across many apps without writing code.
- What it does well: A canvas for complex scenarios. Branches, routers and data mapping are drawn and read as a picture. Many ready-made app modules. A wide library of connections. Scenario history. Each run can be inspected afterwards.
- Works with Vyre today: A scenario can call a Flow’s path, and a Flow’s web step can call a scenario’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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Flows. Flows run stored steps with branches, and a person approves each version before it runs. Records. The data a Flow works on is a record kept in the same Space, not a payload passed along. Agents. A judgment step goes to an agent instead of a fixed rule. Keep Make for the connections to apps Vyre does not package yet, and keep any scenario that already works.
- Why that helps: Rules decide, not a model. A 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 approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes. Fewer subscriptions and less copy-paste. One Space covers parts of a job that took several tools, so there are fewer logins and fewer places to keep in step.

### Vyre and n8n (https://vyre.run/compare/n8n/)
- What n8n is: Builds workflows with nodes, hosted or on your own server. Technical teams that want a node-based workflow tool they can run themselves.
- What it does well: 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.
- Works with Vyre 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: 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: Data on your own server. Records, files and the history of every decision stay on a server you own. Sealed fields show an agent a placeholder. Rules decide, not a model. A 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 approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes.

### Vyre and Microsoft Power Automate (https://vyre.run/compare/power-automate/)
- What Microsoft Power Automate is: Automates tasks across Microsoft 365 and other services. Teams that live in Microsoft 365 and want flows that react to their mail, files and Teams.
- What it does well: Close to Microsoft 365. Triggers and actions for the Microsoft products a company already runs on. Custom connectors. A service with an API can be added as a connector. Administration in one place. IT can govern it with the rest of the tenant.
- Works with Vyre today: A cloud flow can call a Flow’s path through an HTTP action, and a Flow’s web step can call a flow that starts from an HTTP request. 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.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Flows. Flows start from records and stages in the Space, and a person approves each version. Agents. An agent step handles the judgment a fixed rule cannot. The Gate. Anything that leaves waits for a person’s yes. Keep Power Automate for work that lives inside Microsoft 365. Vyre handles the records, agent work and approvals around it.
- Why that helps: Rules decide, not a model. A 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. One place for people and agents. People 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. Every outward action approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes.

### Vyre and Notion (https://vyre.run/compare/notion/)
- What Notion is: A workspace for notes, documents, databases and tasks. Teams that want pages, wikis and databases in one flexible workspace.
- What it does well: Flexible pages and databases. Notes, wikis and tables share one editor. Easy to shape. People build their own templates and views. Familiar to many people. New teammates often know it already.
- Works with Vyre today: Notion publishes an API for pages and databases. 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.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Records. Records of any type you define, linked in any web, with boards, calendars and dashboards. Tasks and Playbooks. Tasks and Playbooks hold the stages of each kind of job and who does each. Agents. An agent takes a task and works in the project, instead of only answering in a page. Keep Notion for the wiki and long-form writing if your team likes it there. Let Vyre hold the records, tasks and agent work.
- Why that helps: Agents do the work. An 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. One place for people and agents. People 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. Fewer subscriptions and less copy-paste. One Space covers parts of a job that took several tools, so there are fewer logins and fewer places to keep in step.

### Vyre and ClickUp (https://vyre.run/compare/clickup/)
- What ClickUp is: Plans and tracks tasks, docs and goals. Teams that want tasks, docs and dashboards in one configurable tool.
- What it does well: Many views of the same tasks. List, board, calendar and timeline views. Configurable. Statuses, fields and automations can be set to the team’s way of working. Docs beside tasks. Written material sits near the work.
- Works with Vyre today: ClickUp publishes 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Tasks and Playbooks. Tasks assigned to people or agents, and Playbooks for each kind of job. Records. The clients, jobs and cases the tasks are about, linked to them. Flows. Flows do the actions between stages, and a person approves each version. Keep ClickUp if other teams depend on it. A Flow can read or update it where its API allows.
- Why that helps: Agents do the work. An 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. One place for people and agents. People 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. Fewer subscriptions and less copy-paste. One Space covers parts of a job that took several tools, so there are fewer logins and fewer places to keep in step.

### Vyre and Asana (https://vyre.run/compare/asana/)
- What Asana is: Plans projects and tracks who does what by when. Teams that coordinate projects across people and departments.
- What it does well: Clear ownership. Each task has an owner and a due date. Timelines and portfolios. Managers can see work across projects. Rules and forms. Built-in automations and intake forms.
- Works with Vyre today: Asana publishes 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Tasks and Playbooks. Tasks have an owner who is a person or an agent, with Needs you for what is waiting. Records. Clients and projects are records the tasks link to. Flows. Flows move work between stages on stored steps. Keep Asana where several departments already plan in it. Vyre can read it through a Flow and do the work behind each task.
- Why that helps: Agents do the work. An 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. Rules decide, not a model. A 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. One place for people and agents. People 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.

### Vyre and Monday.com (https://vyre.run/compare/monday/)
- What Monday.com is: A visual work platform of boards, dashboards and automations. Teams that run work on colourful boards and want dashboards on top.
- What it does well: Boards that anyone can read. Status columns and views are quick to learn. Dashboards. Charts and summaries across boards. Ready-made templates. Starting points for common kinds of work.
- Works with Vyre today: Monday.com publishes 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Records. Boards by stage, calendars and dashboards over any record type you define. Tasks and Playbooks. Playbooks give each kind of job its stages and owners. Agents. Agents take items and finish them. Keep Monday.com for cross-team boards. A Flow can update it where its API allows.
- Why that helps: One place for people and agents. People 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. Agents do the work. An 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. Fewer subscriptions and less copy-paste. One Space covers parts of a job that took several tools, so there are fewer logins and fewer places to keep in step.

### Vyre and Airtable (https://vyre.run/compare/airtable/)
- What Airtable is: Relational databases with views, forms and automations. Teams that keep structured data in tables and build their own apps on it.
- What it does well: Spreadsheet feel, database power. Linked tables that non-developers can shape. Views and forms. Grid, kanban, calendar and gallery over one table. Interfaces. Custom screens for the people who use the data.
- Works with Vyre today: Airtable publishes a web 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Records. Record types and fields in your own words, linked to each other, with imports from Excel and CSV. Flows. Flows start when a record changes or enters a stage. Agents. Agents read and update the records under a role, with sealed fields kept from them. A team that only keeps lists and boards in Airtable can move them into Records. Keep Airtable for bases other systems depend on.
- Why that helps: One place for people and agents. People 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. Data on your own server. Records, files and the history of every decision stay on a server you own. Sealed fields show an agent a placeholder. Fewer subscriptions and less copy-paste. One Space covers parts of a job that took several tools, so there are fewer logins and fewer places to keep in step.

### Vyre and Trello (https://vyre.run/compare/trello/)
- What Trello is: Kanban boards with cards and lists. Small teams that want a simple board and little setup.
- What it does well: Simple to start. A board and cards, with no setup. Easy to share. Clients and teammates grasp it quickly. Power-Ups. Extra features can be added to a board.
- Works with Vyre today: Trello publishes a REST 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Records. Boards by stage over any record type, with calendars and dashboards. Tasks and Playbooks. Tasks go to a person or an agent and show up under Needs you when stuck. Flows. Flows move a card on when a step finishes. A team that only needs a board can run it in Vyre and drop the seat. Keep Trello for boards shared with people outside your Space.
- Why that helps: Fewer subscriptions and less copy-paste. One Space covers parts of a job that took several tools, so there are fewer logins and fewer places to keep in step. Agents do the work. An 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. One place for people and agents. People 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.

### Vyre and HubSpot (https://vyre.run/compare/hubspot/)
- What HubSpot is: A CRM with marketing, sales and service tools. Teams that run marketing, sales and service from one platform.
- What it does well: One platform for the funnel. Marketing, sales and service data sit together. A large ecosystem. Integrations, partners and training. Reporting. Dashboards across the pipeline.
- Works with Vyre today: HubSpot publishes 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Records. Contacts, organizations and deals as records you shape, with boards by stage. Agents. An agent reads a new enquiry, drafts a reply from your price list and stops for a person. Documents and Signing. Proposals and engagement letters filled from the record. Keep HubSpot for email marketing, forms on the web and ad reporting. Let Vyre do the follow-up work and the approvals around it.
- Why that helps: Agents do the work. An 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 approved. An 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 agents. People 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.

### Vyre and Salesforce (https://vyre.run/compare/salesforce/)
- What Salesforce is: A CRM and platform for sales, service and custom apps. Larger sales and service organisations that build on a configurable platform.
- What it does well: A deep platform. Objects, workflows and apps can be built on it. A broad ecosystem. A large partner and app marketplace. Enterprise administration. Roles, audit and governance for big teams.
- Works with Vyre today: Salesforce publishes REST and other 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Records. Working records and stages for a team that does not need the whole platform. Agents. Agents that prepare the follow-up from a record. Flows. Flows with an approved version for each repeated step. Salesforce is a platform, and Vyre does not replace it for an organisation built on it. Vyre works beside it as the place where agents prepare the work.
- Why that helps: Agents do the work. An 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 approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes. Rules decide, not a model. A 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.

### Vyre and Pipedrive (https://vyre.run/compare/pipedrive/)
- What Pipedrive is: A sales CRM built around the pipeline. Sales teams that want a pipeline of deals and clear next activities.
- What it does well: Pipeline first. Deals move across visible stages. Easy to adopt. Sales teams pick it up quickly. Activity reminders. Next steps stay in front of the rep.
- Works with Vyre today: Pipedrive publishes 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Records. Deals as a record type with boards by stage. Tasks and Playbooks. Follow-up tasks go to a person or an agent. Flows. A Flow acts when a deal enters a stage. A team that uses Pipedrive for a simple pipeline can run it in Vyre. Keep it where your sales process depends on its own features.
- Why that helps: Agents do the work. An 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. Fewer subscriptions and less copy-paste. One 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 approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes.

### Vyre and Zoho CRM (https://vyre.run/compare/zoho-crm/)
- What Zoho CRM is: A CRM from the Zoho suite. Teams that run on Zoho products and want a CRM that fits in the suite.
- What it does well: Part of a suite. It works with other Zoho products. Configurable. Modules, fields and workflows can be changed. Broad feature set. Sales automation, analytics and more.
- Works with Vyre today: Zoho CRM publishes 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Records. Contacts and deals as records you shape, linked to the work. Agents. Agents prepare replies and documents from a record. Flows. Flows with a person’s approval on each version. Keep Zoho for the other products in the suite. Vyre can be extended by integrating your Zoho stack, where the vendor provides an API.
- Why that helps: Agents do the work. An 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 approved. An 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 agents. People 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.

### Vyre and GoHighLevel (https://vyre.run/compare/gohighlevel/)
- What GoHighLevel is: A marketing and CRM platform used by agencies and local businesses. Agencies and small businesses that want funnels, messaging and a CRM in one platform.
- What it does well: Funnels and messaging in one place. Pages, texts, email and calls sit with the contacts. Built for agencies. Accounts can be set up for many clients. Automations. Workflows start from contact events.
- Works with Vyre today: GoHighLevel publishes 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Records. Contacts, opportunities and projects as records you shape. Sites. Sites put a built page online after one yes. Agents. Agents read an enquiry and draft the reply for approval. Keep GoHighLevel for sending texts, phone numbers and marketing funnels, which Vyre does not provide. Vyre can read from it and prepare the work.
- Why that helps: Agents do the work. An 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 approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes. Rules decide, not a model. A 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.

### Vyre and Clio (https://vyre.run/compare/clio/)
- What Clio is: Practice management software for law firms. Law firms that want matters, time, billing and client records in one system.
- What it does well: Built for legal practice. Matters, time entries and billing match how firms work. A system of record. Clients, matters and communications in one place. A large ecosystem. Integrations and partners.
- Works with Vyre today: Clio publishes 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Agents. Agents prepare intake, drafts and reminders from a record. Documents and Signing. Your own Word templates filled from a record, with signing for people who have no account. The Gate. Nothing goes to a client until a person approves the exact words. Vyre does not replace Clio’s billing or its role as the record of the practice. Keep it, and let Vyre do the preparation around it.
- Why that helps: Agents do the work. An 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 approved. An 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 server. Records, files and the history of every decision stay on a server you own. Sealed fields show an agent a placeholder.

### Vyre and MyCase (https://vyre.run/compare/mycase/)
- What MyCase is: Practice management software for law firms. Smaller law firms that want cases, billing and client communication together.
- What it does well: Built for legal practice. Case management, billing and a client portal. One system for the firm. Cases, contacts and communications together. Vendor support. The vendor runs and updates it.
- Works with Vyre today: Check the vendor’s developer documentation for what it offers. Where there is nothing to call, a person can export a list and import the CSV into a Records type, and a custom module can wrap anything that has an endpoint. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Agents. Agents prepare intake, drafts and reminders. Documents and Signing. Documents from your templates, and signing with no account. The Gate. Client messages wait for a person’s yes. Keep MyCase for billing and as the case record. Vyre does the preparation around it.
- Why that helps: Agents do the work. An 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 approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes. Rules decide, not a model. A 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.

### Vyre and PracticePanther (https://vyre.run/compare/practicepanther/)
- What PracticePanther is: Practice management software for law firms. Law firms that want matters, time and billing in a hosted system.
- What it does well: Built for legal work. Matters, time tracking and billing. Hosted for you. The vendor runs and updates it. Integrations. It connects to other products.
- Works with Vyre today: PracticePanther publishes 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Agents. Agents prepare drafts, intake and reminders from a record. Documents and Signing. Your Word templates filled from a record, with signing. Flows. Flows with an approved version for each repeated step. Keep PracticePanther for billing and the matter record. Vyre works with it where its API allows.
- Why that helps: Agents do the work. An 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 approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes. Rules decide, not a model. A 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.

### Vyre and Lawmatics (https://vyre.run/compare/lawmatics/)
- What Lawmatics is: Client intake and marketing automation for law firms. Law firms that want intake, CRM and follow-up automation.
- What it does well: Intake and follow-up. Forms, pipelines and automated outreach for prospects. Built for law firms. Terms and stages match the field. Automation. Workflows from prospect events.
- Works with Vyre today: Lawmatics publishes 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Records. Prospects and matters as records, with boards by stage. Agents. An agent reads a new enquiry and drafts the reply for approval. Flows. Flows react to a new record or stage. Keep Lawmatics for its intake forms and campaigns if the firm relies on them. Vyre can read from it and prepare the work.
- Why that helps: Agents do the work. An 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 approved. An 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 agents. People 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.

### Vyre and Karbon (https://vyre.run/compare/karbon/)
- What Karbon is: Practice management software for accounting firms. Accounting firms that want work, email and team collaboration in one place.
- What it does well: Built for accounting practice. Work items, recurring jobs and team views. Email beside the work. Messages tie to the job they concern. Visibility across the team. Managers see work by person and status.
- Works with Vyre today: Karbon publishes 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Tasks and Playbooks. Playbooks list the stages and tasks of each kind of engagement and who does each. Agents. Agents prepare checklists, requests and summaries. Documents and Signing. Engagement letters filled from a record and sent for signature. Keep Karbon as the practice system. Vyre works with it where its API allows and does the preparation around it.
- Why that helps: Agents do the work. An 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. Rules decide, not a model. A 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 approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes.

### Vyre and TaxDome (https://vyre.run/compare/taxdome/)
- What TaxDome is: Practice management with a client portal for accounting and tax firms. Accounting and tax firms that want a client portal, documents and billing together.
- What it does well: A client portal. Clients upload documents and sign in one place. Built for the field. Workflows and templates for accounting and tax work. Everything in one system. CRM, documents and billing together.
- Works with Vyre today: Check the vendor’s developer documentation for what it offers. Where there is nothing to call, a person can export a list and import the CSV into a Records type, and a custom module can wrap anything that has an endpoint. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Documents and Signing. Your own Word templates filled from a record, with signing for people who have no account. Agents. Agents prepare requests, reminders and summaries. Tasks and Playbooks. Playbooks for each kind of engagement. Keep TaxDome for its client portal and billing. Vyre does the preparation around it.
- Why that helps: Agents do the work. An 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 approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes. Rules decide, not a model. A 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.

### Vyre and Canopy (https://vyre.run/compare/canopy/)
- What Canopy is: Practice management software for tax and accounting firms. Tax and accounting firms that want clients, documents and billing in one system.
- What it does well: Built for tax and accounting. Client management, documents and billing. A client portal. Documents shared and collected in one place. Hosted for you. The vendor runs and updates it.
- Works with Vyre today: Check the vendor’s developer documentation for what it offers. Where there is nothing to call, a person can export a list and import the CSV into a Records type, and a custom module can wrap anything that has an endpoint. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Documents and Signing. Documents from your templates, and signing with no account. Agents. Agents prepare requests, reminders and summaries. Tasks and Playbooks. Playbooks for each kind of engagement. Keep Canopy as the practice system. Vyre does the preparation around it.
- Why that helps: Agents do the work. An 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 approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes. Rules decide, not a model. A 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.

### Vyre and DocuSign (https://vyre.run/compare/docusign/)
- What DocuSign is: Electronic signature and agreement management. Organisations that need signatures with an established legal and compliance footprint.
- What it does well: An established standard. Many counterparties already know it. Signing features. Routing, fields and audit trails for agreements. Wide integrations. It connects to many products.
- Works with Vyre today: DocuSign publishes an eSignature 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Documents and Signing. Vyre fills your own Word template from a record and sends it for signature. The signer needs no account and the signed copy files back on the record. The Gate. Sending is a held act: a person reads the email and says yes once. Records. The signature status lives on the Document record. For routine engagement letters and agreements, Vyre’s signing is enough. Keep DocuSign where a counterparty requires it.
- Why that helps: One place for people and agents. People 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. Every outward action approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes. Fewer subscriptions and less copy-paste. One Space covers parts of a job that took several tools, so there are fewer logins and fewer places to keep in step.

### Vyre and PandaDoc (https://vyre.run/compare/pandadoc/)
- What PandaDoc is: Document creation, proposals and e-signature. Sales and service teams that send proposals and quotes and want them signed.
- What it does well: Proposal templates. Designed documents with content blocks. Signing and tracking. See when a document is opened and signed. CRM connections. It links to common CRMs.
- Works with Vyre today: PandaDoc publishes 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Documents and Signing. Your Word templates filled from a record, with signing for people who have no account. Agents. An agent drafts the covering message from the record. The Gate. The send waits for a person’s yes. Keep PandaDoc if you rely on its designed proposal layouts. Vyre covers template-based documents and signing.
- Why that helps: One place for people and agents. People 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. Every outward action approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes. Fewer subscriptions and less copy-paste. One Space covers parts of a job that took several tools, so there are fewer logins and fewer places to keep in step.

### Vyre and Dropbox Sign (https://vyre.run/compare/dropbox-sign/)
- What Dropbox Sign is: Electronic signatures from Dropbox. Teams that want a simple way to send and sign documents.
- What it does well: Simple to use. Send a document and collect a signature. Part of Dropbox. It sits beside the files many teams already keep there. Templates. Reuse a document for repeated signing.
- Works with Vyre today: Dropbox Sign publishes 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: Documents and Signing. Send a template for signature from a record, with no account needed by the signer. Records. Signed copies file on the record. The Gate. A person approves the send. A team that signs routine documents can use Vyre’s signing instead. Keep Dropbox Sign where a counterparty asks for it.
- Why that helps: Fewer subscriptions and less copy-paste. One Space covers parts of a job that took several tools, so there are fewer logins and fewer places to keep in step. One place for people and agents. People 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. Every outward action approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes.

### Vyre and 1Password (https://vyre.run/compare/1password/)
- What 1Password is: A password manager for people, families and businesses. People and companies that want every login in a manager with browser and phone apps.
- What it does well: Apps everywhere. Browser extensions and apps on every device. Sharing and vaults. Teams share logins by vault. Developer tools. A command line and secrets tooling for builders.
- Works with Vyre today: 1Password publishes developer tools for reading secrets. 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.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Vault. The Vault seals passwords, keys, tokens and cards, and hands them to an agent or Flow as use only, so a model never reads the value. The Gate. A held send that uses a Vault credential waits for a yes. Vyre’s Vault is built for the credentials your agents and Flows use. Keep 1Password for the logins your people fill in on the web every day.
- Why that helps: Data on your own server. Records, files and the history of every decision stay on a server you own. Sealed fields show an agent a placeholder. Every outward action approved. An 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 agents. People 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.

### Vyre and Bitwarden (https://vyre.run/compare/bitwarden/)
- What Bitwarden is: An open-source password manager. People and teams that want a password manager they can self-host.
- What it does well: 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.
- Works with Vyre 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: 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: Data on your own server. Records, files and the history of every decision stay on a server you own. Sealed fields show an agent a placeholder. Every outward action approved. An 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 agents. People 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.

### Vyre and ChatGPT for teams (https://vyre.run/compare/chatgpt-team/)
- What ChatGPT for teams is: A shared ChatGPT workspace for a team. Teams that want OpenAI’s assistant with shared workspace controls.
- What it does well: OpenAI’s models and features. The people who build the model build the assistant. Nothing to run. Sign up and invite the team. Polished apps. Web, desktop and phone.
- Works with Vyre today: OpenAI publishes an API, and Vyre runs Codex through your own sign-in or key. 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.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Chat. Chats where people and agents from any model take part together. Agents. Agents with a role and a reach, taking tasks. Records. The records, tasks and files the chat is about, in the same Space. Keep ChatGPT for thinking and drafting if your team likes it. Vyre uses your own accounts as models and is where the work happens.
- Why that helps: One place for people and agents. People 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. Agents do the work. An 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 approved. An 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 server. Records, files and the history of every decision stay on a server you own. Sealed fields show an agent a placeholder.

### Vyre and Claude for teams (https://vyre.run/compare/claude-teams/)
- What Claude for teams is: A shared Claude workspace for a team. Teams that want Anthropic’s assistant with shared projects and admin controls.
- What it does well: Anthropic’s models and features. The people who build the model build the assistant. Nothing to run. Sign up and invite the team. Projects and connectors. Shared context and connections to common apps.
- Works with Vyre today: Anthropic publishes an API, and Vyre works with Claude through your own accounts or keys. 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.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Chat. Chats where people and agents from any model take part together. Agents. Agents with a role and a reach, taking tasks. Records. The records, tasks and files the chat is about, in the same Space. Vyre runs Claude through your own accounts. Keep the Claude workspace for individual thinking and let Vyre hold the team’s shared work.
- Why that helps: One place for people and agents. People 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. Agents do the work. An 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 approved. An 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 server. Records, files and the history of every decision stay on a server you own. Sealed fields show an agent a placeholder.

### Vyre and Microsoft Copilot (https://vyre.run/compare/copilot/)
- What Microsoft Copilot is: An AI assistant built into Microsoft 365. Organisations that live in Microsoft 365 and want an assistant inside Word, Outlook and Teams.
- What it does well: Inside the tools people use. It works in the Microsoft apps they already have open. Tenant administration. IT governs it with the rest of Microsoft 365. Microsoft Graph data. It can use the mail, files and calendar a tenant holds.
- Works with Vyre today: Microsoft publishes extensibility options for Copilot and APIs through Microsoft Graph. 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.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Agents. Agents with a role and a reach that take tasks and finish them. Records. Records, tasks and files in a Space you own. Flows. Flows with a person’s approval on each version. Vyre does not replace Copilot in Word, Outlook or Teams. Use Copilot there and Vyre for the work that spans people, records and approvals.
- Why that helps: One place for people and agents. People 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. Every outward action approved. An 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 server. Records, files and the history of every decision stay on a server you own. Sealed fields show an agent a placeholder.

### Vyre and Webflow (https://vyre.run/compare/webflow/)
- What Webflow is: A visual website builder and host. Designers and marketing teams that want to build and publish custom sites visually.
- What it does well: 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.
- Works with Vyre 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: 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: Agents do the work. An 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 approved. An 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 server. Records, files and the history of every decision stay on a server you own. Sealed fields show an agent a placeholder.

### Vyre and Squarespace (https://vyre.run/compare/squarespace/)
- What Squarespace is: A website builder with hosting and templates. Small businesses and individuals who want a good-looking site without code.
- What it does well: Templates with good design. A site looks finished quickly. Everything included. Hosting, domain options and commerce. Simple editing. No code needed.
- Works with Vyre today: Check the vendor’s developer documentation for what it offers. Where there is nothing to call, a person can export a list and import the CSV into a Records type, and a custom module can wrap anything that has an endpoint. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: 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 Squarespace if the editor suits your team. Vyre fits a site built as files and published from your Space.
- Why that helps: Fewer subscriptions and less copy-paste. One 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 approved. An 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 work. An 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.

### Vyre and Wix (https://vyre.run/compare/wix/)
- What Wix is: A website builder with hosting. Small businesses and individuals who want to build a site with an editor and add features from an app market.
- What it does well: An editor for everyone. Drag-and-drop editing. An app market. Add features without code. Hosting included. The vendor serves the site.
- Works with Vyre 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre replaces it: 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: Fewer subscriptions and less copy-paste. One 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 approved. An 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 work. An 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.

### Vyre and RingCentral (https://vyre.run/compare/ringcentral/)
- What RingCentral is: Phone, messaging and video for business. Businesses that run their phone lines, messages and meetings on one communications platform.
- What it does well: A business phone system. Numbers, extensions and call handling. Messaging and video together. One platform for calls, chat and meetings. Carrier-grade service. Run by the vendor.
- Works with Vyre today: RingCentral publishes a developer 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Records. A Flow can turn what comes from RingCentral into a record, where its API allows. Agents. An agent can prepare the follow-up from it. The Gate. The reply waits for a person’s yes. Vyre does not replace a phone system, and it does not carry calls. Keep RingCentral for telephony and connect it where its API allows.
- Why that helps: One place for people and agents. People 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. Agents do the work. An 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 approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes.

### Vyre and Slack (https://vyre.run/compare/slack/)
- What Slack is: Team messaging in channels and threads. Companies that run daily conversation in channels and want apps close to it.
- What it does well: Where many teams already talk. Channels, threads and huddles. A large app directory. Many products post into Slack. Search across conversations. History is easy to find.
- Works with Vyre today: Slack publishes a Web API and incoming webhooks. 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.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Chat. Chats between people and agents in a Space, with a Needs you chip when one waits. Tasks and Playbooks. Tasks go to a person or an agent and appear under Needs you when stuck. Records. The chat sits beside the records it is about. Keep Slack for company-wide conversation. Vyre’s chat is for work with agents on records and tasks. A Flow can post to Slack where its API allows.
- Why that helps: One place for people and agents. People 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. Agents do the work. An 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 approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes.

### Vyre and QuickBooks (https://vyre.run/compare/quickbooks/)
- What QuickBooks is: Accounting software for small businesses. Small businesses that want bookkeeping, invoicing and reports.
- What it does well: Standard in bookkeeping. Many accountants and tools support it. Invoicing and reports. Core small-business accounting. A large ecosystem. Apps connect to it.
- Works with Vyre today: Intuit publishes an API for QuickBooks Online. 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.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Records. Clients and engagements as records, with the data a bill needs. Agents. Agents prepare an invoice request or a reminder from the record. The Gate. A payment or a send waits for a person’s yes. Vyre does not replace your accounting ledger. Keep QuickBooks as the books, and have Vyre prepare what goes into it.
- Why that helps: Agents do the work. An 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 approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes. Rules decide, not a model. A 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.

### Vyre and Xero (https://vyre.run/compare/xero/)
- What Xero is: Cloud accounting software for small businesses. Small businesses and their advisers that want online bookkeeping and invoicing.
- What it does well: Online accounting. Bank feeds, invoicing and reports. Adviser access. Accountants work in the same books. An app marketplace. Other tools connect to it.
- Works with Vyre today: Xero publishes 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. Coming in 0.7: a packaged Integration, so the Connection and its operations arrive ready-made.
- Where Vyre fits: Records. Clients and engagements as records, with the data a bill needs. Agents. Agents prepare an invoice request or a reminder from the record. The Gate. A payment or a send waits for a person’s yes. Vyre does not replace your accounting ledger. Keep Xero as the books, and have Vyre prepare what goes into it.
- Why that helps: Agents do the work. An 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 approved. An email, a payment, a deletion or a published page waits at the Gate until a person has read the exact words and said yes. Rules decide, not a model. A 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.

## Direction (not a promise of dates)
- Now, 0.5: the features above.
- Next, 0.6: one chat per Flow, deadlines on agent steps, a failure panel on every step, per-record privacy for custom record types, Flow email with CC, BCC and attachments, an audit screen for admins.
- After that, 0.7: Integrations (Clio, Lawmatics, GoHighLevel and DecisionVault are planned), a Skills screen and a Plugins screen.
- Later: Screen Share (watch and take over your agents' computers and Chrome, on every device).
- Later: a Vyre-hosted home for people without a server.

## Map your business onto Vyre
To see how a business would run on Vyre, give this prompt to your AI agent (ChatGPT, Claude or any agent that can read links). It sends the agent to https://vyre.run/agenthome.md, which holds the full instructions: what Vyre is, a map of the site and docs, the questions to ask, the mapping method and how to get started. https://vyre.run/map/ has a five-step guide that draws your business on Vyre and adds its details to the prompt, and the repository has it as docs/for-agents/PROMPT.md.

```
Read https://vyre.run/agenthome.md and follow it to show me how my business would run on Vyre. Ask me what you need.
```

## FAQ
### Is Vyre free?
Yes. Vyre is open source under Apache 2.0. You use your own Claude, Codex, Grok or OpenRouter account, so you pay those providers directly and nobody pays Vyre.

### Do I need a server?
Yes, one machine that stays on: a Linux server with Docker, or a Mac that stays on. Your Mac, your Windows PC and your phone connect to it. Your agents keep working when your laptop is closed.

### Does it run on Windows?
Yes, as an app on your PC with a tray icon and an Alt+Space panel. The server itself runs on Linux or on a Mac that stays on. The Windows app is not code-signed yet, so Windows asks you to choose “More info”, then “Run anyway”.

### Does it work on my phone?
Yes, on Android and iPhone. You install the Vyre app from a file (it is not on a store yet), then open Vyre on the phone and sign in with the Space, your username and your password, or Continue with GitHub.

### Where does my data live?
Records, chats, files and the vault stay on your server and your computers. vyre.run holds your name’s DNS record and runs the relay, which carries phone pairing, end-to-end encrypted. Prompts go to your AI provider the way they would from that provider’s own app.

### Do I need a VPN or another network app?
No. Vyre has its own private network built in, so your server, your computers and your phone find each other with nothing to install and nothing to sign in to. Where a direct path is not possible, Vyre’s relay carries the connection, end-to-end encrypted.

### Does it replace Claude Code, Codex or Grok?
No. Vyre runs them with your own accounts and adds records, Flows, a vault, agents with roles and one chat that outlives any one model. You keep using each tool the way you do.

### What stops an agent from doing something I did not ask for?
Anything that leaves your server, such as an email, a payment, a deletion or a published page, waits at the Gate until a person has read the exact words and approved them. An agent can ask and cannot approve. A model sees a placeholder where a secret would be. The architecture page shows how.

### Who is Vyre for?
Professional services teams that want people and agents to work in one place: the people set the direction and make the calls, and the agents draft, track and follow up. Point your AI agent at the repo and it can show how your business would run on Vyre.

### Is it ready?
It is 0.5.1, and what this page shows works today. What comes next is labelled with its version on the direction page and in the roadmap.