Questions about VibeMap
What VibeMap does, what it costs, where your data goes, and how a spec reaches the coding agent that builds it. 38 answers, no sales pitch.
The basics
What VibeMap is, who it's for, and what you get out of it.
- What is VibeMap?
- VibeMap is an AI spec generator for spec-driven development. You describe an app idea in plain English, and VibeMap generates a linked product spec: personas, features, user stories, Gherkin-style acceptance criteria, a page inventory, and a relational database schema, with every artifact traced back to the one that justified it. A first pass takes about 30 minutes and needs no product management experience. AI coding tools such as Cursor and Claude Code then read the spec through the VibeMap MCP server and build against it. On Pro and above, the App Builder can also compile the spec into a running app pushed to your own GitHub repo.
- How does VibeMap relate to spec-driven development?
- Spec-driven development is a way of building software where a structured specification, not the prompt history or the code, is the source of truth an AI coding agent builds from. VibeMap writes that specification for you. Instead of drafting markdown specs by hand, you describe the product and VibeMap generates linked personas, user stories, acceptance criteria, pages, and schema, then keeps them consistent as you change them. The full definition is at vibemap.ai/blog/spec-driven-development, and how VibeMap runs the workflow end to end is at vibemap.ai/ai-product-planning.
- How long does it take to get a first spec?
- A complete first pass in VibeMap takes 10 to 30 minutes. You sign in, click New Project, and describe the product in plain English. VibeMap asks a few clarifying questions about target users, technical stack, and constraints, then runs a multi-step pipeline that produces the blueprint: personas, features, user stories, acceptance criteria, pages, and schema. Artifacts stream in as they are generated, so you can read the personas while the stories are still being written. Refining the result through the conversational agent typically takes another 15 to 30 minutes.
- Do I need product management experience to use VibeMap?
- No. VibeMap is built for solo founders, indie hackers, and engineers who have never written a PRD. You describe the product in your own words; VibeMap supplies the structure — user stories in As a / I want to / so that form, Given/When/Then acceptance criteria, priority and effort estimates, a normalised schema — that a trained product manager would otherwise have to author by hand. The structure is applied for you, so you review rather than write. Experienced PMs use VibeMap differently: as a fast first draft they then edit, rather than as a tutor.
- What exactly does VibeMap generate?
- VibeMap generates seven linked artifacts: a project summary, user personas with goals and pain points, a feature list with priority, business value, and effort sizing, user stories in As a / I want to / so that form with story-point estimates, Given/When/Then acceptance criteria categorised as happy path, edge case, or error scenario, a page inventory with routes and a section-by-section breakdown, and a relational database schema. The artifacts are linked rather than merely adjacent — every story traces to the persona it serves, every acceptance criterion to its story, every schema table to the pages that read it.
How it compares
Where VibeMap sits relative to AI app builders, coding agents, and PRD generators.
- How is VibeMap different from Lovable, Bolt, or Base44?
- Lovable, Bolt, and Base44 generate working prototypes directly from a prompt. VibeMap starts upstream: it produces the linked specification — personas, user stories, acceptance criteria, pages, and schema — that those tools or your own AI coding agent build from. On Pro and above, the VibeMap App Builder can also compile that spec into a running Next.js and Supabase app pushed to your own GitHub repo, so the code starts from a reviewed spec rather than a prompt. The practical difference shows up in month two: a prototype built from a prompt has no artifact explaining why it works the way it does, while a VibeMap spec does. Detailed comparisons are at vibemap.ai/alternatives.
- Does VibeMap write the code?
- It can, two ways, and you choose. By default VibeMap writes the specification and your own AI coding agent writes the code: Cursor, Claude Code, or Windsurf read the spec through the VibeMap MCP server and build one acceptance criterion at a time in your own repo, while VibeMap tracks progress on its kanban board. On Pro and above, the VibeMap App Builder writes the code itself: it compiles the spec into a running Next.js and Supabase app, with database migrations, row-level-security policies, auth, and CRUD actions, type-checks and repairs the result, then pushes it to your own GitHub repo and deploys it on Vercel. Either way, the code lives in your repo and belongs to you.
- How is this different from asking ChatGPT to write a PRD?
- ChatGPT produces a document; VibeMap produces a linked data model. A chat transcript cannot tell you which user stories go stale when you change a feature, cannot be queried by your coding agent over MCP, and has to be re-pasted into every new conversation. In VibeMap each artifact is a row with real relationships, so editing a feature flags the user stories and acceptance criteria that were written from it. VibeMap also produces the same structure every time — persona-linked user stories, Given/When/Then criteria, prioritised features — rather than whatever format the model happened to reach for.
- Why not just use a PRD template or GitHub Spec Kit?
- A template tells you what sections to fill in; it does not fill them in, and it does not keep them consistent with each other. GitHub Spec Kit is closer — it is a structured, spec-driven workflow for coding agents — but it lives in your repository as markdown you author and maintain by hand. VibeMap generates the content, keeps the cross-references live, and exposes the result over MCP and a REST API so an agent can read and write it directly. Template-based workflows and VibeMap are not mutually exclusive; VibeMap removes the authoring cost.
AI coding agents
MCP, your IDE, and how the spec reaches the agent actually writing code.
- Does VibeMap work with AI coding tools like Cursor and Claude Code?
- Yes. VibeMap publishes an MCP server (@vibemap.ai/mcp-server on npm) that connects your spec directly to MCP-compatible agents like Cursor, Claude Code, and Windsurf. The agent reads personas, user stories, acceptance criteria, and database schema straight from your VibeMap project — no copy-pasting context into prompts. This keeps the agent grounded in one source of truth while it builds. MCP access is open on every VibeMap plan, including Free.
- How hard is it to connect my IDE to VibeMap?
- It is a config paste, not an integration project. In VibeMap, open Account → Developer and generate a personal access token (prefixed vm_), then open Account → MCP, pick your IDE — Claude Desktop, Cursor, or Windsurf — and copy the ready-made JSON config it assembles for you. Paste that into your IDE's MCP settings and substitute your token. The same screen shows IDE Connection Status, listing each key and when it last authenticated, which is the fastest way to confirm the connection actually worked.
- Does using my own coding agent spend my VibeMap tokens?
- No. VibeMap's token budget meters only VibeMap's own generations. If you author your spec with your own connected agent over MCP — your IDE agent writing personas, features, stories, criteria, pages, and schema straight into the project — that work runs on your agent's tokens and VibeMap only stores the result. The rule in one line: you are billed when VibeMap generates, and anything your own agent authors is free. This is how users on smaller plans stretch a budget a long way.
- Can my agent write back into the spec, or only read it?
- Both. The VibeMap MCP server and REST API are two front doors onto the same surface, sharing one auth model, and that surface supports writes as well as reads. Your agent can create and update personas, features, user stories, acceptance criteria, pages, and schema tables in your project. Plan gates still apply per entity — authoring pages or schema over MCP needs Starter, exactly as it does in the browser — but the access itself is not what varies between plans.
- How does VibeMap help an agent build test-first?
- VibeMap's acceptance criteria are written as discrete, Gherkin-style Given/When/Then statements, each tagged with a scope (front-end, back-end, or full-stack) and linked to its user story and persona. Over MCP, an agent can claim a single acceptance criterion, implement exactly that behaviour, and submit it for review, rather than being handed a whole feature and improvising the boundaries. Narrower, pre-scoped work is the practical defence against the duplicated components and conflicting files that unplanned AI codebases accumulate.
Spec quality and control
What the output actually looks like, and what happens when the AI gets it wrong.
- How detailed are the user stories and acceptance criteria?
- VibeMap writes each user story in As a / I want to / so that form, linked to a named persona and a specific feature, with a priority and a story-point estimate on the Fibonacci scale. Acceptance criteria are written as separate Given, When, and Then fields and categorised as happy path, edge case, or error scenario, and every story gets at least one. This level of detail means QA engineers and AI coding tools like Cursor or Claude Code can consume the output directly without manual clarification or rewriting.
- What if VibeMap gets something wrong or invents a detail?
- Treat the first pass as a draft, not an oracle. Every artifact VibeMap generates is editable, and the conversational agent lets you correct anything in plain language rather than by hand. VibeMap is designed so mistakes are cheap to catch: artifacts are short, linked, and reviewable in minutes, which is the opposite of discovering a bad assumption after an AI coding agent has built three features on top of it. Nothing is rewritten silently — when you change a feature or story, VibeMap flags what was written from it and you approve each proposed rewrite.
- Can I edit the user stories and acceptance criteria that VibeMap generates?
- Yes. Every artifact VibeMap generates is editable. Users can rewrite, reorder, or extend user stories, acceptance criteria, personas, and schema fields directly in the VibeMap interface. When a feature or user story changes in a way that matters, VibeMap marks the stories and acceptance criteria written from it as stale and offers a reconcile step that proposes updated wording for each one, which you accept or reject item by item. A conversational agent lets users refine artifacts through natural-language dialogue.
- How does VibeMap handle changes to existing work items?
- VibeMap tracks which artifacts were written from which. When you change a feature's name, description, or business value, or a story's wording or user role, VibeMap marks the user stories and acceptance criteria written from it as stale and shows exactly which fields changed upstream. Nothing is rewritten silently: a reconcile step proposes updated wording for each stale item, and you accept or reject them one at a time. Status, priority, and effort changes never mark anything stale, because nothing downstream was derived from them.
- How does VibeMap identify user roles and personas?
- VibeMap generates distinct user personas for every project — three by default — each with demographics, goals, pain points, motivations, and a representative quote. Every user story VibeMap generates is linked to the persona it serves, and every acceptance criterion and page traces back through those stories, so teams can see which journeys each persona has and which are missing. Personas are editable — users can rewrite, rename, or add personas at any point.
- How does VibeMap prioritize features and user stories?
- VibeMap gives every feature a priority (high, medium, or low), a business-value and complexity rating, and an effort size from XS to XL; every user story gets its own priority and a story-point estimate on the Fibonacci scale, from 1 to 13. You can change any of these on the item itself. On Pro and above, the VibeMap sprint planner goes further: it works out which acceptance criteria depend on which, then orders them into themed sprints so prerequisite work comes first.
- How does VibeMap categorize acceptance criteria?
- VibeMap categorizes every acceptance criterion into one of three types: happy path (the expected successful flow), edge case (boundary conditions and unusual but valid inputs), and error scenario (invalid input, permission denied, conflicts, and other failures). Each criterion is written as separate Given, When, and Then fields and linked to the user story it verifies, so an AI coding agent can claim and build one scenario at a time over MCP.
- What are tags in VibeMap and how do they work?
- VibeMap does not use free-form tags. Instead, every acceptance criterion carries structured fields: a scenario category (happy path, edge case, or error scenario), a link to its user story and through it to a persona and feature, a sprint once the sprint planner has run, and a build status on the kanban board. Those fields are what an AI coding agent works from over MCP — for example, asking VibeMap for the next criterion that is ready to build.
- How does VibeMap organize pages and components for my application?
- VibeMap generates a complete page inventory from the user stories. Each page includes its route, its purpose, the personas it serves, and a section-by-section breakdown, and VibeMap generates working UI code for every section that you can preview live in the browser. The page inventory feeds directly into downstream tools: your coding agent reads it over MCP, and the generated pages download as a Next.js project ZIP you can open in any editor.
- Can VibeMap help with technical requirements, compliance, and performance constraints?
- Yes. VibeMap captures technical requirements through a structured conversation during project setup. As users describe their product, VibeMap asks targeted clarifying questions covering technology stack preferences, compliance requirements such as GDPR or HIPAA, performance targets, and scalability constraints. These answers are embedded into the generated acceptance criteria and database schema so engineers receive a specification that already accounts for non-functional requirements, not just feature behavior.
- Which AI models does VibeMap use?
- VibeMap is multi-provider by design and routes each step to a model suited to it, drawing on Anthropic, OpenAI, and Google. Routine steps such as the summary, features, and user stories run on fast economy models; heavier steps such as pages and the database schema run on stronger models. Your plan sets how capable a model VibeMap may pick: Free uses economy models, Starter adds standard models, and Pro and Team add premium models such as GPT-5 and Claude 4.5 Sonnet. Model choice is automatic on every plan, and VibeMap is never hard-wired to a single provider.
- Does VibeMap remember project context across sessions?
- Yes. VibeMap persists every project decision, artifact, and conversational exchange. Users can close the browser and return weeks later; the project state, pipeline progress, and conversation history are preserved. Projects can be shared with teammates on the Team plan, with role-based access so engineers, PMs, and designers can collaborate on the same blueprint.
Pricing and tokens
What it costs, how the token budget works, and what happens when you run out.
- How much does VibeMap cost, and is there a free plan?
- VibeMap has five tiers, billed monthly or yearly: Free at $0, Starter at $19 a month or $182/yr, Pro at $49 or $470/yr, Team at $79 or $758/yr, and Enterprise at $199 or $1,910/yr. Every paid plan has a 14-day free trial on monthly billing: card required, nothing to pay if you cancel before day 14. Yearly costs about 20% less; promo codes apply to monthly plans only. The Free plan needs no credit card and covers one project with the core pipeline — summary, personas, features, user stories, and acceptance criteria. Starter adds pages, sections, schema, the Blueprint map, and the conversational agent. Pro adds the App Builder, sprint planner, dependency graph, stack proposal, and system design spec. Team adds shared workspaces; Enterprise adds the biggest allowance and frontier models. Or try vibemap.ai/demo without signing up.
- What are auto and premium tokens?
- Every VibeMap plan includes a monthly token budget split into two pools. Auto tokens cover routine steps — summary, features, user stories — which run on fast economy models. Premium tokens cover the steps VibeMap routes to premium reasoning models, which only Pro and above can use. The two pools are tracked separately: Free includes 300K auto and no premium, Starter 1.75M auto and no premium, Pro 6M plus 1M, and Team 15M plus 3M. Budgets meter in rolling five-day windows so one heavy day cannot drain the month.
- Will I burn through tokens fixing the AI's own mistakes?
- This is the standard failure mode of credit-metered AI app builders, and VibeMap's design avoids most of it. Most of what VibeMap generates is specification, so a wrong answer is usually a paragraph you edit by hand rather than a build you re-run. The App Builder on Pro and above does generate code, but it first shows a free build plan of what it will compile and which pages need AI, before any tokens are spent, and it type-checks and repairs its own output before pushing. Any authoring your own coding agent does over MCP costs nothing from your VibeMap budget. You are billed when VibeMap generates, not when you correct it.
- What happens if I run out of tokens mid-project?
- Your project does not lock. Existing data stays fully editable, and your connected IDE agent can keep working through already-generated acceptance criteria — only new VibeMap generations pause until the next rolling window or an upgrade. On Pro and Team, running out of premium tokens does not stop you: VibeMap steps down to an economy model automatically for the rest of the period, and generations pause only when the total budget is spent. Free and Starter have no premium pool, so they simply stop at their cap.
- Do unused tokens roll over to the next month?
- No. VibeMap meters token budgets in rolling five-day windows inside each billing period, and unused allowance in a window does not carry forward. The design trades rollover for protection against the opposite problem: a single runaway day consuming an entire month's budget. In practice this means a steady working rhythm gets more out of a plan than one long sprint. Usage, the premium-versus-auto split, days remaining in the cycle, and a record-by-record table are all visible under Billing → Usage & Analytics.
- Can I cancel anytime?
- Yes. Open Billing → Subscriptions and choose Cancel Subscription; cancellation is scheduled for the end of the current paid period, and the page then shows the date your access stops. You keep full access until then. Note that no refunds are issued for partial months except where required by law, so cancelling mid-cycle does not generate a pro-rata refund. Payments run through Stripe, and card details are handled entirely by Stripe and never stored on VibeMap servers.
- How does billing work for teams?
- The VibeMap Team plan is $79 per month for a single shared subscription with unlimited seats and a shared token budget, rather than a per-person licence. It adds shared team workspaces and owner, admin, and member roles. The Team plan is billed separately from any personal subscription, on the team's own settings page rather than your personal billing page.
Data and privacy
Who can see your spec, who owns it, and how you get it out.
- Do you train AI models on my data?
- On paid plans, no. Your inputs and generated outputs are not used by VibeMap or by VibeMap's LLM providers to train foundation models, and this is enforced at the gateway: paid inference is routed through OpenRouter with a no-data-collection policy that restricts routing to upstream providers whose own policy is not to log or train on prompts. The full detail, including what applies on the free tier, is in the VibeMap privacy policy at vibemap.ai/privacy.
- Who owns the specs I create in VibeMap?
- You do. VibeMap's terms state plainly that VibeMap claims no rights over your content. The personas, features, user stories, acceptance criteria, schema, and pages you generate are yours to use commercially, publish, hand to a client, or take elsewhere. VibeMap's role is to produce and host the artifacts, not to license them back to you.
- Am I locked in? How do I get my spec out of VibeMap?
- No. Every VibeMap artifact — features, personas, stories, acceptance criteria, pages, schema — is readable through the VibeMap REST API and the MCP server, so your agent, scripts, or tools pull straight from the source of truth. You can also download files: the whole dev spec as one markdown document, the project summary as markdown, the schema as a SQL file with row-level-security policies, and your generated pages as a Next.js project ZIP. Account → Credentials → Export downloads a GDPR-style JSON copy of your profile, projects, and billing history.
- Can I delete my account and everything in it?
- Yes. Account → Credentials holds the Privacy & Data controls: Export downloads a JSON copy of your profile, projects, and billing history, and Delete account removes everything permanently. VibeMap also supports GDPR access rights through the same section. If you want a copy of your work before deleting, run the export first — deletion is not reversible.
- Can I share a project with my team?
- Yes, on VibeMap's Team plan. Team workspaces give you shared projects, a shared token budget, and owner, admin, and member roles, so engineers, PMs, and designers collaborate on one blueprint rather than passing copies around. The VibeMap Team plan is a single $79 subscription with unlimited seats rather than per-person pricing. On Free, Starter, and Pro, projects belong to the individual account.