Local-first workspaces

Roadmap Flow keeps your roadmap on your computer. This page explains what that means and why it is a deliberate choice.

What "local-first" means here

When you open Roadmap Flow on the desktop, you pick a workspace folder on your machine. Your roadmaps, items, workstreams, teams, and settings are saved there as a single roadmap.json file. There is no account, no cloud sync, and no server holding your data.

Your roadmap leaves your machine only when you choose to move it — by exporting a file or sharing a transfer package. Until then it is yours alone.

Why it works this way

  • Privacy. An early roadmap is sensitive. It should not sit on a vendor's server before you are ready to show it.
  • No subscription to read your own data. Even with no paid plan, you can always open and edit your roadmap.
  • It works offline. No connection required.

How your data is protected

Every time Roadmap Flow saves, it writes carefully: it saves to a temporary file, checks the contents are valid, and only then replaces the real file. It also keeps three rolling backups next to your workspace file.

If the workspace file is ever damaged, Roadmap Flow does not silently overwrite it — it offers to restore. See Workspace recovery.

The trade-off

Local-first means there is no automatic multi-device sync and no real-time co-editing. If you work across two computers, move the roadmap yourself with a roadmap transfer package or a workspace backup. If two people need the same roadmap, one person owns the file and shares updates.

Related guide pages

Free Updated in 0.1.1

← Back to the Field Guide