Bolt.new vs Floot

Agent access

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

   weight 2 · round drawn
   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

   Floot✓fullprobed8/10

   Floot serves a live llms.txt (HTTP 200) and an llms-full.txt with agent-oriented documentation of its capabilities, confirmed by direct probes. missing for 10: independent third-party confirmation that agents actually consume and act on these docs successfully, and docs.md/openapi endpoints return 404 suggesting the agent-doc surface is limited to llms.txt only.

   • [probe] “PROBE llms.txt: HTTP 200 at https://floot.com/llms.txt # Floot > Floot turns a plain-language description into a real, deployed full-stack …”
   • [claimed-docs] “point at an element or annotate a screenshot for the assistant to pick up”
   • [probe] “PROBE docs-md: HTTP 404 at https://floot.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Floot—none0/10

   Floot is a chat-based/MCP-driven app builder with no evidence of a CLI, API, or headless mode for CI/automation pipelines; MCP integration is for interactive AI clients (Cursor, VS Code, Zed), not headless CI execution. No mention of scripted builds, CI/CD triggers, or non-interactive automation. Missing for 10: CLI or SDK for scripted invocation, CI/CD pipeline documentation, headless build/deploy commands, API endpoints for automation.

   ⚑ 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

   Floot—none0/10

   All evidence describes Floot exposing itself as an MCP server that other clients (Cursor, VS Code, Zed) can connect to and use its tools (get_logs, query_database, etc.) — the reverse direction of this story. There is no evidence that a user can plug external MCP servers into Floot so Floot's own AI can call their tools.

   • [claimed-docs] “Add Floot to Cursor, VS Code, Zed, or any client that supports remote MCP servers”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”

   proof ↗⚑ 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

   Floot—none0/10

   Floot is a chat/browser-based app builder that offers an MCP server for connecting external AI clients, but there is no evidence of an official CLI tool for AI-native workflows; all evidence points to MCP integration and web-based chat, not a CLI. Missing for 10: any mention of a CLI binary, npm/pip install, or command-line docs.

   • [claimed-docs] “Add Floot to Cursor, VS Code, Zed, or any client that supports remote MCP servers”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”

   proof ↗⚑ flag

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

   weight 3 · round to Floot
   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

   Floot~partialprobed7/10

   Floot documents a first-party MCP server exposing concrete tools (get_logs, query_database, execute_sql, create_checkpoint, generate_image) that let an AI client drive the product programmatically, which directly serves the AI-native persona. However, probes show no conventional public REST/OpenAPI API (openapi.json/swagger.json all 404, docs.md 404), so the 'documented public API' story is only satisfied via the MCP protocol rather than a broader API surface. Missing for 10: a traditional REST/OpenAPI-documented API or SDK, and independent confirmation of MCP tool reliability beyond vendor docs.

   • [claimed-docs] “Add Floot to Cursor, VS Code, Zed, or any client that supports remote MCP servers”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “generate_image writes AI images into the project.”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”
   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://floot.com/docs.md”

   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

   Floot—none0/10

   No evidence Floot supports issuing scoped or least-privilege API credentials/tokens for agents; MCP integration docs describe tool capabilities (query_database, execute_sql, etc.) but nothing about credential scoping, permission levels, or least-privilege access control for agents. missing for 10: any mention of API keys, token scoping, permission tiers, or credential management for agent access.

   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   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

   Floot—none0/10

   Floot exposes an MCP server with tool functions (get_logs, query_database, execute_sql, etc.) but there is no evidence of official language SDKs (e.g., npm/pip packages) or an OpenAPI spec for developers to build against programmatically; probes for openapi.json/swagger.json all 404.

   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://floot.com/docs.md”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”

   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

   Floot—none0/10

   No evidence pack item mentions webhooks, event subscriptions, or any outbound notification/event system that AI-native users could subscribe to; the docs cover database, logs, images, mobile apps, and MCP tooling but nothing about webhooks.

   ⚑ 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

   Floot—none0/10

   Floot's docs show built-in analytics tracking (page views, traffic sources, trends) and AI tools that can query/execute against the app's database, but there is no evidence the AI surfaces proactive insights or suggestions derived from that data back to the user — the query/execute tools are for development/debugging, not analytical insight generation.

   • [claimed-docs] “Built-in visitor tracking: page views, traffic sources, and trends.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”

   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

   Floot—none0/10

   Floot's evidence covers app-building tools (database queries, logs, checkpoints, image generation, MCP integration) but nothing about scheduled tasks, triggers, or autonomous background automations running independently of a chat session. There is no mention of cron-like jobs, webhooks-as-triggers, or agent workflows executing without user interaction.

   ⚑ 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

   Floot✓fullprobed8/10

   Floot's core product is an AI chat assistant that builds, debugs, queries databases, generates images, and manages checkpoints for the app directly from the chat interface, with tool actions like get_logs, query_database, generate_image documented. missing for 10: independent/hands-on corroboration beyond vendor docs, and clearer detail on task complexity/limits the assistant can handle autonomously.

   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “point at an element or annotate a screenshot for the assistant to pick up”
   • [claimed-docs] “generate_image writes AI images into the project.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://floot.com/llms.txt # Floot > Floot turns a plain-language description into a real, deployed full-stack …”

   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

   Floot✓fullprobed8/10

   Floot's core product is natural-language chat-based app building ('build and ship full-stack apps without leaving your AI chat', 'turns a plain-language description into a real, deployed full-stack app'), with rich agentic tool support (get_logs, query_database, create_checkpoint, generate_image) operable via NL commands. Missing for 10: independent/hands-on corroboration beyond vendor docs, and no detail on limits of NL command coverage for advanced operations.

   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”
   • [probe] “PROBE llms.txt: HTTP 200 at https://floot.com/llms.txt # Floot > Floot turns a plain-language description into a real, deployed full-stack …”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “generate_image writes AI images into the project.”

   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

   Floot—none0/10

   There is no evidence of an interactive API reference or runnable examples; probes explicitly show no OpenAPI/Swagger docs (404s) and no docs.md, and the MCP tool docs are plain text descriptions without runnable playgrounds.

   • [probe] “PROBE docs-md: HTTP 404 at https://floot.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”

   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

   Floot—none0/10

   Direct probes for OpenAPI/Swagger specs all returned 404 at every candidate path, and no documentation mentions a machine-readable API spec for Floot's own platform API.

   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://floot.com/docs.md”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   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

   Floot—none0/10

   Evidence shows database tools (query_database, execute_sql) and checkpoint/revert features, but nothing describes a separate sandbox/staging environment isolated from production data — checkpoints revert code state, not provide a parallel test database. Missing for 10: any mention of a staging/sandbox database, environment cloning, or explicit separation between test and production data.

   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”

   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

   Floot—none0/10

   No evidence of any versioned API or documented deprecation policy; OpenAPI probes returned 404 and no changelog/docs mention API versioning or deprecation practices. missing for 10: versioned API documentation, deprecation policy statement, API stability guarantees.

   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”
   • [probe] “PROBE docs-md: HTTP 404 at https://floot.com/docs.md”

   proof ↗⚑ 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

   Floot—none0/10

   Floot's evidence covers single-app database queries/writes (query_database, execute_sql) and other AI-assisted dev tools, but nothing describes bulk operations across many items/records/projects at once as a distinct capability. missing for 10: any documentation of batch/bulk editing, mass updates across records, or multi-item automation workflows.

   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”

   proof ↗⚑ 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

   Floot—none0/10

   No evidence anywhere in the pack of scheduled/recurring jobs, cron-like automation, or workflow scheduling features; Floot's documented tools cover logs, database queries, checkpoints, image generation, mobile app conversion, and self-hosting but nothing about recurring or scheduled execution.

   ⚑ flag

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

   weight 1 · round to Bolt.new
   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

   Floot~partialclaimed5/10

   Floot documents a checkpoint system where create_checkpoint labels a revertible point accessible from the Checkpoint panel, covering versioning and rollback of AI-driven changes. However, there is no evidence of a review/diff mechanism to inspect what changed before reverting, nor of a broader automation version history beyond simple checkpoints. Missing for 10: explicit review/diff tooling, multi-version history browsing, and independent confirmation of rollback reliability.

   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”

   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 drawn
   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

   Floot—none0/10

   The evidence shows Floot's builder assistant can call tools like generate_image during app creation, but there is no documentation of end-user apps being able to make LLM calls or run agents with Floot managing the provider API keys on the app's behalf.

   ⚑ 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

   Floot—none0/10

   The evidence pack covers Floot's database, logging, image generation, mobile app conversion, and self-hosting features, but contains no mention of authentication, user sign-up/login scaffolding, or social provider integration. This is a reasonable capability to expect from a full-stack app builder, so its absence is a gap rather than an inapplicable axis.

   ⚑ flag

