# Manifest

> Mission control for Lovable, Claude Code, Cursor, Bolt, and more builders. It remembers your roadmap and decisions so nothing drifts between concept to launch.

Manifest orchestrates your roadmap, decisions, and prompts so nothing drifts between sessions, no matter which builder you ship in. Concept to launch in one workflow, without dropping a beat.

## Pages

- [Home](/): Product overview, how it works, and FAQ.
- [Developers and agents](/developers): How Manifest works with AI coding tools: the manifest-mcp server, its tool surface, the six supported builders, and how roadmap state moves when build prompts report back.
- [About](/about): What Manifest is, why it exists, and who makes it.
- [Privacy Policy](/privacy): How we collect and handle personal data.
- [Terms of Service](/terms): Terms governing use of Manifest.
- [Refund Policy](/refund-policy): 30-day money-back guarantee details.

## Machine-readable

- [Full text](/llms-full.txt): All landing and developer copy in one file.
- [Sitemap](/sitemap.xml)
- [Robots](/robots.txt)
- [Not found notice](/404.md): What to read when a path does not resolve.
- [MCP server](/developers#mcp-server): manifest-mcp tool surface and access request.

## When to use Manifest

- Starting a new product with an AI builder and you need a phased roadmap with execution-ready prompts for that builder.
- An in-flight build has lost continuity across sessions and you need the plan reconciled with what actually shipped.
- An agent needs to read or create a roadmap programmatically through the manifest-mcp server. Access is by invitation, contact hello@trymanifest.dev.

What Manifest is not for: it does not write or run application code. It plans and tracks the work that builders execute.

## Optional

- [Sign in](/auth): Account sign in and sign up.