Who each is for
Work management
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.
Vyre
Vyre is for a team whose work is partly done by AI agents, and that wants those agents to take tasks the way a colleague does.
It also keeps the records the work is about, such as clients, jobs and cases, linked to the tasks.
What they do well.
Where work management are strong.
- Views people already knowBoards, lists, calendars and timelines, refined over many years.
- Templates and a familiar interfaceA new teammate or an outside client often knows the tool already.
- Docs and wikis next to tasksNotion in particular puts pages, databases and notes in one workspace.
- Reporting dashboardsPortfolio and workload views for managers.
- A large ecosystemIntegrations, templates and a community of people who can help.
Where Vyre is different.
Six things Vyre does its own way.
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.
Side by side.
The two approaches, row by row.
The left column describes the kind of tool, from its public documentation. Where a product differs, its own documentation is the one to trust.
| Question | Work management | Vyre |
|---|---|---|
| Where it runs | Hosted by the vendor. | On a server you own. |
| Unit of work | Tasks, items, pages and databases. | Tasks, plus records of any type you define, linked to each other. |
| Who does the work | People. Most of these tools now include AI features that help inside the tool. | People and agents, both as members. An agent takes a task, then finishes, hands on or marks it stuck. |
| Process | Project and board templates. | Playbooks: stages, tasks and who does each. An owner approves one before it goes live. |
| Automation | Built-in rules and automations. | Flows: stored steps, a person approves each version, every run follows it. |
| Views | Boards, lists, calendars, timelines and dashboards. | Boards by stage, calendars by date and dashboards over any record type. |
| Documents | Pages and docs inside the tool. | Your own Word templates filled from records, with signing for people who have no account. |
| Outward actions | Set by how each automation is built. | Held at the Gate until a person approves the exact words. |
| Sensitive fields | The tool’s own permission settings. | Sealed fields show an agent a placeholder, and fields can be hidden from named roles. |
How they work together.
Use both, and let each do its part.
- 01The board your team usesA task or status changes in the planning tool
- 02A Vyre Flow reads itThrough a connection and a web step, where the vendor provides an API
- 03An agent does the taskIt works in the project and hands the task on or marks it stuck
- 04A person approves the sendThe result goes out once the Gate has a yes
One way to combine them. The board stays where your team already looks.
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.
One page for each product
Questions people ask
Can an agent take a task in Vyre?
Yes. When a task is given to an agent, by a person, by a Flow or by another agent, the agent starts with the task, its record and where it came from. It finishes the task, hands it on, or marks it stuck with a reason, and a stuck task appears under Needs you.
Does Vyre import from the tools on this page?
Excel or CSV imports into any list from the web app. A connection or a custom module can reach a planning tool that has an API. Packaged Integrations are Next, in 0.5.2.