Database

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

   weight 3 · round to Floot
   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

   Floot✓fullprobed7/10

   Floot documents built-in database tooling (query_database, execute_sql, pull_database_schema) accessible directly through the AI assistant inside the builder, indicating a database is provisioned and wired automatically without leaving the chat/builder. Missing for 10: independent/hands-on confirmation of automatic provisioning flow and details on database type/scaling, and no explicit doc showing the provisioning UX step-by-step.

   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”
   • [probe] “PROBE llms.txt: HTTP 200 at https://floot.com/llms.txt # Floot > Floot turns a plain-language description into a real, deployed full-stack …”

   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

   Floot—none0/10

   No evidence pack item mentions security review, vulnerability scanning, or pre-launch security audits of generated apps; the docs cover logging, database tools, checkpoints, mobile export, and self-hosting but nothing on security review workflows. Missing for 10: any mention of automated security scanning, vulnerability checks, or a review gate before deployment.

   ⚑ flag

Server logic

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

   weight 2 · round drawn
   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

   Floot~partialclaimed6/10

   Floot's docs show database read/write tools (query_database, execute_sql), built-in email sending/receiving, and other backend-like capabilities exposed to the AI builder, indicating server-side functionality can be added conversationally. However, there is no explicit mention of general-purpose custom server-side functions or third-party payment integrations, which are core parts of this story. Missing for 10: explicit payments integration support, generic server-side function/webhook creation beyond DB and email, and independent verification of these integrations working in practice.

   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “Your apps can now send AND receive email — no third-party email service needed.”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”

   proof ↗⚑ flag

