Product overview

Mayvor is local-first project management for people building with coding agents — Desktop for local work, Cloud for optional team visibility.

Make Your Vision Real

Mayvor is a coined name inspired by Make Your Vision Real, pronounced MAY-vah (IPA: /ˈmeɪ.və/). Its mission is to help builders move from ideas to outcomes: Vision → Plan → Action → Progress → Reality. The current product connects project planning, tasks, steps, and agent-assisted execution. These stages describe a working philosophy rather than five separate modules.

The mission leaves room for the product to evolve beyond project management; no additional products are announced here. See About Mayvor, local-first architecture, and migration from Peacae PM.

Agents already plan and ship work. Traditional tools ask humans to re-enter that into tickets. Mayvor removes the duplicate entry: the agent writes progress once, onto the project board.

Who does what

Actor	Role
Developer	Directs goals, reviews work, unblocks decisions
Coding agent	Plans, codes, updates the project board
Mayvor Desktop	Watches one or many projects, shows board / timeline / sync
Mayvor Cloud	Optional accounts, shared dashboard, invites, org-wide activity, plus the public site (docs, FAQ, blog, changelog, contact)

Rule: agents never call Mayvor APIs or Cloud. Their only write surface is the project board in the repo they are working in.

Working process

Each session, in this order — it matches how work actually moves:

1. Launch the local desktop app so Desktop is already watching the board
2. Launch or open your IDE so you and the coding agent can work in that repo
3. Connect with Cloud for sync when you want the team to see the same board

Desktop is the watcher and sync client. The IDE is where the agent writes the board. Cloud is optional and last: skip it for solo or offline work. Details: How it works.

Principles

1. Developer directs; agent executes
2. Capture from the board — don’t interrupt with a separate ticket ritual
3. One write contract: the project board
4. Local-first; Cloud is optional
5. Status comes from timestamps the agent writes — not invented dashboards

Where to look on Cloud

Need	Where
How setup / Desktop / Cloud fit	How it works (working process + happy path), FAQ
Setup questions	FAQ (search + topic filters) or Contact
What shipped	Changelog, Blog
Team visibility after sync	Sign in → Cloud dashboard (Home, board, org Orchestrator)

What it is not

• Not a replacement for your IDE or agent
• Not a Git commit parser
• Not tied to one AI vendor