Plan locally. Share only when you choose.

Start a roadmap

Choose Blank roadmap for one empty Planning phase, or Starter example for three phases and nine tasks that demonstrate progress, focus, and dependencies. Everything is editable.

Local roadmaps are stored in browser local storage and work offline. Clearing site data or changing browsers can remove them, so keep a JSON backup of anything important.

Create phases and tasks

Add phases from the roadmap toolbar. Add tasks inside each phase, then use task details for descriptions, estimates, assignees, tags, dependencies, and links.

RoadForge can highlight one or more Recommended tasks. Recommendations are guidance, not a decision about what you must do next. Dependencies mark work as blocked until its prerequisites are done. Search and filters only change the current view; they never remove roadmap data.

Import and export

Open Import / Export from the workspace header. JSON is the portable backup format and can be imported again. Markdown is a readable snapshot for people and agents.

RoadForge validates an import and shows a preview before changing anything. You can create a separate local roadmap, add safe new items, or replace the current roadmap. Session tokens, invite credentials, passwords, and edit locks are never exported.

Save and share

Save creates a server-backed copy and enables sharing. On `roadforge.anvilary.tools`, that server is the public hosted demo. Owner and editor links are credentials, so send them privately. Viewer links are read-only.

• Owner: edit, restore versions, manage links and participants, and override claims.
• Editor: edit roadmap content and claim tasks.
• Viewer: read the roadmap and activity without changing anything.

An edit lock prevents two people from changing the same control at once. A task claim communicates who is working on a task; it does not assign permanent ownership.

Use the demo or self-host

The Anvilary-hosted RoadForge instance is for evaluation, examples, and light collaboration. It is not a managed team SaaS, durable backup service, or large-team production service. It has no hosted SLA, reserved per-team capacity, or guaranteed data-recovery service.

If RoadForge becomes part of your team's operating workflow—especially for a larger team or long-running roadmap—fork the repository or maintain a controlled clone and self-host it. Your operator should own PostgreSQL backups and restores, retention, monitoring, capacity, upgrades, security configuration, and incident response. Load-test the expected concurrency before depending on the deployment.

Forking and self-hosting remain subject to the repository's current PolyForm Noncommercial License 1.0.0; the current license does not grant commercial use.

Resolve save and conflict states

Saving means a request is in progress,Synced means the server accepted it, andOffline means RoadForge could not reach the server. Your browser copy remains available.

A conflict means somebody saved a newer version first. Review the differences, then choose whether to keep your local version or load the server version. Loading the server version discards the local draft only after confirmation.

Use activity and versions

Activity shows meaningful actions on a shared roadmap. Versions are explicit restore points. Owners and editors can inspect them; only owners can restore one. A restore creates a new restore point rather than deleting later history.

Troubleshoot safely

• If a local roadmap is missing, open the roadmap switcher and check whether browser site data was cleared.
• If sync is offline, keep working locally and retry after the server is reachable.
• If a session expired or was revoked, keep the local copy and rejoin through a current invite link.
• If an import fails, leave the original file unchanged and use the validation message to repair a copy.
• If a self-hosted team instance is slow or unstable, inspect resource/database/Redis/proxy metrics before adding workers blindly.

Need help? Report a problem. Do not include invite links, tokens, private roadmap exports, secrets, or private logs in a public issue.

Known limitations

• Browser storage is not a substitute for an exported backup.
• The public hosted instance is a demo/reference deployment with no uptime, capacity, or recovery SLA.
• RoadForge does not publish an arbitrary large-team concurrency guarantee; self-hosters must validate their expected load.
• Markdown is presentation-only and PDF export is not available.
• Conflicts require a deliberate choice; RoadForge does not silently merge competing edits.
• Accountless sharing identifies access credentials and display names, not verified personal identities.