Export

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

   weight 3 · round to Floot
   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

   Floot✓fullclaimed8/10

   Floot's docs explicitly state you can export the code and database and deploy them wherever you like, directly matching the story of exporting source and self-hosting outside the platform. Missing for 10: independent/hands-on verification of the export process and details on completeness/portability of exported code beyond the doc claim.

   • [claimed-docs] “you can export the code and the database and deploy them wherever you like.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Floot~partialclaimed5/10

   Floot lets you connect external editors (Cursor, VS Code, Zed) via its remote MCP server, giving access to tools like execute_sql, query_database and create_checkpoint that can modify the live project, and separately lets you export code/database for self-hosting — but there's no documented local file-sync or git-style push workflow; the platform's own framing emphasizes staying in the AI chat rather than local file editing pushed back. missing for 10: explicit local-editor file sync/push mechanism, evidence of two-way git-based workflow, independent confirmation this MCP path is used for real code editing rather than just DB/log operations.

   • [claimed-docs] “Add Floot to Cursor, VS Code, Zed, or any client that supports remote MCP servers”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “you can export the code and the database and deploy them wherever you like.”
   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”

   proof ↗⚑ flag

Git sync

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

   weight 3 · round to Bolt.new
   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

   Floot—none0/10

   The evidence pack shows Floot supports exporting code/database for self-hosting, but there is no mention of a GitHub integration or bidirectional repo sync anywhere in the docs, changelog, or probes.

   • [claimed-docs] “you can export the code and the database and deploy them wherever you like.”

   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

   Floot—none0/10

   No evidence in the pack mentions multi-user workspaces, team member invites, roles/permissions, or shared project collaboration features. Evidence focuses on AI chat tooling, MCP integration, mobile app conversion, self-hosting, and checkpoints, none of which speak to teams working together in a shared workspace.

   ⚑ 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

   Floot—none0/10

   No evidence pack item mentions custom domain connection, DNS setup, or domain management for published apps; only deployment-adjacent features like self-hosting export and mobile app conversion are documented.

   ⚑ flag

