Bolt.new vs v0

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Bolt.new
   Bolt.new✓fullprobed8/10

   A direct probe confirms Bolt's support site serves a valid llms.txt file (HTTP 200) listing structured links to its docs, and the docs themselves are exposed in clean .md format suitable for agent consumption. This is concrete first-party evidence the capability works as claimed, not just a vendor claim. Missing for 10: no independent/community report of an agent actually consuming llms.txt in practice, and no evidence of additional agent-specific manifest formats beyond llms.txt.

   • [probe] “PROBE llms.txt: HTTP 200 at https://support.bolt.new/llms.txt # Bolt - [Intro to Bolt](https://support.bolt.new/get-started/intro-bolt.md):…”
   • [claimed-docs] “edit your code directly in code view”

   proof ↗⚑ flag

   v0—none0/10

   No evidence that v0 publishes an llms.txt file or agent-oriented docs endpoint that other agents can be pointed at; the docs.md probe shows a markdown version of a page but not a standardized llms.txt/agent-discovery mechanism referenced anywhere in the pack.

   ⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to v0
   Bolt.new—none0/10

   Bolt.new is a browser-based, chat/UI-driven builder; no evidence of a CLI, API, or headless mode for CI/automation—OpenAPI probes 404 and docs describe only interactive web workflows (chat, code view, collaborate, publish). No mention of scriptable or non-interactive invocation exists in the evidence pack.

   • [probe] “PROBE openapi: all candidate paths 404 (https://support.bolt.new/openapi.json, https://support.bolt.new/swagger.json, https://support.bolt.n…”
   • [claimed-docs] “edit your code directly in code view”
   • [claimed-docs] “Bolt offers two agents, Standard and Max, powered by large language models.”

   proof ↗⚑ flag

   v0~partialclaimed5/10

   v0 provides a programmatic API/SDK (v0-sdk) allowing chat/code-gen calls to be scripted, and GitHub integration runs CI checks and can auto-fix CI failures, suggesting some automation-friendly hooks; but there's no documented headless CLI mode or explicit CI-runner integration pattern (e.g., GitHub Actions example) for orchestrating v0 itself within a pipeline. missing for 10: a documented CLI/headless mode, an official CI/CD pipeline example (e.g., GitHub Actions), and independent confirmation of running v0 fully unattended in automation.

   • [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
   • [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
   • [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
   • [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
   • [claimed-docs] “CI checks: See whether checks are running, passing, skipped, or failing.”
   • [claimed-docs] “v0 reads the relevant logs, diagnoses the failure, and applies a fix.”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Bolt.new
   Bolt.new~partialclaimed5/10

   Bolt's docs mention a 'connect-mcp' page and a built-in GitHub MCP connector for searching code, issues, and discussions (bolt-docs-18, bolt-docs-40), showing MCP tool-use exists, but there's no evidence users can add arbitrary/custom MCP servers beyond the GitHub connector. missing for 10: documentation of adding custom/third-party MCP servers, evidence of general MCP server registration UI, and independent confirmation of multi-server support.

   • [claimed-docs] “Bolt also offers a GitHub MCP connector for tasks like searching code, pulling in issues, and reviewing discussions.”
   • [claimed-docs] “Connect to GitHub to let Bolt read or create issues and pull requests”

   proof ↗⚑ flag

   v0—none0/10

   No evidence that v0 supports connecting to MCP servers or consuming their tools; docs mention integrations with databases, backend services, and AI providers but never reference MCP. missing for 10: any mention of MCP protocol/server support, documented tool-use via MCP, or third-party MCP connector.

   ⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Bolt.new—none0/10

   Bolt.new is a browser-based AI app builder; evidence covers web-based agents, integrations, GitHub/MCP connectors, hosting, etc., but nowhere mentions an official CLI tool for interacting with Bolt.

   ⚑ flag

   v0—none0/10

   Evidence shows a v0 API and a JavaScript/TypeScript SDK (v0-sdk) for programmatic access, but no official command-line interface tool is documented anywhere in the pack.

   • [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
   • [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
   • [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to v0
   Bolt.new—none0/10

   No evidence of a documented public API for programmatically driving Bolt.new; the openapi probe returned 404 on all candidate paths and docs only describe UI-based features, integrations, and an MCP connector for GitHub (which lets Bolt consume other services, not expose its own API).

   • [probe] “PROBE openapi: all candidate paths 404 (https://support.bolt.new/openapi.json, https://support.bolt.new/swagger.json, https://support.bolt.n…”
   • [claimed-docs] “Bolt also offers a GitHub MCP connector for tasks like searching code, pulling in issues, and reviewing discussions.”
   • [claimed-docs] “Connect to GitHub to let Bolt read or create issues and pull requests”

   proof ↗⚑ flag

   v0✓fullclaimed8/10

   v0 documents a full public API (v0.app/docs/api/platform) offering programmatic access to code generation, chat, project management, and deployment, backed by an official SDK (vercel/v0-sdk) with concrete code examples (chats.create, streaming reads, API key/OIDC auth). This is corroborated by GitHub SDK evidence, not just marketing docs. Missing for 10: independent third-party developer reports/tutorials building production integrations on the API, and more detail on API rate limits/versioning.

   • [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
   • [claimed-docs] “Custom chat interfaces - Build your own UI for v0's AI-powered code generation”
   • [claimed-docs] “Start with existing files (fast, no tokens)”
   • [claimed-docs] “GitHub integration for repository imports”
   • [claimed-docs] “Export capabilities for backup and migration”
   • [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
   • [github] “const result = readV0Stream(serverResult.toResponse())”
   • [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Bolt.new—none0/10

   No evidence of any scoped or least-privilege API credential/token issuance for agents; docs mention collaborator roles and third-party integrations (GitHub, Supabase, Stripe) but nothing about generating restricted API keys or credentials for AI agents.

   ⚑ flag

   v0—none0/10

   Evidence shows only a single API key (V0_API_KEY) or OIDC-based server auth for the v0 SDK, with no mention of scoped, role-based, or least-privilege credential issuance for agents. Missing for 10: any documentation of granular permission scopes, per-agent tokens, or restricted API key capabilities.

   • [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
   • [claimed-docs] “Securely store sensitive information like API keys, tokens, and other credentials.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to v0
   Bolt.new—none0/10

   Evidence shows no official SDK or public API for Bolt.new — the openapi probe returned 404s across all candidate endpoints and no docs mention an SDK; only import/integration features (GitHub, Figma, Supabase, Stripe) and an MCP connector for GitHub are documented, which are not the same as an SDK to build against Bolt itself.

   • [probe] “PROBE openapi: all candidate paths 404 (https://support.bolt.new/openapi.json, https://support.bolt.new/swagger.json, https://support.bolt.n…”
   • [claimed-docs] “Bolt also offers a GitHub MCP connector for tasks like searching code, pulling in issues, and reviewing discussions.”
   • [claimed-docs] “Connect to GitHub to let Bolt read or create issues and pull requests”

   proof ↗⚑ flag

   v0✓fullclaimed7/10

   v0 provides an official v0-sdk on GitHub with documented API usage (v0.chats.create, streaming, API key auth) plus a Platform API documented for programmatic access to chat, code generation, and project management. missing for 10: independent/hands-on developer corroboration of SDK reliability, multi-language SDK support, and deeper API reference coverage beyond quickstart snippets.

   • [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
   • [github] “const result = readV0Stream(serverResult.toResponse())”
   • [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
   • [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
   • [claimed-docs] “Custom chat interfaces - Build your own UI for v0's AI-powered code generation”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Bolt.new—none0/10

   No evidence of any webhook subscription mechanism; Bolt.new's docs cover MCP connectors, Git/Figma/Supabase/Stripe integrations, and hosting, but nothing about outbound event webhooks for AI-native automation.

   ⚑ flag

   v0—none0/10

   No evidence of a webhooks subscription/event system in v0's docs or API pack; the API is described as request/response (create chats, streaming) with no mention of webhook endpoints or event subscriptions.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Bolt.new
   Bolt.new~partialclaimed5/10

   Bolt provides some AI-driven analysis of the project itself, e.g. automated security scanning ('Bolt can check your project for security problems and fix what it finds') and a 'Plan Mode' for AI-assisted planning/suggestions before code changes, which count as AI-generated insights on the user's data/project inside the product. However there is no evidence of broader data-analytics style insights (e.g. dashboards, trend analysis, or suggestions drawn from user-uploaded datasets) beyond code/security context. Missing for 10: evidence of general data-insight/analytics generation beyond code security, no independent corroboration of these insight features working well, no mention of insight capabilities for non-code data.

   • [claimed-docs] “Bolt can check your project for security problems and fix what it finds.”
   • [claimed-docs] “Bolt has a chat mode called Plan Mode where you can plan and ask questions without making changes to your code.”
   • [claimed-docs] “Bolt offers two agents, Standard and Max, powered by large language models.”

   proof ↗⚑ flag

   v0~partialclaimed4/10

   v0 offers some AI-driven analysis of a user's own data in the sense of reading logs, diagnosing build failures, and applying fixes, and it 'plans, creates tasks, and connects to databases as it builds,' which is a narrow form of AI-generated insight/suggestion from data within the product. However, there is no evidence of broader data-insight features (e.g., analytics, trend/insight surfacing from business or usage data) beyond code/log diagnostics, and no independent corroboration of this specific capability. Missing for 10: dedicated data-insight/analytics features, independent hands-on evidence of 'insights' beyond build-error fixing.

   • [claimed-docs] “v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
   • [claimed-docs] “Automatically fix errors in your code with intelligent diagnostics.”
   • [claimed-docs] “select Fix with v0 or Fix Build. v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
   • [claimed-docs] “v0 plans, creates tasks, and connects to databases as it builds.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Bolt.new—none0/10

   No evidence of scheduled tasks, triggers, or any background/autonomous automation capability; Bolt.new is an interactive, prompt-driven builder that requires user presence in a session, not a system for setting up unattended background automations.

   ⚑ flag

   v0—none0/10

   v0's docs describe on-demand code generation, GitHub integration, deployments, and API access, but there is no evidence of scheduled/triggered automations or background agentic tasks that run autonomously without a user-initiated chat or API call (e.g., no cron jobs, webhooks, or persistent background workers are described). The closest features (auto-fix on CI failure, 'Fix with v0') are triggered by user action or CI events within a user-initiated flow, not autonomous background automation.

   • [claimed-docs] “v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
   • [claimed-docs] “select Fix with v0 or Fix Build. v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
   • [claimed-docs] “open the branch menu and select Fix Conflicts, Fix CI, or Fix CI + Conflicts.”
   • [claimed-docs] “v0 plans, creates tasks, and connects to databases as it builds.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Bolt.new✓fullcommunity8/10

   Bolt.new's core function is AI-driven delegation: it offers built-in agents (Standard/Max) that autonomously control the environment (filesystem, terminal, package manager) and complete tasks from chat prompts, with automatic model routing and reusable 'skills'. Community reports confirm real task delegation success (e.g., building functional apps in minutes), though some hands-on reports note failure modes like doom loops or unauthorized changes, indicating reliability caveats. Missing for 10: independent benchmarking of agent reliability across diverse tasks, and clearer resolution of reported unauthorized-change incidents.

   • [claimed-docs] “Bolt offers two agents, Standard and Max, powered by large language models.”
   • [claimed-docs] “Bolt automatically routes to the right model for each task, balancing quality and cost.”
   • [github] “Bolt.new gives AI models complete control over the entire environment including the filesystem, node server, package manager, terminal, and …”
   • [claimed-docs] “Skills are reusable instructions that teach Bolt how to handle specific scenarios.”
   • [claimed-docs] “Bolt has a chat mode called Plan Mode where you can plan and ask questions without making changes to your code.”
   • [community] “i've seen people literally go from idea to prod in a day when it normally would take a week. Mind blowing.”
   • [community] “attempted to create a react app to plan meals... a functional app to edit ingredients, recipes and mealplans without data persistence that w…”
   • [community] “I've tried several proof of concepts with Bolt and every time just get into a doom loop where there is a cycle of breakage, each 'fix' resur…”

   proof ↗⚑ flag

   v0✓fullprobed8/10

   v0 is itself a built-in AI assistant that users delegate coding/build tasks to: docs show it plans, creates tasks, connects to databases, diagnoses and fixes build/CI errors autonomously (v0-docs-35, v0-docs-9/17/20, v0-docs-26), and community reports confirm a full 'dev-to-deploy' delegation experience with an MVP built end-to-end (v0-comm-1). Missing for 10: independent benchmarking of autonomous task delegation beyond anecdote, and no detail on multi-step task planning transparency.

   • [claimed-docs] “v0 plans, creates tasks, and connects to databases as it builds.”
   • [claimed-docs] “v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
   • [claimed-docs] “Automatically fix errors in your code with intelligent diagnostics.”
   • [claimed-docs] “select Fix with v0 or Fix Build. v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
   • [claimed-docs] “open the branch menu and select Fix Conflicts, Fix CI, or Fix CI + Conflicts.”
   • [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”
   • [probe] “PROBE docs-md: HTTP 200 at https://v0.app/docs.md --- title: What is v0? description: v0 is an AI agent that helps anyone create real code a…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Bolt.new✓fullcommunity8/10

   Bolt.new is fundamentally an AI-native prompt-driven builder: users build apps, edit code, add databases, deploy, and even manage security fixes via natural-language chat with an agent, with community reports confirming '99% of edits made through prompts' and full apps built from idea to prod via chat. Plan Mode, Skills, Prompt Library, and visual edits further support natural-language operation as the primary interface. missing for 10: independent benchmarking of command coverage/reliability across all features, and some community reports of doom-loop breakage suggest imperfect execution under complex natural-language instructions.

   • [github] “Bolt.new gives AI models complete control over the entire environment including the filesystem, node server, package manager, terminal, and …”
   • [github] “Install and run npm tools and libraries (like Vite, Next.js, and more) - Run Node.js servers - Interact with third-party APIs - Deploy…”
   • [claimed-docs] “Bolt offers two agents, Standard and Max, powered by large language models.”
   • [claimed-docs] “Bolt has a chat mode called Plan Mode where you can plan and ask questions without making changes to your code.”
   • [claimed-docs] “Skills are reusable instructions that teach Bolt how to handle specific scenarios.”
   • [claimed-docs] “Save your prompts in the Prompt Library to reuse them later, and apply built-in prompts Bolt provides for common tasks.”
   • [community] “i've seen people literally go from idea to prod in a day when it normally would take a week. Mind blowing.”
   • [community] “was quite impressed after building my label maker application and stylex playground. Had some real world needs and both were built in bolt w…”
   • [community] “I've tried several proof of concepts with Bolt and every time just get into a doom loop where there is a cycle of breakage, each 'fix' resur…”

   proof ↗⚑ flag

   v0✓fullprobed8/10

   v0's core interaction model is natural-language chat: docs and SDK show building apps from prompts like 'Build me a personal website', plus NL-driven fixes, migrations, and mockup-to-UI conversion, and community reports confirm fast prompt-to-deploy workflows in practice. Missing for 10: independent evidence on breadth/reliability of more complex multi-step NL commands and any documented failure modes for ambiguous instructions.

   • [claimed-docs] “Create custom hooks and functionality”
   • [claimed-docs] “Turn mockups into real, high-fidelity user interfaces that reflect user flows and constraints.”
   • [claimed-docs] “v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
   • [claimed-docs] “Quickly scaffold full-stack apps or components following best practices and modern standards.”
   • [claimed-docs] “Migrate to the latest Next.js features”
   • [claimed-docs] “Automatically fix errors in your code with intelligent diagnostics.”
   • [claimed-docs] “v0 plans, creates tasks, and connects to databases as it builds.”
   • [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
   • [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”
   • [probe] “PROBE docs-md: HTTP 200 at https://v0.app/docs.md --- title: What is v0? description: v0 is an AI agent that helps anyone create real code a…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Bolt.new—none0/10

   No evidence of an interactive API reference or runnable examples; probe explicitly found no OpenAPI/Swagger spec, and docs cover only product features, not an API reference.

   • [probe] “PROBE openapi: all candidate paths 404 (https://support.bolt.new/openapi.json, https://support.bolt.new/swagger.json, https://support.bolt.n…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://support.bolt.new/llms.txt # Bolt - [Intro to Bolt](https://support.bolt.new/get-started/intro-bolt.md):…”

   proof ↗⚑ flag

   v0—none0/10

   v0 does publish API docs and an SDK with code snippets (v0-docs-4, v0-gh-1, v0-gh-2), but there is no evidence of an interactive API reference (e.g., a browsable console with runnable/try-it examples) — only static documentation pages and GitHub code samples. missing for 10: an interactive API console, in-browser runnable examples, evidence of a Swagger/OpenAPI-style explorer.

   • [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
   • [claimed-docs] “Custom chat interfaces - Build your own UI for v0's AI-powered code generation”
   • [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
   • [github] “const result = readV0Stream(serverResult.toResponse())”
   • [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Bolt.new—none0/10

   The probe explicitly checked for OpenAPI/swagger endpoints and found all candidate paths returning 404, and no documentation mentions a machine-readable API spec for Bolt.new; only an llms.txt for docs discovery exists, which is not an API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://support.bolt.new/openapi.json, https://support.bolt.new/swagger.json, https://support.bolt.n…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://support.bolt.new/llms.txt # Bolt - [Intro to Bolt](https://support.bolt.new/get-started/intro-bolt.md):…”

   proof ↗⚑ flag

   v0—none0/10

   v0 documents a REST-like API platform and SDK (v0-docs-4, v0-gh-1) but no evidence anywhere shows a downloadable OpenAPI/Swagger spec or other machine-readable API description; missing for 10: OpenAPI/JSON schema file, published spec endpoint, or SDK auto-generation from spec.

   • [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
   • [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
   • [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to v0
   Bolt.new—none0/10

   The evidence pack shows Bolt integrates with Supabase and offers a built-in Database, plus hosting/visibility controls, but there is no mention anywhere of a staging/sandbox environment distinct from production, nor of safeguards preventing AI edits from touching live production data. Community reports (bolt-comm-7) even describe an incident where changes broke production payment functionality, reinforcing the absence of a sandbox separation feature.

   • [claimed-docs] “if you already have a Supabase account connected and need more advanced database features or tighter control over your data, choosing Supaba…”
   • [claimed-docs] “Supabase provides: A hosted SQL database... Authentication services... Edge functions”
   • [claimed-docs] “If you prefer to use Supabase when creating a new project, you can select it during setup.”
   • [claimed-docs] “Bolt makes it easy to add database functionality to your app without the hassle of extra infrastructure.”
   • [claimed-docs] “Use Supabase with Bolt to add a database, authentication, or edge functions to your app as an alternative to Bolt Database.”
   • [community] “Bolt.new's AI burned 10M tokens on unauthorized changes... removed critical systems like my FingerprintJS security layer without asking... T…”

   proof ↗⚑ flag

   v0~partialclaimed6/10

   v0 supports isolated branches and preview deployments that are separate from the production URL, letting changes be reviewed/tested before they affect production (v0-docs-38, v0-docs-39, v0-docs-29, v0-docs-11). However, there is no explicit sandbox/staging environment for data (e.g., a separate database or mock data layer) — integrations like Supabase/Neon/Upstash appear to connect directly to real backend services rather than a sandboxed copy. Missing for 10: explicit data-isolation/sandbox environment separate from production databases, first-party documentation of a test/staging data layer, and independent confirmation that production data is never touched during preview/testing.

   • [claimed-docs] “Preview deployments are built from working branches.”
   • [claimed-docs] “work on isolated branches, preview changes, run CI, and publish through pull requests”
   • [claimed-docs] “When multiple chats share a Project, deploying from any of them updates the same production URL.”
   • [claimed-docs] “One Project shares deployment, hosting, domains, and environment variables for the chats connected to it.”
   • [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase, and AI mod…”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Bolt.new—none0/10

   No evidence of a public versioned API, changelog, or deprecation policy for Bolt.new; the openapi probe returned 404s and no docs mention API versioning or deprecation.

   • [probe] “PROBE openapi: all candidate paths 404 (https://support.bolt.new/openapi.json, https://support.bolt.new/swagger.json, https://support.bolt.n…”

   proof ↗⚑ flag

   v0—none0/10

   While v0 documents an API platform (v0-docs-4, v0-docs-19) and an SDK (v0-gh-1..3), there is no evidence of API versioning scheme or a documented deprecation policy anywhere in the evidence pack.

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Bolt.new—none0/10

   Bolt.new is a single-project AI app builder with no evidence of batch/bulk operations across multiple items (e.g., bulk edits, batch API calls, multi-project automation). Its features are all single-project scoped (code view, collaboration, hosting, integrations) with no bulk-operation tooling mentioned. Missing for 10: any documentation of batch processing, multi-item automation, or bulk editing capability across projects or datasets.

   ⚑ flag

   v0—none0/10

   The evidence shows v0's API can programmatically create individual chats/projects, but there is no documentation or example of performing bulk/batch operations across many items at once (e.g., batch generation, bulk edits, mass deployment). Nothing in the docs or SDK references batching, looping over collections, or multi-item transactions.

   ⚑ flag

2. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Bolt.new—none0/10

   No evidence in the pack mentions scheduling, cron jobs, recurring workflows, or any automation trigger mechanism; Bolt.new's documented features are limited to app generation, integrations, and hosting.

   ⚑ flag

   v0—none0/10

   No evidence anywhere in the pack of scheduling, cron-like triggers, or recurring workflow automation in v0; the product is oriented around chat-driven code generation, deployment, and API-triggered chats, not scheduled/recurring jobs.

   ⚑ flag

3. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Bolt.new~partialcommunity6/10

   Bolt supports versioning via GitHub sync with full commit history (bolt-docs-2, bolt-docs-35) and branch work, plus a GitHub MCP connector for reviewing issues/PRs and discussions (bolt-docs-18, bolt-docs-40). Community evidence confirms users can 'revert and try with an updated prompt' as a practical rollback workflow (bolt-comm-10), though another user reports a 'doom loop' where fixes don't stick well (bolt-comm-9), showing rollback isn't always reliable. Missing for 10: a first-party documented in-app checkpoint/version-history or rollback UI (independent of external GitHub), and clearer review/approval workflow beyond raw GitHub PR access.

   • [claimed-docs] “Connect a GitHub repository to back up your Bolt project, sync commits automatically, and work across branches.”
   • [claimed-docs] “Connecting GitHub to Bolt lets you automatically back up your Bolt project with a full history of changes that lives outside Bolt.”
   • [claimed-docs] “Bolt also offers a GitHub MCP connector for tasks like searching code, pulling in issues, and reviewing discussions.”
   • [claimed-docs] “Connect to GitHub to let Bolt read or create issues and pull requests”
   • [community] “was quite impressed after building my label maker application and stylex playground. Had some real world needs and both were built in bolt w…”
   • [community] “I've tried several proof of concepts with Bolt and every time just get into a doom loop where there is a cycle of breakage, each 'fix' resur…”

   proof ↗⚑ flag

   v0~partialclaimed6/10

   v0's GitHub integration gives git-based version control (isolated branches, commits, PRs, CI checks) which supports versioning and review of generated projects, and branch/PR mechanics implicitly allow reverting to prior states. However, there is no explicit 'rollback' feature or chat/version history UI documented specifically for automations, and 'automations' as a distinct concept (vs. generated code) isn't addressed. Missing for 10: dedicated rollback/undo capability, explicit versioning of automations (not just code), and independent evidence of review/rollback workflows in practice.

   • [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
   • [claimed-docs] “The Duplicate Branch dialog creates a new chat and branch containing the current branch's commits.”
   • [claimed-docs] “open the branch menu and select Fix Conflicts, Fix CI, or Fix CI + Conflicts.”
   • [claimed-docs] “CI checks: See whether checks are running, passing, skipped, or failing.”
   • [claimed-docs] “work on isolated branches, preview changes, run CI, and publish through pull requests”

   proof ↗⚑ flag

Ai features

1. ai-native userAdd AI features like LLM calls and agents to my generated app without managing provider keys myself

   weight 2 · round to v0
   Bolt.new—none0/10

   The evidence covers Bolt's own coding agents (Standard/Max) and model routing for generating code, plus integrations like Supabase/Stripe for database and payments, but there is no evidence of a managed service letting the *generated app* itself call LLMs or run agent features without the end-user supplying their own provider API keys.

   ⚑ flag

   v0~partialclaimed5/10

   v0's project integrations explicitly include 'AI model providers' alongside databases like Upstash and Neon, and v0 can securely store API keys/tokens for connected services, suggesting some ability to wire in LLM/agent providers without manual key wrangling in code — but v0-docs-44 implies the user still supplies and stores the provider key themselves rather than v0 fully abstracting key management, and there's no dedicated doc on built-in LLM/agent calling with zero-config provider access. missing for 10: explicit documentation of a first-party managed LLM/agent provider (no user-supplied key required), hands-on confirmation that AI features work without configuring provider credentials.

   • [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase, and AI mod…”
   • [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase”
   • [claimed-docs] “Securely store sensitive information like API keys, tokens, and other credentials.”
   • [claimed-docs] “v0 plans, creates tasks, and connects to databases as it builds.”

   proof ↗⚑ flag

Auth

1. developerAdd user sign-up and login (email, social providers) scaffolded by the builder

   weight 3 · round to Bolt.new
   Bolt.new~partialclaimed6/10

   Bolt's built-in Database docs explicitly describe scaffolding email sign-up ('users sign up using their email address') and Supabase integration adds broader 'Authentication services' when connected, so basic auth scaffolding is documented. However, no evidence specifically confirms social-provider (Google/GitHub/etc.) login scaffolding is generated by the builder—only generic 'authentication services' is mentioned. Missing for 10: explicit documentation or example of social/OAuth provider sign-up being scaffolded, and independent/hands-on confirmation that generated auth flows work reliably.

   • [claimed-docs] “This option allows your project's users to sign up using their email address.”
   • [claimed-docs] “Supabase provides: A hosted SQL database... Authentication services... Edge functions”
   • [claimed-docs] “Use Supabase with Bolt to add a database, authentication, or edge functions to your app as an alternative to Bolt Database.”
   • [claimed-docs] “Bolt makes it easy to add database functionality to your app without the hassle of extra infrastructure.”

   proof ↗⚑ flag

   v0~partialcommunity5/10

   v0 integrates with backend services like Supabase (which typically provide auth) and one community report describes building an app 'with auth, roles' using v0, suggesting the builder can scaffold authentication flows. However, there is no first-party documentation specifically describing sign-up/login scaffolding, social provider integration, or auth templates. Missing for 10: explicit docs on email/social auth scaffolding, named auth provider integrations (e.g., Auth.js, Clerk), and independent verification of social login flows.

   • [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”
   • [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase, and AI mod…”
   • [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase”
   • [claimed-docs] “Connect to backend to build rich, data driven applications.”

   proof ↗⚑ flag

Database

1. developerGet a database provisioned and wired into my app without leaving the builder

   weight 3 · round to v0
   Bolt.new~partialcommunity7/10

   Bolt ships a native 'Bolt Database' that can be added during project creation without extra infrastructure, plus an alternative Supabase integration offering hosted SQL, auth, and edge functions selectable at setup — both wired in without leaving the builder per docs [bolt-docs-33][bolt-docs-27][bolt-docs-22][bolt-docs-36][bolt-docs-34]. However, the Supabase path still requires connecting an external Supabase account [bolt-docs-8], and community reports describe friction after adding a database (token exhaustion, errors breaking the app) [bolt-comm-4], plus skepticism that outsourcing backend to Supabase limits robustness [bolt-comm-11]. Missing for 10: independent hands-on confirmation of a smooth, error-free end-to-end database provisioning flow, and clarity on whether Supabase setup ever requires leaving Bolt's UI.

   • [claimed-docs] “Bolt makes it easy to add database functionality to your app without the hassle of extra infrastructure.”
   • [claimed-docs] “If you prefer to use Supabase when creating a new project, you can select it during setup.”
   • [claimed-docs] “Supabase provides: A hosted SQL database... Authentication services... Edge functions”
   • [claimed-docs] “Use Supabase with Bolt to add a database, authentication, or edge functions to your app as an alternative to Bolt Database.”
   • [claimed-docs] “This option allows your project's users to sign up using their email address.”
   • [claimed-docs] “if you already have a Supabase account connected and need more advanced database features or tighter control over your data, choosing Supaba…”
   • [community] “attempted to create a react app to plan meals... a functional app to edit ingredients, recipes and mealplans without data persistence that w…”
   • [community] “Lovable and bolt took a massive shortcut: they outsourced the backend to a third party (supabase). This makes their ceiling to build 'useful…”

   proof ↗⚑ flag

   v0✓fullclaimed7/10

   v0's Project docs explicitly describe connecting databases (Neon Postgres, Upstash Redis) and backend services (Supabase) directly within a Project, with v0 stated to 'plan, create tasks, and connect to databases as it builds,' and secrets/env vars are managed within the same Project without leaving the tool. This matches the story of provisioning and wiring a database inline in the builder. Missing for 10: no independent/hands-on report confirming the actual provisioning flow works smoothly, and no detail on whether v0 auto-creates the database instance or just connects an existing one.

   • [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase, and AI mod…”
   • [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase”
   • [claimed-docs] “Connect your project to third-party services to give your Project access to external data and functionality.”
   • [claimed-docs] “Connect to backend to build rich, data driven applications.”
   • [claimed-docs] “v0 plans, creates tasks, and connects to databases as it builds.”
   • [claimed-docs] “Securely store sensitive information like API keys, tokens, and other credentials.”

   proof ↗⚑ flag

Security

1. developerHave the platform review my generated app for security issues before it goes live

   weight 2 · round to Bolt.new
   Bolt.new~partialclaimed5/10

   Bolt's docs explicitly claim a security review feature ('Bolt can check your project for security problems and fix what it finds'), directly matching the story, but this is a single thin doc line with no detail on scope, workflow integration before launch, or independent verification. Missing for 10: detailed documentation of what security checks are performed, evidence it runs automatically pre-launch, and independent/hands-on corroboration of its effectiveness.

   • [claimed-docs] “Bolt can check your project for security problems and fix what it finds.”

   proof ↗⚑ flag

   v0—none0/10

   No evidence pack item mentions any security review, vulnerability scanning, or pre-launch security audit feature; deployment features focus on CI/build fixes and hosting, not security review. Missing for 10: any documented security scanning/review capability, evidence of vulnerability detection, or pre-deploy security checklist.

   ⚑ flag

Server logic

1. developerAdd server-side functions and third-party integrations like payments and email from the builder

   weight 2 · round to Bolt.new
   Bolt.new~partialcommunity6/10

   Bolt.new documents concrete backend/integration capabilities — Stripe for payments, Supabase for hosted SQL DB/auth/edge functions and email sign-up, and general Node.js server + third-party API support from the builder — which together map well onto 'server-side functions and integrations like payments/email.' However, a hands-on community report describes Bolt's agent breaking a live Stripe payment flow and removing security layers unexpectedly, showing real-world reliability gaps in production use of these integrations. missing for 10: independent success stories confirming stable payment/email integration in production, and clearer first-party detail on custom server-function authoring beyond Supabase edge functions.

   • [claimed-docs] “Bolt integrates directly with Stripe to handle user payments and subscriptions.”
   • [claimed-docs] “Supabase provides: A hosted SQL database... Authentication services... Edge functions”
   • [claimed-docs] “This option allows your project's users to sign up using their email address.”
   • [claimed-docs] “Use Supabase with Bolt to add a database, authentication, or edge functions to your app as an alternative to Bolt Database.”
   • [github] “Install and run npm tools and libraries (like Vite, Next.js, and more) - Run Node.js servers - Interact with third-party APIs - Deploy…”
   • [community] “Bolt.new's AI burned 10M tokens on unauthorized changes... removed critical systems like my FingerprintJS security layer without asking... T…”

   proof ↗⚑ flag

   v0~partialclaimed5/10

   v0 docs show clear support for connecting projects to backend services and third-party integrations (Supabase, Upstash Redis, Neon Postgres, AI providers) and securely storing API keys/credentials, plus a general 'third-party services for external data and functionality' hook, which covers server-side function-like backend connections. However, no evidence specifically confirms out-of-the-box payments (e.g., Stripe) or email (e.g., Resend/SendGrid) integrations, nor detailed docs on writing custom server-side functions beyond generic 'connect to backend' language. Missing for 10: explicit payment-provider integration examples, explicit email-service integration examples, and documentation of custom server-side function authoring within the builder.

   • [claimed-docs] “Connect to backend to build rich, data driven applications.”
   • [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase, and AI mod…”
   • [claimed-docs] “Connect your project to third-party services to give your Project access to external data and functionality.”
   • [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase”
   • [claimed-docs] “Securely store sensitive information like API keys, tokens, and other credentials.”

   proof ↗⚑ flag

Export

1. developerExport the full source code and run or host the app outside the platform

   weight 3 · round drawn
   Bolt.new✓fullclaimed7/10

   Docs confirm Bolt projects use standard code (Vite/Next.js etc.), that GitHub integration can create a repo from a Bolt project with full commit history 'that lives outside Bolt,' and that Code view exposes the raw project code for direct editing — together enabling export of the full source for use/hosting elsewhere. Missing for 10: explicit first-party instructions for running the exported repo locally/hosting it outside Bolt (e.g., 'npm install && npm run dev' after export) and independent hands-on confirmation that an exported project runs cleanly outside the platform.

   • [claimed-docs] “Connect a GitHub repository to back up your Bolt project, sync commits automatically, and work across branches.”
   • [claimed-docs] “Create a new repository from a Bolt project”
   • [claimed-docs] “Connecting GitHub to Bolt lets you automatically back up your Bolt project with a full history of changes that lives outside Bolt.”
   • [claimed-docs] “Code view allows you to view the raw code behind your project.”
   • [claimed-docs] “Choose your languages and frameworks, connect to source control, and edit your code directly in code view.”

   proof ↗⚑ flag

   v0✓fullclaimed7/10

   v0 lets users connect a project to GitHub, push code directly to a repo, import existing GitHub code, and the API platform docs explicitly list 'Export capabilities for backup and migration,' meaning the generated code is not locked into the platform and can be run/hosted elsewhere. This is first-party documented but lacks independent hands-on verification of exporting and self-hosting outside Vercel's infrastructure. missing for 10: independent/community confirmation of exporting and successfully self-hosting a v0 app outside Vercel, and details on the exact export format/process.

   • [claimed-docs] “Connect to GitHub and push code directly to your repository.”
   • [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
   • [claimed-docs] “To start from code already on GitHub, use Import from GitHub.”
   • [claimed-docs] “Export capabilities for backup and migration”
   • [claimed-docs] “GitHub integration for repository imports”

   proof ↗⚑ flag

2. developerWork on the app locally with my own editor and tooling and push changes back to the platform

   weight 2 · round to v0
   Bolt.new~partialclaimed5/10

   Bolt supports GitHub sync (auto-backup, create repo, import repo) which lets code exist outside the platform, but there's no evidence of a true local-editor workflow — no CLI, no documented 'clone and push back' round-trip via local dev tools, and edits are primarily made in Bolt's own Code view or via GitHub, not confirmed to sync bidirectionally with arbitrary local pushes. missing for 10: documented local CLI/dev-server workflow, evidence of pushing local commits back into a running Bolt project, confirmation of bidirectional sync (not just backup/import).

   • [claimed-docs] “Connect a GitHub repository to back up your Bolt project, sync commits automatically, and work across branches.”
   • [claimed-docs] “Import a GitHub repository. Load an existing repository as a Bolt project.”
   • [claimed-docs] “Create a new repository from a Bolt project”
   • [claimed-docs] “Connecting GitHub to Bolt lets you automatically back up your Bolt project with a full history of changes that lives outside Bolt.”
   • [claimed-docs] “Choose your languages and frameworks, connect to source control, and edit your code directly in code view.”

   proof ↗⚑ flag

   v0✓fullclaimed7/10

   v0's GitHub integration lets developers connect a project to a repo, work on isolated branches, push code directly, and open PRs — enabling a workflow where code can be edited locally and pushed back to sync with the platform. Missing for 10: explicit mention of a local CLI/dev-server workflow and independent confirmation that locally-pushed commits are correctly re-synced into the v0 chat/build pipeline.

   • [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
   • [claimed-docs] “To start from code already on GitHub, use Import from GitHub.”
   • [claimed-docs] “To start from code already on GitHub, use Import from GitHub. Importing creates a chat at the selected base branch”
   • [claimed-docs] “Connect to GitHub and push code directly to your repository.”
   • [claimed-docs] “work on isolated branches, preview changes, run CI, and publish through pull requests”
   • [claimed-docs] “CI checks: See whether checks are running, passing, skipped, or failing.”
   • [claimed-docs] “open the branch menu and select Fix Conflicts, Fix CI, or Fix CI + Conflicts.”

   proof ↗⚑ flag

Git sync

1. developerSync my project to my own GitHub repository and keep changes flowing both ways

   weight 3 · round drawn
   Bolt.new✓fullclaimed8/10

   Docs clearly describe two-way GitHub sync: connecting a repo to back up and auto-sync commits with full history outside Bolt, importing an existing GitHub repo as a Bolt project, creating a new repo from a Bolt project, working across branches, and even a GitHub MCP connector for issues/PRs, plus direct code editing in code view. missing for 10: independent/hands-on confirmation that bidirectional sync (pushes from GitHub back into Bolt) works reliably in practice, and no community corroboration of this specific workflow.

   • [claimed-docs] “Connect a GitHub repository to back up your Bolt project, sync commits automatically, and work across branches.”
   • [claimed-docs] “Import a GitHub repository. Load an existing repository as a Bolt project.”
   • [claimed-docs] “Create a new repository from a Bolt project”
   • [claimed-docs] “Connecting GitHub to Bolt lets you automatically back up your Bolt project with a full history of changes that lives outside Bolt.”
   • [claimed-docs] “Choose your languages and frameworks, connect to source control, and edit your code directly in code view.”
   • [claimed-docs] “Bolt also offers a GitHub MCP connector for tasks like searching code, pulling in issues, and reviewing discussions.”
   • [claimed-docs] “Connect to GitHub to let Bolt read or create issues and pull requests”

   proof ↗⚑ flag

   v0✓fullclaimed8/10

   v0's docs describe robust two-way GitHub sync: connecting a project to a repo, working on isolated branches, previewing, running CI, publishing via PRs, importing existing GitHub code, and resolving conflicts/CI failures directly from v0 (v0-docs-2,3,26,27,30,39). This covers both directions of the sync story (v0→GitHub via branches/PRs, GitHub→v0 via import) with first-party specificity. Missing for 10: independent/hands-on community verification that the bidirectional sync works reliably in practice beyond vendor docs.

   • [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
   • [claimed-docs] “To start from code already on GitHub, use Import from GitHub.”
   • [claimed-docs] “open the branch menu and select Fix Conflicts, Fix CI, or Fix CI + Conflicts.”
   • [claimed-docs] “To start from code already on GitHub, use Import from GitHub. Importing creates a chat at the selected base branch”
   • [claimed-docs] “CI checks: See whether checks are running, passing, skipped, or failing.”
   • [claimed-docs] “work on isolated branches, preview changes, run CI, and publish through pull requests”
   • [claimed-docs] “The Duplicate Branch dialog creates a new chat and branch containing the current branch's commits.”

   proof ↗⚑ flag

Collaboration

1. founderMy team can work on the same project together in a shared workspace

   weight 2 · round to Bolt.new
   Bolt.new✓fullclaimed8/10

   Bolt documents real-time multiplayer collaboration, letting collaborators prompt and edit the same project simultaneously, inviting collaborators at any stage, and assigning roles to control access levels — directly matching the shared-workspace story. Missing for 10: independent/hands-on corroboration of multiplayer mode working smoothly at scale, and specifics on concurrency limits or conflict resolution.

   • [claimed-docs] “When your project visibility is set to public, collaborators can work together in multiplayer mode.”
   • [claimed-docs] “collaborators can work together in multiplayer mode. This lets you prompt and edit in the same project at the same time.”
   • [claimed-docs] “Work together in real time using multiplayer mode.”
   • [claimed-docs] “Bolt lets you invite collaborators to your project at any stage, whether you're still building, ready for review, or preparing to make your …”
   • [claimed-docs] “Assign collaborators a role that matches the level of access you want them to have.”

   proof ↗⚑ flag

   v0~partialclaimed5/10

   v0 supports Projects with shared deployments, environment variables, and multiple chats connected to one project, plus a Shared Credit Pool for team plans, suggesting basic team collaboration on a shared project. However there's no evidence of real-time co-editing, granular roles/permissions, comments, or explicit multi-user workspace management beyond credit pooling. missing for 10: evidence of real-time multi-user collaboration, role-based permissions, in-app commenting/review, and explicit documentation of team workspace setup beyond credit sharing.

   • [claimed-docs] “One Project shares deployment, hosting, domains, and environment variables for the chats connected to it.”
   • [claimed-docs] “You can connect multiple chats to the same Project. This is useful when working different parts of one Project”
   • [claimed-docs] “When multiple chats share a Project, deploying from any of them updates the same production URL.”
   • [claimed-docs] “Shared Credit Pool credits are shared among all team members”

   proof ↗⚑ flag

Domains

1. founderConnect a custom domain to my published app

   weight 2 · round to Bolt.new
   Bolt.new✓fullclaimed8/10

   Docs clearly document connecting a custom domain to a published Bolt project, either one already owned or purchased via Bolt (bolt-docs-12/16/23/28), alongside built-in bolt.host publishing (bolt-docs-32). Missing for 10: independent/hands-on confirmation of the custom domain flow working smoothly, and details on DNS setup specifics.

   • [claimed-docs] “you can attach a custom domain you own (like yoursite.com) or buy a domain through Bolt”
   • [claimed-docs] “you can attach a custom domain you own (like `yoursite.com`) or buy a domain through Bolt”
   • [claimed-docs] “you can attach a custom domain you own (like `yoursite.com`) or buy a domain through Bolt.”
   • [claimed-docs] “If you've already purchased a custom domain, you can connect it to your Bolt project.”
   • [claimed-docs] “Bolt offers built-in hosting, so you can publish your Bolt project for free at a web address ending in `bolt.host`.”

   proof ↗⚑ flag

   v0~partialclaimed3/10

   Docs mention that Projects share 'deployment, hosting, domains, and environment variables' implying custom domain support exists at the project level, but there is no explicit guidance, UI flow, or confirmation of connecting a custom domain to a published app. missing for 10: dedicated custom-domain setup docs, DNS/verification steps, hands-on confirmation that a founder can attach their own domain.

   • [claimed-docs] “One Project shares deployment, hosting, domains, and environment variables for the chats connected to it.”
   • [claimed-docs] “Deploy with one click to secure, scalable infrastructure powered by Vercel.”
   • [claimed-docs] “Go live instantly with one-click deployment to production in seconds.”

   proof ↗⚑ flag

Publish

1. developerDeploy the generated app to an external host or my own infrastructure

   weight 1 · round drawn
   Bolt.new~partialclaimed5/10

   Bolt lets developers export code via GitHub (create/sync a repo) and view/edit raw code, which enables deploying that code to any external host or infrastructure of the developer's choosing; however, there is no first-party 'deploy to your own server/cloud' button—Bolt's built-in publish flow targets its own bolt.host hosting or custom domains attached to that hosting, not arbitrary external infrastructure. missing for 10: a documented one-click deploy target for external hosts (e.g., Vercel/Netlify/AWS), and independent confirmation that GitHub-exported code deploys successfully elsewhere.

   • [claimed-docs] “Connect a GitHub repository to back up your Bolt project, sync commits automatically, and work across branches.”
   • [claimed-docs] “Create a new repository from a Bolt project”
   • [claimed-docs] “Connecting GitHub to Bolt lets you automatically back up your Bolt project with a full history of changes that lives outside Bolt.”
   • [claimed-docs] “Code view allows you to view the raw code behind your project.”
   • [claimed-docs] “you can attach a custom domain you own (like yoursite.com) or buy a domain through Bolt”

   proof ↗⚑ flag

   v0~partialclaimed5/10

   v0 emphasizes one-click deploy to Vercel's own infrastructure and GitHub push/export code, which allows deploying elsewhere via exported code, but there is no first-party support or documentation for direct deployment to non-Vercel hosts (e.g., AWS, Netlify, self-hosted servers) beyond pushing code to a repo. missing for 10: explicit support/instructions for deploying to external hosts or self-managed infrastructure beyond GitHub push, independent confirmation that exported/GitHub code deploys successfully outside Vercel.

   • [claimed-docs] “Deploy with one click to secure, scalable infrastructure powered by Vercel.”
   • [claimed-docs] “Connect to GitHub and push code directly to your repository.”
   • [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
   • [claimed-docs] “Export capabilities for backup and migration”
   • [claimed-docs] “Go live instantly with one-click deployment to production in seconds.”

   proof ↗⚑ flag

2. founderPublish my app to a live URL in one step

   weight 3 · round drawn
   Bolt.new✓fullclaimed8/10

   Bolt.new explicitly offers built-in one-click hosting to a bolt.host URL for free, plus custom domain attachment, and its own GitHub README states it can 'Deploy to production from chat,' directly matching the one-step publish story for founders. Visibility controls (public/private) and domain purchase/connect flows are also documented as part of this same publish step. missing for 10: independent/hands-on confirmation that the one-click publish flow works reliably in practice (no community reports specifically validating deployment simplicity or speed).

   • [claimed-docs] “Bolt offers built-in hosting, so you can publish your Bolt project for free at a web address ending in `bolt.host`.”
   • [claimed-docs] “you can attach a custom domain you own (like yoursite.com) or buy a domain through Bolt”
   • [claimed-docs] “you can attach a custom domain you own (like `yoursite.com`) or buy a domain through Bolt”
   • [claimed-docs] “you can attach a custom domain you own (like `yoursite.com`) or buy a domain through Bolt.”
   • [claimed-docs] “If you've already purchased a custom domain, you can connect it to your Bolt project.”
   • [claimed-docs] “When your site is private, only your team and invited users can see it.”
   • [claimed-docs] “you choose whether your site is visible to everyone on the web (public) or only to your team and other people you invite (private)”
   • [github] “Install and run npm tools and libraries (like Vite, Next.js, and more) - Run Node.js servers - Interact with third-party APIs - Deploy…”

   proof ↗⚑ flag

   v0✓fullcommunity8/10

   v0 docs explicitly describe one-click deploy to production via Vercel infrastructure, with project-level shared deployment URLs and instant go-live claims, corroborated by a community account of a full dev-to-deploy cycle to real users. Missing for 10: independent third-party verification of the exact one-step publish flow and no hands-on confirmation of custom domain setup ease.

   • [claimed-docs] “Deploy with one click to secure, scalable infrastructure powered by Vercel.”
   • [claimed-docs] “Go live instantly with one-click deployment to production in seconds.”
   • [claimed-docs] “When multiple chats share a Project, deploying from any of them updates the same production URL.”
   • [claimed-docs] “One Project shares deployment, hosting, domains, and environment variables for the chats connected to it.”
   • [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”

   proof ↗⚑ flag

Agent integration

1. ai-native userConnect my own coding agent to the project so it drives the builder alongside or instead of the built-in one

   weight 2 · round to v0
   Bolt.new—none0/10

   Evidence shows Bolt connecting outward to GitHub/MCP servers as a client (e.g., bolt-docs-18, bolt-docs-40) and offers its own built-in Standard/Max agents (bolt-docs-38), but there is no documentation or API allowing an external coding agent to connect to and drive the Bolt builder itself. Missing for 10: any API/CLI/agent-control interface for external agents to operate the builder, evidence of third-party agent integration replacing Bolt's own agent.

   • [claimed-docs] “Bolt offers two agents, Standard and Max, powered by large language models.”
   • [claimed-docs] “Bolt also offers a GitHub MCP connector for tasks like searching code, pulling in issues, and reviewing discussions.”
   • [claimed-docs] “Connect to GitHub to let Bolt read or create issues and pull requests”

   proof ↗⚑ flag

   v0~partialclaimed3/10

   The v0 API/SDK exposes programmatic access to v0's generation capabilities (e.g. v0.chats.create()) and GitHub integration for code sync, which could let an external tool or script drive v0 programmatically, but there is no evidence of a documented way to plug a third-party coding agent (e.g. Claude Code, Cursor) into a v0 project to replace or run alongside the built-in agent inside the builder UI. Missing for 10: explicit 'bring your own agent' support, agent-swap or multi-agent orchestration inside a v0 project, and any first-party or community confirmation of this working end-to-end.

   • [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
   • [claimed-docs] “Custom chat interfaces - Build your own UI for v0's AI-powered code generation”
   • [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
   • [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
   • [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”

   proof ↗⚑ flag

Code editing

1. developerOpen and edit the generated source code directly inside the builder

   weight 2 · round to Bolt.new
   Bolt.new✓fullclaimed9/10

   Bolt's docs clearly document a Code view where developers can view and directly edit the raw generated code, free of token cost, alongside source control integration for syncing changes. This is well documented across multiple first-party docs pages describing the exact capability requested. Missing for 10: independent hands-on confirmation of code-view editing specifically (community evidence focuses on prompting/iteration rather than manual code editing experience).

   • [claimed-docs] “edit your code directly in code view”
   • [claimed-docs] “you can still make direct edits to your project's existing code for free in Code view, which doesn't use tokens”
   • [claimed-docs] “Choose your languages and frameworks, connect to source control, and edit your code directly in code view.”
   • [claimed-docs] “connect to source control, and edit your code directly in code view”
   • [claimed-docs] “Code view allows you to view the raw code behind your project.”

   proof ↗⚑ flag

   v0—none0/10

   The evidence pack describes visual controls, live preview, GitHub push/pull, and export capabilities, but never explicitly confirms an in-builder code editor where developers can directly view and edit the generated source files. Missing for 10: explicit documentation or screenshot of a code/editor pane inside the v0 builder, hands-on confirmation of direct code editing (not just prompting or visual controls).

   • [claimed-docs] “Fine-tune every detail with visual controls and live preview.”
   • [claimed-docs] “Connect to GitHub and push code directly to your repository.”
   • [claimed-docs] “Export capabilities for backup and migration”

   proof ↗⚑ flag

Preview

1. founderInteract with a live preview of my app while building, before publishing

   weight 2 · round drawn
   Bolt.new✓fullclaimed8/10

   Bolt provides a live preview alongside chat/code editing, including 'Visual edits' that let founders change appearance directly in the preview before publishing, plus Code view and Plan Mode for iterating pre-publish. Missing for 10: independent hands-on confirmation specifically of the live preview UX (most community evidence is about final output quality/breakage rather than the preview interaction itself), and no detail on preview refresh/latency behavior.

   • [claimed-docs] “Visual edits let you change how your project looks directly in the preview.”
   • [claimed-docs] “Code view allows you to view the raw code behind your project.”
   • [claimed-docs] “Bolt has a chat mode called Plan Mode where you can plan and ask questions without making changes to your code.”
   • [claimed-docs] “Build your first website or app with Bolt: no code required.”
   • [claimed-docs] “you choose whether your site is visible to everyone on the web (public) or only to your team and other people you invite (private)”

   proof ↗⚑ flag

   v0✓fullcommunity8/10

   v0's docs explicitly describe live preview with visual controls while iterating ('Fine-tune every detail with visual controls and live preview') and preview deployments built from working branches before publishing, matching the founder's need to see a live app preview pre-publish. Community evidence corroborates rapid build-to-preview workflows, though it's not preview-specific. Missing for 10: independent hands-on account specifically describing the live-preview interaction (vs generation speed) and detail on preview fidelity/limitations.

   • [claimed-docs] “Fine-tune every detail with visual controls and live preview.”
   • [claimed-docs] “Preview deployments are built from working branches.”
   • [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”

   proof ↗⚑ flag

Prompt iteration

1. founderRefine my app through follow-up prompts without breaking what already works

   weight 3 · round to v0
   Bolt.new!disputedcontradicted4/10

   Bolt offers features that support iterative refinement (Plan Mode for planning without code changes, Code view/direct edits, GitHub backup for version history, Skills for reusable instructions), but concrete hands-on reports directly contradict the 'without breaking what already works' promise: one founder reports Bolt's AI made unauthorized changes that removed a security layer and killed payment functionality, and another describes a recurring 'doom loop where there is a cycle of breakage, each fix resurrecting a previous break,' with users advising to revert rather than try to fix in place. missing for 10: first-party evidence of safe-iteration mechanisms like automatic checkpoints/rollback specifically preventing regressions, and independent confirmation that follow-up prompts reliably preserve prior functionality.

   • [claimed-docs] “Bolt has a chat mode called Plan Mode where you can plan and ask questions without making changes to your code.”
   • [claimed-docs] “Code view allows you to view the raw code behind your project.”
   • [claimed-docs] “Connecting GitHub to Bolt lets you automatically back up your Bolt project with a full history of changes that lives outside Bolt.”
   • [claimed-docs] “Skills are reusable instructions that teach Bolt how to handle specific scenarios.”
   • [community] “Bolt.new's AI burned 10M tokens on unauthorized changes... removed critical systems like my FingerprintJS security layer without asking... T…”
   • [community] “I've tried several proof of concepts with Bolt and every time just get into a doom loop where there is a cycle of breakage, each 'fix' resur…”
   • [community] “was quite impressed after building my label maker application and stylex playground. Had some real world needs and both were built in bolt w…”

   proof ↗⚑ flag

   v0~partialcommunity5/10

   v0 supports iterative refinement (chat-based prompts, automatic error fixing, isolated branches, project structure preserving deployment/config) and community reports confirm fast, incremental build-to-deploy cycles, but no evidence explicitly addresses preserving existing functionality across follow-up prompts or preventing regressions. missing for 10: explicit regression-safety guarantees, hands-on evidence that follow-up prompts don't break prior working features, independent testing of iterative stability.

   • [claimed-docs] “Automatically fix errors in your code with intelligent diagnostics.”
   • [claimed-docs] “v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
   • [claimed-docs] “You can connect multiple chats to the same Project. This is useful when working different parts of one Project”
   • [claimed-docs] “One Project shares deployment, hosting, domains, and environment variables for the chats connected to it.”
   • [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”

   proof ↗⚑ flag

Visual editing

1. designerSelect an element and edit its text, style, or layout directly without a prompt round-trip

   weight 2 · round to Bolt.new
   Bolt.new~partialclaimed6/10

   Bolt's Visual Edits feature lets users change how a project looks directly in the preview without prompting [bolt-docs-44], and Code view supports direct manual edits [bolt-docs-45, bolt-docs-3]. However, evidence doesn't confirm true element-select-and-edit for layout/structure (not just style) or independent hands-on validation of Visual Edits' scope. missing for 10: independent/community confirmation of Visual Edits reliability, detail on whether layout (not just style/text) is editable via the visual UI, and any limitations noted by users.

   • [claimed-docs] “Visual edits let you change how your project looks directly in the preview.”
   • [claimed-docs] “Code view allows you to view the raw code behind your project.”
   • [claimed-docs] “you can still make direct edits to your project's existing code for free in Code view, which doesn't use tokens”

   proof ↗⚑ flag

   v0~partialclaimed3/10

   v0.app claims 'Fine-tune every detail with visual controls and live preview' (v0-docs-7), suggesting some direct-manipulation UI, but nearly all other documentation describes chat/prompt-driven generation and iteration cycles rather than click-to-select element editing. Missing for 10: explicit documentation or demo of selecting an element on canvas and editing its text/style/layout inline, independent corroboration that this bypasses the prompt loop, and detail on what 'visual controls' actually cover.

   • [claimed-docs] “Fine-tune every detail with visual controls and live preview.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to v0
   Bolt.new—none0/10

   There is no evidence Bolt.new exposes any public API at all — probes for OpenAPI/swagger endpoints all returned 404, and all documented capabilities (code view, GitHub sync, Figma import, Supabase, hosting, collaboration) are described only as UI/chat features. No documentation mentions a REST/GraphQL API, CLI, or SDK that would let an AI-native user replicate UI actions programmatically.

   • [probe] “PROBE openapi: all candidate paths 404 (https://support.bolt.new/openapi.json, https://support.bolt.new/swagger.json, https://support.bolt.n…”
   • [claimed-docs] “edit your code directly in code view”
   • [claimed-docs] “Choose your languages and frameworks, connect to source control, and edit your code directly in code view.”
   • [claimed-docs] “Bolt offers two agents, Standard and Max, powered by large language models.”

   proof ↗⚑ flag

   v0~partialclaimed5/10

   v0 explicitly claims the API gives 'programmatic access to all of v0's capabilities' including chat, project management, and deployment (v0-docs-4), backed by SDK examples (v0-gh-1/2/3) and API docs on GitHub import and export (v0-docs-37, v0-docs-43). However, many UI-specific workflows (Figma/screenshot cloning, CI/conflict-fix buttons, command palette search, iOS app, visual style controls) are only documented as UI features with no API equivalent shown, and no independent test confirms true 1:1 parity. missing for 10: API-exposed equivalents for design import (Figma/screenshots), GitHub PR/CI-fix actions, and independent verification that API surface matches UI feature set.

   • [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
   • [claimed-docs] “GitHub integration for repository imports”
   • [claimed-docs] “Export capabilities for backup and migration”
   • [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
   • [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
   • [claimed-docs] “Custom chat interfaces - Build your own UI for v0's AI-powered code generation”
   • [claimed-docs] “Clone pages with screenshots or Figma files”
   • [claimed-docs] “open the branch menu and select Fix Conflicts, Fix CI, or Fix CI + Conflicts.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Bolt.new
   Bolt.new~partialclaimed6/10

   Bolt lets users connect/export projects to GitHub with full commit history and edit raw code in Code view, letting a user leave with their code in an open, standard format (bolt-docs-2, bolt-docs-4, bolt-docs-30, bolt-docs-35, bolt-docs-45). However there's no documented mechanism to export other data such as chat/prompt history, project metadata, database contents beyond using Supabase, or account data in a single open bundle. Missing for 10: full account/data export beyond code (chat history, prompt library, non-Supabase DB export), independent confirmation that exported repos are fully self-contained with no bolt.new lock-in.

   • [claimed-docs] “Connect a GitHub repository to back up your Bolt project, sync commits automatically, and work across branches.”
   • [claimed-docs] “Import a GitHub repository. Load an existing repository as a Bolt project.”
   • [claimed-docs] “Create a new repository from a Bolt project”
   • [claimed-docs] “Connecting GitHub to Bolt lets you automatically back up your Bolt project with a full history of changes that lives outside Bolt.”
   • [claimed-docs] “Code view allows you to view the raw code behind your project.”
   • [claimed-docs] “Bolt makes it easy to add database functionality to your app without the hassle of extra infrastructure.”
   • [claimed-docs] “Use Supabase with Bolt to add a database, authentication, or edge functions to your app as an alternative to Bolt Database.”

   proof ↗⚑ flag

   v0~partialclaimed5/10

   v0 lets users push/export generated code to GitHub in a standard, open format (docs-2, docs-31, docs-39), and the API docs mention generic 'Export capabilities for backup and migration' (docs-43), supporting a degree of data portability. However there's no concrete evidence of exporting full account data (chat history, project settings, credentials) in open formats, and no independent confirmation the export path is complete or lock-in-free. Missing for 10: evidence of exporting non-code data (chats, project metadata, integrations config), a documented full-account export/download feature, and independent verification that migrated projects run outside v0/Vercel without further dependency.

   • [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
   • [claimed-docs] “Connect to GitHub and push code directly to your repository.”
   • [claimed-docs] “work on isolated branches, preview changes, run CI, and publish through pull requests”
   • [claimed-docs] “Export capabilities for backup and migration”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Bolt.new
   Bolt.new~partialclaimed3/10

   The evidence confirms a public GitHub repository (stackblitz/bolt.new) exposing the product's source and describing its capabilities, suggesting some source-level openness, but no citation states an explicit open-source license (e.g., MIT, Apache) governing that code. Missing for 10: explicit license file/statement, confirmation that the full product (not just a subset) is covered, and independent confirmation of license terms.

   • [github] “Install and run npm tools and libraries (like Vite, Next.js, and more) Run Node.js servers”
   • [github] “Bolt.new gives AI models complete control over the entire environment including the filesystem, node server, package manager, terminal, and …”
   • [github] “Install and run npm tools and libraries (like Vite, Next.js, and more) - Run Node.js servers - Interact with third-party APIs - Deploy…”
   • [github] “Install and run npm tools and libraries (like Vite, Next.js, and more)”

   proof ↗⚑ flag

   v0—none0/10

   v0 is a closed, proprietary hosted product (with an SDK client library on GitHub, not the core product source); there is no evidence the v0 application/model itself is released under an open license. missing for 10: any statement of an open-source license for v0's core product/source code.

   ⚑ flag

Pricing

1. founderUnderstand what credits or tokens each action consumes and what my plan includes

   weight 2 · round to Bolt.new
   Bolt.new~partialcommunity3/10

   Docs mention that code-view edits are free (no tokens) and that additional tokens can be purchased, but there is no clear breakdown of how many tokens each specific AI action costs or what token allotments come with each plan tier. Community reports of running out of free tokens mid-project and of the AI 'burning 10M tokens' on unauthorized changes suggest actual consumption is unpredictable and not well understood by users. missing for 10: per-action token cost table, plan-tier token allotments, first-party pricing page detail, and independent confirmation that users can predict usage.

   • [claimed-docs] “you can still make direct edits to your project's existing code for free in Code view, which doesn't use tokens”
   • [claimed-docs] “you can purchase additional tokens by following the steps below”
   • [community] “attempted to create a react app to plan meals... a functional app to edit ingredients, recipes and mealplans without data persistence that w…”
   • [community] “Bolt.new's AI burned 10M tokens on unauthorized changes... removed critical systems like my FingerprintJS security layer without asking... T…”

   proof ↗⚑ flag

   v0!disputedcontradicted5/10

   Docs describe a credits/plan system (Premium $20/month, shared credit pools, ability to buy more credits) and even flag one action as token-free (v0-docs-10, v0-docs-23, v0-docs-42, v0-docs-25), but no documentation breaks down per-action credit costs. A hands-on community report contradicts the idea that users can predict consumption, describing unexpectedly high usage-based costs (~$50 in a weekend, '>$20/day') versus flat subscription alternatives (v0-comm-3), showing the credit model is opaque in practice. missing for 10: a clear per-action credit/token cost table, first-party UI showing real-time credit usage, and corroborating community confirmation that costs are predictable.

   • [claimed-docs] “You can buy more credits any time (Premium, Plus, and Business plans).”
   • [claimed-docs] “Premium: $20/month. For higher limits and power users.”
   • [claimed-docs] “Shared Credit Pool credits are shared among all team members”
   • [claimed-docs] “Start with existing files (fast, no tokens)”
   • [community] “Cost complaint: 'V0 is pay by usage... we talking > +$20/day vs $XX/month' for a subscription-based alternative like Copilot; spent about $5…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Bolt.new—none0/10

   No evidence in the pack mentions data residency, regional storage options, or compliance controls for choosing where data is stored; Bolt's docs cover hosting, database, and integrations but never address data-location choice.

   ⚑ flag

   v0—none0/10

   No evidence in the pack mentions data residency, regional storage options, or any data-location controls for v0; the docs focus on code generation, deployment, GitHub integration, and pricing, none of which address where data is stored.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Bolt.new—none0/10

   No evidence in the pack addresses AI training data opt-out, data usage policies, or privacy controls related to model training on user data; all evidence covers unrelated features like integrations, hosting, and collaboration.

   ⚑ flag

   v0—none0/10

   No evidence in the pack addresses data-training opt-out, privacy controls, or any statement about whether user data/code is used to train AI models; nothing mentions a privacy policy toggle or enterprise no-training guarantee.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Bolt.new—none0/10

   No evidence pack items address data retention policies, data deletion controls, or privacy settings for user data/projects; documentation covers hosting, collaboration, integrations, and agent features but nothing about retention/deletion controls.

   ⚑ flag

   v0—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or privacy settings for user data/chats/projects in v0; only export capabilities for backup/migration are mentioned, which is unrelated to retention/deletion control. Missing for 10: documented data retention policy, user-facing deletion/export-of-data controls, opt-out of training data usage, any privacy/compliance documentation.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Bolt.new—none0/10

   No evidence pack item mentions telemetry, analytics opt-out, or usage-tracking controls for Bolt.new; documentation covers integrations, hosting, agents, and collaboration but is silent on privacy/telemetry settings.

   ⚑ flag

   v0—none0/10

   No evidence pack item mentions telemetry, analytics opt-out, or usage tracking controls for v0; nothing addresses privacy settings of this kind.

   ⚑ flag

Design import

1. designerImport a Figma file or existing design and have the builder implement it

   weight 2 · round to Bolt.new
   Bolt.new✓fullclaimed8/10

   Bolt has a dedicated Figma integration that loads Figma frames/designs and generates working UIs, including a design-system agent that recreates frames using real design system components, plus similar import support for Google Stitch designs. Missing for 10: independent/hands-on evidence of Figma import fidelity and no detail on handling complex multi-page files.

   • [claimed-docs] “you can quickly load Figma designs into Bolt, and generate sites and UIs based on the designs”
   • [claimed-docs] “adding a design system can help build your Figma frames into working webpages”
   • [claimed-docs] “Using Bolt's Figma integration, you can quickly load Figma designs into Bolt, and generate sites and UIs based on the designs.”
   • [claimed-docs] “Bolt's design system agent processes the frame and recreates it using your real design system components.”
   • [claimed-docs] “you can quickly load Figma designs into Bolt, and generate sites and UIs based on the designs.”
   • [claimed-docs] “Anyone can start from a blank prompt, upload files to build with, or import designs from Figma or Google Stitch.”
   • [claimed-docs] “Export your Google Stitch designs to Bolt and build them into a fully functional app.”

   proof ↗⚑ flag

   v0~partialclaimed6/10

   Docs explicitly claim ability to 'Clone pages with screenshots or Figma files' and 'Create high-fidelity UIs from your wireframes or mockups,' directly supporting the story, but this is first-party doc text only with no workflow detail, screenshots, or independent hands-on confirmation of Figma import fidelity. Missing for 10: detailed Figma import workflow documentation, independent/community verification that Figma import works as claimed, and coverage of fidelity/limitations when translating Figma designs to code.

   • [claimed-docs] “Clone pages with screenshots or Figma files”
   • [claimed-docs] “Create high-fidelity UIs from your wireframes or mockups.”
   • [claimed-docs] “Turn mockups into real, high-fidelity user interfaces that reflect user flows and constraints.”

   proof ↗⚑ flag

Generation

1. developerGenerate both frontend UI and backend logic from a single prompt

   weight 3 · round to v0
   Bolt.new~partialcommunity6/10

   Bolt.new documents generating full frontend UIs (Vite/Next.js) plus backend logic via Node servers, third-party API integration, and database/auth via Bolt Database or Supabase, and community reports confirm working full-stack apps (e.g., meal-planner with persistence) built from prompts alone [bolt-gh-1][bolt-gh-3][bolt-docs-33][bolt-docs-27][bolt-comm-4]. However, backend depth is largely delegated to a third-party service (Supabase) rather than fully custom logic, and hands-on reports cite backend breakage, doom-loop failures, and unauthorized removal of critical backend systems [bolt-comm-11][bolt-comm-9][bolt-comm-7]. Missing for 10: independent verification of complex custom backend logic beyond Supabase/Stripe integrations, and resolution of reported reliability issues with backend generation.

   • [github] “Install and run npm tools and libraries (like Vite, Next.js, and more) Run Node.js servers”
   • [github] “Install and run npm tools and libraries (like Vite, Next.js, and more) - Run Node.js servers - Interact with third-party APIs - Deploy…”
   • [claimed-docs] “Bolt makes it easy to add database functionality to your app without the hassle of extra infrastructure.”
   • [claimed-docs] “If you prefer to use Supabase when creating a new project, you can select it during setup.”
   • [claimed-docs] “if you already have a Supabase account connected and need more advanced database features or tighter control over your data, choosing Supaba…”
   • [community] “attempted to create a react app to plan meals... a functional app to edit ingredients, recipes and mealplans without data persistence that w…”
   • [community] “Lovable and bolt took a massive shortcut: they outsourced the backend to a third party (supabase). This makes their ceiling to build 'useful…”
   • [community] “I've tried several proof of concepts with Bolt and every time just get into a doom loop where there is a cycle of breakage, each 'fix' resur…”
   • [community] “Bolt.new's AI burned 10M tokens on unauthorized changes... removed critical systems like my FingerprintJS security layer without asking... T…”

   proof ↗⚑ flag

   v0✓fullcommunity8/10

   v0 docs and community evidence show single-prompt generation of both frontend UI and connected backend logic (databases, auth, Supabase/Neon/Upstash integrations) plus full-stack scaffolding and deployment, corroborated by a hands-on HN report of building a full app with auth/roles/export from prompt to deployed MVP. missing for 10: no controlled benchmark of backend logic correctness/robustness, and no independent review specifically validating backend code quality (community feedback focuses mostly on UI generation and cost).

   • [claimed-docs] “Quickly scaffold full-stack apps or components following best practices and modern standards.”
   • [claimed-docs] “Connect to backend to build rich, data driven applications.”
   • [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase, and AI mod…”
   • [claimed-docs] “v0 plans, creates tasks, and connects to databases as it builds.”
   • [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase”
   • [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”

   proof ↗⚑ flag

2. founderDescribe an app in natural language and get a working full-stack application

   weight 3 · round to v0
   Bolt.new!disputedcontradicted6/10

   Bolt's docs and product clearly support prompt-to-app generation with built-in database, auth, hosting, and deployment (bolt-docs-31, bolt-docs-33, bolt-docs-32, bolt-gh-3), and multiple community testimonials confirm fast working builds (bolt-comm-3, bolt-comm-4, bolt-comm-10). However, concrete hands-on reports contradict reliable full-stack delivery: users describe 'doom loop' cycles of breakage where fixes resurrect prior bugs (bolt-comm-9), and one detailed account describes the AI making unauthorized changes that broke critical security and payment systems in a deployed app (bolt-comm-7). Missing for 10: consistent reproducibility across complex apps, resolution of the doom-loop/breakage pattern, and vendor response addressing these failures.

   • [claimed-docs] “Build your first website or app with Bolt: no code required.”
   • [claimed-docs] “Bolt makes it easy to add database functionality to your app without the hassle of extra infrastructure.”
   • [claimed-docs] “Bolt offers built-in hosting, so you can publish your Bolt project for free at a web address ending in `bolt.host`.”
   • [github] “Install and run npm tools and libraries (like Vite, Next.js, and more) - Run Node.js servers - Interact with third-party APIs - Deploy…”
   • [community] “i've seen people literally go from idea to prod in a day when it normally would take a week. Mind blowing.”
   • [community] “attempted to create a react app to plan meals... a functional app to edit ingredients, recipes and mealplans without data persistence that w…”
   • [community] “was quite impressed after building my label maker application and stylex playground. Had some real world needs and both were built in bolt w…”
   • [community] “I've tried several proof of concepts with Bolt and every time just get into a doom loop where there is a cycle of breakage, each 'fix' resur…”
   • [community] “Bolt.new's AI burned 10M tokens on unauthorized changes... removed critical systems like my FingerprintJS security layer without asking... T…”

   proof ↗⚑ flag

   v0✓fullprobed8/10

   Docs and API show natural-language-to-app generation, full-stack scaffolding, backend/database integrations, and one-click deployment (v0-docs-15, v0-docs-24, v0-docs-28, v0-docs-32, v0-gh-1). A first-hand community report confirms a working MVP built and deployed quickly from a prompt (v0-comm-1). Missing for 10: broader independent benchmarking on complex, non-trivial apps and evidence addressing the noted design-sameness limitation (v0-comm-4).

   • [claimed-docs] “Quickly scaffold full-stack apps or components following best practices and modern standards.”
   • [claimed-docs] “Connect to backend to build rich, data driven applications.”
   • [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase, and AI mod…”
   • [claimed-docs] “Go live instantly with one-click deployment to production in seconds.”
   • [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
   • [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”
   • [probe] “PROBE docs-md: HTTP 200 at https://v0.app/docs.md --- title: What is v0? description: v0 is an AI agent that helps anyone create real code a…”

   proof ↗⚑ flag

Programmatic generation

1. ai-native userGenerate and manage apps programmatically through a platform API

   weight 3 · round to v0
   Bolt.new—none0/10

   No evidence of a public/programmatic API for creating or managing Bolt projects; the OpenAPI probe returned 404 on all candidate endpoints, and all documented capabilities (chat, code view, GitHub sync, MCP connector) are UI/agent-driven rather than API-driven.

   • [probe] “PROBE openapi: all candidate paths 404 (https://support.bolt.new/openapi.json, https://support.bolt.new/swagger.json, https://support.bolt.n…”
   • [claimed-docs] “Bolt also offers a GitHub MCP connector for tasks like searching code, pulling in issues, and reviewing discussions.”
   • [claimed-docs] “Connect to GitHub to let Bolt read or create issues and pull requests”

   proof ↗⚑ flag

   v0✓fullclaimed8/10

   v0 documents a platform API that gives programmatic access to chat/code generation, project management, and deployment (v0-docs-4), and the official v0-sdk on GitHub shows concrete code for creating chats and streaming results with API-key auth (v0-gh-1, v0-gh-2, v0-gh-3), directly matching the 'generate and manage apps programmatically' story. Missing for 10: independent/hands-on corroboration of the API in production use and more detail on full app lifecycle management (list/delete/update) via the API beyond chat creation.

   • [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
   • [claimed-docs] “Custom chat interfaces - Build your own UI for v0's AI-powered code generation”
   • [claimed-docs] “Start with existing files (fast, no tokens)”
   • [claimed-docs] “GitHub integration for repository imports”
   • [claimed-docs] “Export capabilities for backup and migration”
   • [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
   • [github] “const result = readV0Stream(serverResult.toResponse())”
   • [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”

   proof ↗⚑ flag

Templates

1. founderStart from a template or community project instead of a blank prompt

   weight 2 · round to Bolt.new
   Bolt.new~partialclaimed7/10

   Bolt lets founders start from something other than a blank prompt: import a GitHub repo, import a Lovable project, load Figma or Google Stitch designs, or upload files (bolt-docs-4,5,6,7,49). However there's no evidence of a curated template gallery or a browsable community-project marketplace like some competitors offer. missing for 10: a dedicated templates/starter gallery, evidence of browsing/forking community-submitted projects.

   • [claimed-docs] “Import a GitHub repository. Load an existing repository as a Bolt project.”
   • [claimed-docs] “Import from Lovable. Bring a Lovable project into Bolt.”
   • [claimed-docs] “you can quickly load Figma designs into Bolt, and generate sites and UIs based on the designs”
   • [claimed-docs] “Export your Google Stitch designs to Bolt and build them into a fully functional app.”
   • [claimed-docs] “Anyone can start from a blank prompt, upload files to build with, or import designs from Figma or Google Stitch.”
   • [claimed-docs] “Build your first website or app with Bolt: no code required.”

   proof ↗⚑ flag

   v0~partialcommunity4/10

   v0 supports starting from existing code via 'Import from GitHub' and 'Start with existing files (no tokens)', which lets founders begin from a pre-existing project rather than a blank prompt, and community testimony confirms it solves the 'blank canvas problem'. However there is no evidence of a curated template gallery or a community-project showcase/marketplace to browse and remix, which is the core of the story. Missing for 10: a dedicated template/starter gallery, community project discovery or remix feature, and evidence of founders actually starting from such templates.

   • [claimed-docs] “To start from code already on GitHub, use Import from GitHub.”
   • [claimed-docs] “To start from code already on GitHub, use Import from GitHub. Importing creates a chat at the selected base branch”
   • [claimed-docs] “Start with existing files (fast, no tokens)”
   • [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”

   proof ↗⚑ flag