Publish

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

   weight 1 · round to Floot
   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

   Floot~partialclaimed6/10

   Floot explicitly documents exporting code and database to self-host or deploy elsewhere, directly supporting this story, but details are thin—no evidence of specific export formats, supported hosts, CI/CD, or independent confirmation of a successful external deployment. missing for 10: detailed export/deploy workflow docs, supported infrastructure targets, independent hands-on verification of external hosting.

   • [claimed-docs] “you can export the code and the database and deploy them wherever you like.”

   proof ↗⚑ flag

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

   weight 3 · round to Bolt.new
   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

   Floot~partialprobed6/10

   The llms.txt probe confirms Floot 'turns a plain-language description into a real, deployed full-stack app,' implying deployment is automatic as part of building, and self-hosting docs show apps can be exported/deployed elsewhere. However, there is no explicit documentation of a one-click 'publish' action, custom domain setup, or live URL management workflow. missing for 10: explicit publish/deploy button documentation, custom domain configuration details, confirmation of single-step publishing UX.

   • [probe] “PROBE llms.txt: HTTP 200 at https://floot.com/llms.txt # Floot > Floot turns a plain-language description into a real, deployed full-stack …”
   • [claimed-docs] “you can export the code and the database and deploy them wherever you like.”

   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 Floot
   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

   Floot~partialprobed6/10

   Floot documents an official remote MCP server that can be added to Cursor, VS Code, Zed, or any MCP-capable client, letting an external agent drive builder actions like get_logs, query_database, create_checkpoint, and generate_image — this directly supports connecting an outside coding agent to the project. However, evidence doesn't confirm this fully replaces or runs 'alongside' the built-in agent in real workflows, nor is there independent/hands-on confirmation of external agents successfully driving full builds. missing for 10: hands-on/independent verification of external agent parity with built-in agent, clarity on simultaneous or exclusive control, and any limitations when using third-party clients.

   • [claimed-docs] “Add Floot to Cursor, VS Code, Zed, or any client that supports remote MCP servers”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “generate_image writes AI images into the project.”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”

   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

   Floot—none0/10

   Floot's evidence describes chat/AI-driven building, MCP tool integrations, exporting code for self-hosting, and mobile/app features, but there is no mention of an in-builder code editor for directly viewing/editing generated source code within the product itself.

   ⚑ flag

Preview

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

   weight 2 · round to Bolt.new
   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

   Floot~partialclaimed5/10

   Docs imply an interactive project view where users can 'point at an element or annotate a screenshot' for the AI, and a 'Checkpoint panel in your project view,' suggesting a live, before-publish preview exists — but no evidence explicitly describes a dedicated live-preview pane, its update speed, or founder-facing walkthrough of iterating on it before shipping. missing for 10: explicit live-preview UI documentation, screenshots/demo of pre-publish preview, independent hands-on confirmation.

   • [claimed-docs] “point at an element or annotate a screenshot for the assistant to pick up”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”

   proof ↗⚑ flag

Prompt iteration

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

   weight 3 · round to Floot
   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

   Floot~partialclaimed5/10

   Floot supports checkpoint/revert (floot-docs-5) and chat-based iterative building (floot-docs-1), which are relevant to safely refining an app via follow-up prompts, but there's no direct evidence describing regression prevention, test coverage, or how the assistant avoids breaking existing functionality during edits. missing for 10: evidence of automated regression/testing safeguards, independent hands-on account of iterative prompting not breaking prior features, and detail on how conflicts between old and new instructions are resolved.

   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”

   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

   Floot—none0/10

   Floot's documented workflow is prompt/chat-driven — you 'point at an element or annotate a screenshot for the assistant to pick up' (floot-docs-6), which still requires an AI round-trip rather than direct in-canvas editing of text, style, or layout. No evidence describes a direct-manipulation editor mode for designers to bypass the AI prompt loop.

   • [claimed-docs] “point at an element or annotate a screenshot for the assistant to pick up”
   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”

   proof ↗⚑ flag

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

   weight 2 · round to Floot
   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

   Floot~partialprobed5/10

   Floot exposes a documented MCP server with tools (get_logs, query_database/execute_sql, create_checkpoint, generate_image) that let an AI agent perform many core dev actions, mirroring parts of the UI workflow, but there's no public REST/OpenAPI API (probes return 404 for openapi.json/swagger.json and docs.md), so broader UI features like mobile app packaging, push notifications, email, analytics, and self-hosting export are not confirmed to be reachable via API. missing for 10: a general-purpose REST/OpenAPI API, evidence that all UI-exposed features (mobile builds, notifications, analytics, hosting/export) are also API-accessible, independent confirmation of API parity.

   • [claimed-docs] “Add Floot to Cursor, VS Code, Zed, or any client that supports remote MCP servers”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “generate_image writes AI images into the project.”
   • [probe] “PROBE docs-md: HTTP 404 at https://floot.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Floot~partialclaimed6/10

   Floot documents exporting both code and database for self-hosting elsewhere, directly supporting data portability and leaving the platform, but there's no evidence of a broader open-format export (e.g., structured data exports, account data, media assets) beyond code/DB, nor independent confirmation the export is complete or in fully open standard formats. missing for 10: evidence of full data export scope (assets, user data, configs), independent/hands-on verification of export completeness, and confirmation of open standard formats used.

   • [claimed-docs] “you can export the code and the database and deploy them wherever you like.”

   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

   Floot—none0/10

   Floot is a closed proprietary SaaS platform for generating apps; there is no evidence of Floot's own source code being available under an open license. Evidence only shows users can export generated app code (floot-docs-11), which is not the same as the platform's source being open.

   ⚑ flag

4. ai-native userSelf-host the core product

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

   While a GitHub repository for bolt.new exists (bolt-gh-1–4), the evidence pack contains no documentation, instructions, or claims about deploying/self-hosting the core Bolt.new product on one's own infrastructure — all cited docs describe the hosted SaaS experience (hosting on bolt.host, custom domains, Supabase, etc.). No evidence confirms an official self-host path.

   ⚑ flag

   Floot~partialclaimed5/10

   Floot is a hosted platform (not open-source), but docs confirm you can export project code and database and deploy them wherever you like, giving a path to self-host the exported app outside Floot's infrastructure. This is not self-hosting the core Floot platform/builder itself, just the generated output. Missing for 10: evidence of self-hosting the actual Floot builder/service, open-source availability, or independent confirmation the export-and-deploy path works end-to-end.

   • [claimed-docs] “you can export the code and the database and deploy them wherever you like.”

   proof ↗⚑ 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

   Floot—none0/10

   Only floot-docs-8 mentions a credit system (you can 'add credits whenever you need them'), but there is no documentation of what specific actions consume credits/tokens, how many, or what different plans include — the core of the founder's ask is unaddressed.

   • [claimed-docs] “you no longer have to upgrade or downgrade your plan — just add credits whenever you need them.”

   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

   Floot—none0/10

   No evidence anywhere in the pack mentions data residency, region selection, or hosting location choices; only self-hosting/export is mentioned which does not equate to choosing a storage region within Floot's platform.

   ⚑ 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

   Floot—none0/10

   No evidence pack item mentions AI training data usage, opt-out controls, or data-privacy commitments regarding model training; nothing addresses this axis at all.

   ⚑ 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

   Floot—none0/10

   No evidence pack items describe data retention controls, deletion policies, or privacy/export-of-personal-data mechanisms; export/self-hosting docs cover code/database portability, not retention or deletion settings. missing for 10: retention policy documentation, data deletion controls/API, privacy policy references, account/data purge mechanisms.

   ⚑ 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

   Floot—none0/10

   The evidence pack contains no mention of telemetry opt-out or privacy controls for AI-native usage; it only shows built-in visitor tracking for end-user apps (floot-docs-10), which is unrelated to Floot's own telemetry practices toward its users.

   ⚑ 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

   Floot—none0/10

   No evidence pack item mentions Figma import, design file import, or converting existing designs into a Floot app; the docs focus on chat-based prompting, MCP tools, mobile export, and self-hosting.

   ⚑ flag

Generation

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

   weight 3 · round to Floot
   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

   Floot✓fullprobed8/10

   Floot's own docs describe it as turning a plain-language description into a full-stack app with React+TypeScript frontend and backed by database tools (query_database, execute_sql, pull_database_schema), indicating both UI and backend logic are generated from a single prompt. This is corroborated by the llms.txt probe confirming the core positioning. Missing for 10: independent/hands-on developer confirmation of single-prompt generation quality and no explicit example walkthrough of a prompt producing both layers together.

   • [probe] “PROBE llms.txt: HTTP 200 at https://floot.com/llms.txt # Floot > Floot turns a plain-language description into a real, deployed full-stack …”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “build and ship full-stack apps without leaving your AI chat”

   proof ↗⚑ flag

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

   weight 3 · round to Floot
   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

   Floot✓fullprobed8/10

   Floot's own docs describe turning plain-language descriptions into a deployed full-stack app (React+TypeScript frontend, database, backend tooling like query_database/execute_sql, image generation, mobile app conversion), directly matching the prompt-to-app story, and this is corroborated by a live probe of llms.txt confirming the same positioning. Missing for 10: independent/third-party hands-on reviews validating real-world output quality beyond vendor docs and probes.

   • [probe] “PROBE llms.txt: HTTP 200 at https://floot.com/llms.txt # Floot > Floot turns a plain-language description into a real, deployed full-stack …”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “Floot converts your project into native iOS and Android apps”
   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”

   proof ↗⚑ flag

Programmatic generation

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

   weight 3 · round to Floot
   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

   Floot~partialprobed6/10

   Floot exposes a remote MCP server with tools (get_logs, query_database, execute_sql, generate_image, create_checkpoint) that let an AI client programmatically manage an app's data, logs, and images, which is a form of programmatic control aligned with ai-native/prompt-to-app usage. However, probes show no REST/OpenAPI API (all openapi.json/docs.md paths 404), and there's no evidence of programmatically creating new apps from scratch via API—only managing an existing project through MCP tools. Missing for 10: a documented REST/OpenAPI platform API, evidence of app creation (not just management) via API/MCP, and independent confirmation of these tool calls working end-to-end.

   • [claimed-docs] “get_logs — the first step for any 500, blank page, or failed request.”
   • [claimed-docs] “query_database for reads, execute_sql for writes and migrations, pull_database_schema to regenerate typed helpers.”
   • [claimed-docs] “create_checkpoint labels a point you can revert to from the Checkpoint panel in your project view.”
   • [claimed-docs] “generate_image writes AI images into the project.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://floot.com/openapi.json, https://floot.com/swagger.json, https://floot.com/api/openapi.json, …”
   • [probe] “official MCP server documented at https://floot.com/docs/integrations/other-mcp-clients”

   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

   Floot—none0/10

   No evidence in the pack mentions templates, starter kits, or community project galleries as a starting point for new Floot projects; all docs focus on chat-based generation, MCP integrations, and infrastructure features.

   ⚑ flag