Bolt.new vs Base44

Agent access

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

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

   Base44✓fullprobed9/10

   A probe confirms llms.txt is live at https://docs.base44.com/llms.txt returning HTTP 200 with structured content describing Base44, and the docs site itself is built with agent-friendly .md endpoints for every page (e.g. docs-1 through docs-30 all resolve as .md URLs), showing docs are structured for agent consumption. Missing for 10: no independent/community confirmation that third-party agents have actually consumed llms.txt successfully in the wild.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.base44.com/llms.txt # Base44 Documentation > Base44 is an AI-powered app builder. Describe your id…”
   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal. Create new backend projects, sync data model…”
   • [claimed-docs] “Your entire backend is defined in code and configuration files, making it easy for AI coding agents to build and manage your project.”

   proof ↗⚑ flag

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

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

   Base44~partialprobed5/10

   Base44 offers a CLI (login, create, deploy, sync) and an SDK for programmatic app management, which could be scripted in CI, plus 'bring your own agent/scripts' sandbox access — supporting headless automation potential. However there's no explicit documentation of non-interactive auth (API tokens/service accounts), CI/CD pipeline examples, or exit-code/scripting guarantees needed for true CI use. Missing for 10: documented non-interactive/headless auth flow, CI/CD pipeline examples or GitHub Actions integration, explicit statement of unattended/scriptable operation, and independent confirmation of CI usage.

   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal. Create new backend projects, sync data model…”
   • [claimed-docs] “npm install -g base44@latest # Install the CLI base44 login # Authenticate base44 create # Create a project”
   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal.”
   • [claimed-docs] “Bring your own AI coding agent, or your own scripts, to a Base44 app by connecting to its sandbox.”
   • [claimed-docs] “Use the SDK to build your own frontend or backend that uses Base44 as a backend service.”
   • [probe] “official CLI documented at https://docs.base44.com/developers/references/cli/get-started/overview.md”

   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

   Base44—none0/10

   Evidence shows Base44 can expose its own app as an MCP *server* for external assistants (base44-docs-7), which is the reverse capability; there is no evidence Base44 itself can connect to and consume external MCP servers' tools as a client.

   • [claimed-docs] “App MCP lets external AI assistants like Claude, ChatGPT, and Cursor connect to your published app through its own Model Context Protocol (M…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

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

   Base44✓fullprobed8/10

   Base44 ships an official CLI (npm install -g base44, base44 login, base44 create) with documented commands for creating, syncing, deploying, and ejecting projects, explicitly aimed at AI-native/agent workflows since the backend is defined in code/config for AI agents to manage. Missing for 10: independent hands-on verification of CLI usage beyond docs, and no community corroboration of CLI reliability in practice.

   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal. Create new backend projects, sync data model…”
   • [claimed-docs] “Create new Base44 backend projects with the create command. You can choose from available templates to get started quickly.”
   • [claimed-docs] “npm install -g base44@latest # Install the CLI base44 login # Authenticate base44 create # Create a project”
   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal.”
   • [claimed-docs] “Your entire backend is defined in code and configuration files, making it easy for AI coding agents to build and manage your project.”
   • [probe] “official CLI documented at https://docs.base44.com/developers/references/cli/get-started/overview.md”

   proof ↗⚑ flag

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

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

   Base44~partialprobed6/10

   Base44 documents an SDK (with CRUD code examples) and a CLI for programmatically creating, syncing and deploying apps, which lets AI-native users drive the platform outside the UI (base44-docs-4, base44-docs-23, base44-docs-28, base44-docs-5, base44-docs-24). However, a probe for a formal OpenAPI/REST spec returned 404s across all standard paths, indicating no canonical public API reference beyond the SDK/CLI docs. Missing for 10: a documented REST/OpenAPI specification, independent third-party corroboration of API usage, and evidence of API stability/versioning guarantees.

   • [claimed-docs] “Use the SDK to build your own frontend or backend that uses Base44 as a backend service.”
   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal. Create new backend projects, sync data model…”
   • [claimed-docs] “const newTask = await base44.entities.Task.create({ title: "Complete project documentation", status: "pending", dueDate: "2024-12-31", });”
   • [claimed-docs] “npm install -g base44@latest # Install the CLI base44 login # Authenticate base44 create # Create a project”
   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal.”
   • [claimed-docs] “entities: Work with your app's data entities using CRUD operations.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.base44.com/openapi.json, https://docs.base44.com/swagger.json, https://docs.base44.com/…”

   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

   Base44—none0/10

   Evidence shows Base44 has CLI login, SDK access, and MCP server connections, but nothing describes issuing scoped or least-privilege API credentials/tokens for agents — no mention of permission scopes, role-based API keys, or credential restriction mechanisms. missing for 10: any documentation of scoped API keys, permission levels, or least-privilege credential issuance for agents.

   • [claimed-docs] “npm install -g base44@latest # Install the CLI base44 login # Authenticate base44 create # Create a project”
   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal.”
   • [claimed-docs] “Use the SDK to build your own frontend or backend that uses Base44 as a backend service.”
   • [claimed-docs] “App MCP lets external AI assistants like Claude, ChatGPT, and Cursor connect to your published app through its own Model Context Protocol (M…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

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

   Base44✓fullprobed8/10

   Base44 documents an official SDK with clear getting-started docs, code examples (entities.Task.create), CRUD entity operations, and a CLI to scaffold/manage projects, all first-party and probe-confirmed. Missing for 10: independent/hands-on developer corroboration of SDK usage and a public OpenAPI spec (probe found 404s for openapi/swagger endpoints).

   • [claimed-docs] “Use the SDK to build your own frontend or backend that uses Base44 as a backend service.”
   • [claimed-docs] “Build full-stack apps with the SDK, CLI, and a managed backend.”
   • [claimed-docs] “const newTask = await base44.entities.Task.create({ title: "Complete project documentation", status: "pending", dueDate: "2024-12-31", });”
   • [claimed-docs] “entities: Work with your app's data entities using CRUD operations.”
   • [claimed-docs] “npm install -g base44@latest # Install the CLI base44 login # Authenticate base44 create # Create a project”
   • [probe] “official CLI documented at https://docs.base44.com/developers/references/cli/get-started/overview.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.base44.com/openapi.json, https://docs.base44.com/swagger.json, https://docs.base44.com/…”

   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

   Base44—none0/10

   No evidence anywhere in the pack of webhook subscription/event functionality; documentation covers CLI, SDK, MCP server for external assistants, entities/CRUD, GitHub sync, but nothing about outbound webhooks 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

   Base44—none0/10

   Base44 docs describe AI agents that take actions (update records, trigger workflows) and a Data page for viewing tables, but there is no evidence of AI-generated insights, analytics, or suggestions derived from the app's own data. missing for 10: any documentation of data analysis/insight generation, dashboards, or suggestion features surfaced to end users.

   • [claimed-docs] “AI agents turn simple chats into actions in your Base44 app. Instead of only replying with text, they update records, trigger workflows, and…”
   • [claimed-docs] “The Data page shows every table in your app as a card. Click a card to open its records.”

   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

   Base44—none0/10

   Base44's docs describe AI agents that respond to chat and trigger workflows within an app, and CLI/SDK tooling for building apps, but there is no evidence of scheduled, event-driven, or persistent background automations that run autonomously without a user prompt. Missing for 10: any mention of cron/scheduled jobs, background workers, autonomous triggers, or agents operating without live chat interaction.

   • [claimed-docs] “AI agents turn simple chats into actions in your Base44 app. Instead of only replying with text, they update records, trigger workflows, and…”

   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

   Base44✓fullprobed8/10

   Base44 is itself an AI app-building product where the core interaction is delegating tasks (build features, design, resolve conflicts) to a built-in AI assistant via chat, as documented in the AI-agents feature and corroborated by hands-on community reports of the AI resolving issues and building full apps from prompts. missing for 10: independent benchmarking of assistant task scope/limits and more first-party documentation detail on assistant capabilities beyond marketing copy.

   • [claimed-docs] “AI agents turn simple chats into actions in your Base44 app. Instead of only replying with text, they update records, trigger workflows, and…”
   • [claimed-docs] “See every page at once. Leave notes, sketch ideas, and send instructions straight to AI — all on one board.”
   • [claimed-docs] “Ask for design options, pick the one you want. AI shows previews before it touches anything.”
   • [community] “Base has resolve with AI functionality, which is far superior to anything I've seen outside of an IDE. It just works.”
   • [community] “Although Base44 seems to be a wrapper on ChatGpt but output is far superior. I tried 'adminLTE port to React' via both; Chatgpt gave me a ve…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.base44.com/llms.txt # Base44 Documentation > Base44 is an AI-powered app builder. Describe your id…”

   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

   Base44✓fullprobed8/10

   Base44's core product is natural-language app building — users describe ideas, request design changes, and generate content via chat ('Ask for design options', 'Describe a video, get one'), and community evidence confirms this works well in practice ('two prompts and deploy', 'far superior' output from prompts). This is corroborated by hands-on community reports, not just vendor docs. Missing for 10: independent benchmarking of how far natural-language commands alone can go before requiring code/CLI intervention, and clearer documentation of the full scope of NL commands versus GUI-only actions.

   • [claimed-docs] “See every page at once. Leave notes, sketch ideas, and send instructions straight to AI — all on one board.”
   • [claimed-docs] “Ask for design options, pick the one you want. AI shows previews before it touches anything.”
   • [claimed-docs] “Describe a video, get one. Add it to any page — hero sections, onboarding screens, product previews.”
   • [community] “Base has resolve with AI functionality, which is far superior to anything I've seen outside of an IDE. It just works.”
   • [community] “Although Base44 seems to be a wrapper on ChatGpt but output is far superior. I tried 'adminLTE port to React' via both; Chatgpt gave me a ve…”
   • [community] “I find it pretty cool. Even if it's simple to do the same with Cursor, but then deploying it somewhere and all the ceremonies. I quickly bui…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.base44.com/llms.txt # Base44 Documentation > Base44 is an AI-powered app builder. Describe your id…”

   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

   Base44—none0/10

   Base44 provides static SDK/CLI docs with code snippets (e.g., docs-23, docs-28) but no evidence of an interactive API reference with runnable/executable examples; the probe explicitly found no OpenAPI/Swagger spec (404s across all candidate paths), indicating no such interactive reference exists.

   • [claimed-docs] “Use the SDK to build your own frontend or backend that uses Base44 as a backend service.”
   • [claimed-docs] “const newTask = await base44.entities.Task.create({ title: "Complete project documentation", status: "pending", dueDate: "2024-12-31", });”
   • [claimed-docs] “entities: Work with your app's data entities using CRUD operations.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.base44.com/openapi.json, https://docs.base44.com/swagger.json, https://docs.base44.com/…”

   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

   Base44—none0/10

   A direct probe for OpenAPI/swagger specs on Base44's docs domain returned 404 on all candidate paths, and no documentation mentions a downloadable machine-readable API spec; only an llms.txt exists, which is not an OpenAPI-equivalent spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.base44.com/openapi.json, https://docs.base44.com/swagger.json, https://docs.base44.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.base44.com/llms.txt # Base44 Documentation > Base44 is an AI-powered app builder. Describe your id…”

   proof ↗⚑ flag

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

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

   Base44~partialclaimed4/10

   Base44 docs mention 'connecting to its sandbox' for bring-your-own-agent workflows and a CLI 'clone/eject' command that spins up a separate project with its own app ID, both of which imply an isolated environment distinct from the live app. However, there is no explicit documentation of a staging/sandbox mode with synced-but-isolated production data, nor guidance on safely testing without affecting production records. Missing for 10: explicit staging environment docs, data-isolation guarantees, and any hands-on/community confirmation that sandbox testing avoids touching production data.

   • [claimed-docs] “Bring your own AI coding agent, or your own scripts, to a Base44 app by connecting to its sandbox.”
   • [claimed-docs] “This command downloads the frontend code and backend resources from a selected app and creates a new project with its own app ID.”
   • [claimed-docs] “Clone an existing Base44 app into a separate local project. This command downloads the frontend code and backend resources from a selected a…”

   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

   Base44—none0/10

   No evidence of API versioning scheme or any documented deprecation policy; probe explicitly found no OpenAPI spec, and SDK/CLI docs describe usage but never mention versioning or deprecation guarantees.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.base44.com/openapi.json, https://docs.base44.com/swagger.json, https://docs.base44.com/…”
   • [claimed-docs] “Use the SDK to build your own frontend or backend that uses Base44 as a backend service.”
   • [claimed-docs] “Build full-stack apps with the SDK, CLI, and a managed backend.”

   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

   Base44—none0/10

   The SDK docs only show single-record CRUD operations (e.g., creating one Task) and the CLI covers deploy/sync of resources, but no evidence describes bulk create/update/delete across many items or batch endpoints for AI-native automation.

   • [claimed-docs] “const newTask = await base44.entities.Task.create({ title: "Complete project documentation", status: "pending", dueDate: "2024-12-31", });”
   • [claimed-docs] “entities: Work with your app's data entities using CRUD operations.”
   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal.”

   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

   Base44—none0/10

   No evidence of scheduled/recurring job or workflow triggers (e.g., cron-like jobs, timers) in Base44's docs — only entities/CRUD, AI agents triggered by chat, and CLI/SDK for building apps are mentioned, none of which describe recurring scheduling.

   ⚑ 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

   Base44~partialclaimed4/10

   Base44 supports GitHub sync for local development, which provides some version-control capability for app code, but there is no documented feature for versioning/reviewing/rolling back automations specifically (AI agents, workflows, or data changes) within the platform itself. missing for 10: automation-specific versioning, in-app diff/review UI for automations, rollback mechanism for workflow or agent changes, independent confirmation of rollback working in practice.

   • [claimed-docs] “Connect your app to GitHub to write code in your local development environment or in Base44 and keep them in sync with each other.”
   • [claimed-docs] “Connect your Base44 app to GitHub for version control, local development, and collaboration.”
   • [claimed-docs] “AI agents turn simple chats into actions in your Base44 app. Instead of only replying with text, they update records, trigger workflows, and…”

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

   Base44~partialcommunity6/10

   Base44 documents built-in 'AI agents for apps' that let generated apps chat, trigger workflows, and call tools without the user standing up their own LLM integration (base44-docs-6), and community feedback confirms this AI functionality 'just works' inside apps (base44-comm-4, base44-comm-5). However, there is no explicit documentation stating that provider API keys are fully managed/abstracted away (e.g., no mention of BYO-key vs. platform-key model, rate limits, or supported providers), so the 'without managing provider keys' claim is only implied, not directly evidenced. Missing for 10: explicit statement on API key management/provider abstraction, list of supported LLM providers, and independent hands-on confirmation that no key setup is required.

   • [claimed-docs] “AI agents turn simple chats into actions in your Base44 app. Instead of only replying with text, they update records, trigger workflows, and…”
   • [community] “Base has resolve with AI functionality, which is far superior to anything I've seen outside of an IDE. It just works.”
   • [community] “Although Base44 seems to be a wrapper on ChatGpt but output is far superior. I tried 'adminLTE port to React' via both; Chatgpt gave me a ve…”

   proof ↗⚑ flag

Auth

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

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

   Base44✓fullclaimed8/10

   Base44 docs explicitly describe built-in sign-up/login scaffolding with email and social providers (e.g., Google), ready-made login/register/forgot-password pages, and customizable branding — directly matching the story. Missing for 10: independent hands-on verification of the full provider list and UI customization depth beyond docs.

   • [claimed-docs] “You can offer multiple ways for people to sign up, such as email, Google, or other providers, so that login stays simple, secure, and famili…”
   • [claimed-docs] “All new Base44 apps come with custom login pages built in. You get ready-made login, register, forgot password, and reset password pages tha…”
   • [claimed-docs] “They live inside your app, so you can customize the design, translate them into any language, and add your own branding.”

   proof ↗⚑ flag

Database

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

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

   Base44✓fullcommunity8/10

   Base44 ships a built-in, managed database as part of the app builder—the Data page shows tables/records directly in-app (base44-docs-9), entities are auto-created and manipulated via SDK CRUD (base44-docs-23, base44-docs-28), and backend/data models sync automatically without leaving the platform. Community corroboration confirms the integrated DB approach is core to the product's value (base44-comm-2). Missing for 10: no independent hands-on walkthrough of provisioning steps, and no detail on schema/migration controls or scaling limits.

   • [claimed-docs] “The Data page shows every table in your app as a card. Click a card to open its records.”
   • [claimed-docs] “const newTask = await base44.entities.Task.create({ title: "Complete project documentation", status: "pending", dueDate: "2024-12-31", });”
   • [claimed-docs] “entities: Work with your app's data entities using CRUD operations.”
   • [claimed-docs] “Your entire backend is defined in code and configuration files, making it easy for AI coding agents to build and manage your project.”
   • [community] “Maor opted to include the db within the platform, rather than enable persistence externally. This really made the output great, and made fix…”

   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

   Base44—none0/10

   No documentation describes an automated security review or pre-launch security scan for generated apps; instead, community reports describe a real vulnerability discovered by external researchers and criticism that code was pushed without reviews, suggesting no such built-in security review process exists.

   • [community] “The vulnerability we discovered was remarkably simple to exploit - by providing only a non-secret app_id value to undocumented registration …”
   • [community] “he also pushed code every day without code reviews. This is how you get technical debt and security vulnerabilities so fast.”
   • [community] “the vulnerability was fixed in less than 24 hours”

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

   Base44~partialclaimed5/10

   Base44 supports backend entities/CRUD, SDK/CLI-based backend code, and login/auth integrations, and its AI-agent/tool-connection features suggest extensibility, but there is no explicit documentation of adding custom server-side functions or built-in third-party integrations like payment processors or email services from the builder. missing for 10: dedicated server-side function/webhook feature, documented payment gateway integration, documented email-sending integration, and independent confirmation of these working in practice.

   • [claimed-docs] “AI agents turn simple chats into actions in your Base44 app. Instead of only replying with text, they update records, trigger workflows, and…”
   • [claimed-docs] “The Data page shows every table in your app as a card. Click a card to open its records.”
   • [claimed-docs] “Build full-stack apps with the SDK, CLI, and a managed backend.”
   • [claimed-docs] “const newTask = await base44.entities.Task.create({ title: "Complete project documentation", status: "pending", dueDate: "2024-12-31", });”
   • [claimed-docs] “entities: Work with your app's data entities using CRUD operations.”
   • [claimed-docs] “Your entire backend is defined in code and configuration files, making it easy for AI coding agents to build and manage your project.”

   proof ↗⚑ flag

Export

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

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

   Base44✓fullclaimed8/10

   The CLI 'eject' command explicitly downloads full frontend and backend code from an app and creates a standalone project with its own app ID, enabling code export outside the platform, and this is corroborated by CLI overview docs and GitHub sync features for local development. missing for 10: no independent/hands-on confirmation that the exported app can be fully hosted/run with no Base44 backend dependency, and no detail on how backend services (DB, auth) are replicated outside the platform.

   • [claimed-docs] “This command downloads the frontend code and backend resources from a selected app and creates a new project with its own app ID.”
   • [claimed-docs] “Clone an existing Base44 app into a separate local project. This command downloads the frontend code and backend resources from a selected a…”
   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal. Create new backend projects, sync data model…”
   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal.”
   • [claimed-docs] “Connect your app to GitHub to write code in your local development environment or in Base44 and keep them in sync with each other.”
   • [claimed-docs] “Connect your Base44 app to GitHub for version control, local development, and collaboration.”

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

   Base44✓fullclaimed8/10

   Base44 documents GitHub sync to write code locally and keep it in sync with the platform, a CLI to eject/clone apps into local projects with their own app ID, and explicit 'bring your own agent/scripts' sandbox connectivity for local tooling. These first-party docs directly cover local editing plus pushing changes back, though there's no independent/hands-on verification of the round-trip workflow. Missing for 10: independent/hands-on confirmation that local-edit-then-push-back actually works smoothly in practice.

   • [claimed-docs] “Connect your app to GitHub to write code in your local development environment or in Base44 and keep them in sync with each other.”
   • [claimed-docs] “Bring your own AI coding agent, or your own scripts, to a Base44 app by connecting to its sandbox.”
   • [claimed-docs] “Connect your Base44 app to GitHub for version control, local development, and collaboration.”
   • [claimed-docs] “Clone an existing Base44 app into a separate local project. This command downloads the frontend code and backend resources from a selected a…”
   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal. Create new backend projects, sync data model…”
   • [claimed-docs] “Your entire backend is defined in code and configuration files, making it easy for AI coding agents to build and manage your project.”

   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

   Base44✓fullclaimed8/10

   Base44 has documented first-party GitHub integration explicitly for two-way sync between local development and the Base44 app editor, plus CLI eject/clone commands to pull code into your own repo with SDK support for custom builds. Missing for 10: independent/hands-on confirmation of the bidirectional sync working reliably in practice, and more detail on conflict resolution or merge behavior.

   • [claimed-docs] “Connect your app to GitHub to write code in your local development environment or in Base44 and keep them in sync with each other.”
   • [claimed-docs] “Connect your Base44 app to GitHub for version control, local development, and collaboration.”
   • [claimed-docs] “This command downloads the frontend code and backend resources from a selected app and creates a new project with its own app ID.”
   • [claimed-docs] “Clone an existing Base44 app into a separate local project. This command downloads the frontend code and backend resources from a selected a…”
   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal. Create new backend projects, sync data model…”

   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

   Base44~partialcommunity4/10

   Base44 supports app-level collaboration via GitHub sync (both docs-2/18) and community evidence confirms apps have an 'editor/collaborator' role concept (base44-comm-9), showing teammates can be added to a shared app. However, there is no first-party documentation of a dedicated shared-workspace UI, invite flow, or role/permission management for teams, and the collaborator mechanism was shown to have a security flaw (base44-comm-9, base44-comm-11) though patched quickly. Missing for 10: explicit workspace/team management docs, invite-teammate flow, granular permission controls, and independent confirmation of smooth real-time multi-user editing.

   • [claimed-docs] “Connect your app to GitHub to write code in your local development environment or in Base44 and keep them in sync with each other.”
   • [claimed-docs] “Connect your Base44 app to GitHub for version control, local development, and collaboration.”
   • [community] “The vulnerability we discovered was remarkably simple to exploit - by providing only a non-secret app_id value to undocumented registration …”
   • [community] “the vulnerability was fixed in less than 24 hours”

   proof ↗⚑ flag

Domains

1. founderConnect a custom domain to my published app

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

   Base44✓fullclaimed8/10

   Docs explicitly cover connecting a custom domain, automatic SSL issuance/renewal, and the branding benefit of a custom domain, directly matching the founder story. Missing for 10: no independent/hands-on corroboration of the domain-connection flow and no detail on DNS setup steps or troubleshooting.

   • [claimed-docs] “Base44 issues and renews your SSL certificate automatically once your domain is connected, so your app is always served securely over HTTPS.”
   • [claimed-docs] “A custom domain looks more professional and reinforces your brand every time someone visits.”

   proof ↗⚑ flag

Publish

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

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

   Base44—none0/10

   Base44's 'eject' command only clones an app into a new Base44-hosted project with its own app ID (base44-docs-1/22), and custom-domain support (base44-docs-8/26) is for pointing a domain at Base44's own hosting, not exporting to external infrastructure. No evidence describes downloading a deployable build for self-hosting or deploying to a third-party cloud/host.

   • [claimed-docs] “This command downloads the frontend code and backend resources from a selected app and creates a new project with its own app ID.”
   • [claimed-docs] “Clone an existing Base44 app into a separate local project. This command downloads the frontend code and backend resources from a selected a…”
   • [claimed-docs] “Base44 issues and renews your SSL certificate automatically once your domain is connected, so your app is always served securely over HTTPS.”
   • [claimed-docs] “A custom domain looks more professional and reinforces your brand every time someone visits.”

   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

   Base44~partialcommunity6/10

   Docs show apps get a custom domain with auto-issued SSL (base44-docs-8, base44-docs-26) and a community user describes building an app with 'two prompts and deploy' (base44-comm-6), implying a simple publish flow, but there is no first-party doc explicitly describing a one-click 'Publish' action or default live URL provisioning step-by-step. missing for 10: explicit docs on the one-step publish/deploy button and default subdomain URL generation, independent confirmation of publish simplicity beyond one anecdote.

   • [claimed-docs] “Base44 issues and renews your SSL certificate automatically once your domain is connected, so your app is always served securely over HTTPS.”
   • [claimed-docs] “A custom domain looks more professional and reinforces your brand every time someone visits.”
   • [community] “I find it pretty cool. Even if it's simple to do the same with Cursor, but then deploying it somewhere and all the ceremonies. I quickly bui…”

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

   Base44✓fullclaimed7/10

   Base44 explicitly documents a 'Bring your own agent' feature letting users connect their own AI coding agent or scripts directly to the app's sandbox, and the backend-as-code design is highlighted as friendly to external AI agents. However, this is only first-party documentation with no independent/hands-on verification of how well an external agent 'drives the builder' compared to the built-in one. missing for 10: independent/hands-on confirmation, details on how full control transfers to the external agent vs the built-in one.

   • [claimed-docs] “Bring your own AI coding agent, or your own scripts, to a Base44 app by connecting to its sandbox.”
   • [claimed-docs] “Your entire backend is defined in code and configuration files, making it easy for AI coding agents to build and manage your project.”
   • [claimed-docs] “Build full-stack apps with the SDK, CLI, and a managed backend.”

   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

   Base44—none0/10

   Evidence shows Base44 supports editing code externally via GitHub sync, CLI eject/download, or bringing your own agent to the sandbox, but there is no documentation of an in-builder source code editor where a developer can view/edit the generated code directly inside the app builder UI. missing for 10: any mention of an in-app/in-builder code editor or code view, first-party or hands-on confirmation of direct in-builder code editing.

   • [claimed-docs] “This command downloads the frontend code and backend resources from a selected app and creates a new project with its own app ID.”
   • [claimed-docs] “Connect your app to GitHub to write code in your local development environment or in Base44 and keep them in sync with each other.”
   • [claimed-docs] “Bring your own AI coding agent, or your own scripts, to a Base44 app by connecting to its sandbox.”
   • [claimed-docs] “Connect your Base44 app to GitHub for version control, local development, and collaboration.”
   • [claimed-docs] “Clone an existing Base44 app into a separate local project. This command downloads the frontend code and backend resources from a selected a…”

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

   Base44~partialclaimed5/10

   Base44 docs mention an AI-driven design/preview flow ('AI shows previews before it touches anything') and an all-in-one board to view pages and send instructions, implying a live-preview-while-building experience, but there is no explicit documentation of a dedicated 'preview before publish' mode or hands-on confirmation of this specific workflow. missing for 10: explicit documentation of a live preview/staging environment distinct from the published app, independent/hands-on confirmation that founders can interact with an unpublished live preview, and details on how changes are reflected in real time before publishing.

   • [claimed-docs] “Ask for design options, pick the one you want. AI shows previews before it touches anything.”
   • [claimed-docs] “See every page at once. Leave notes, sketch ideas, and send instructions straight to AI — all on one board.”

   proof ↗⚑ flag

Prompt iteration

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

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

   Base44~partialcommunity5/10

   Base44 markets AI-driven previews before changes are applied (docs-14) and lets users send follow-up instructions to the AI from a shared board (docs-12), suggesting some iterative safety, and community feedback broadly praises the AI's ability to build/extend apps (base44-comm-4, base44-comm-5). However there is no explicit documentation or hands-on evidence about preserving prior functionality, versioning, rollback, or regression protection when iterating via prompts, and comm-8 notes users can hit walls that cost money without resolving issues cleanly. Missing for 10: explicit non-regression/version-history mechanism, documented safeguards against breaking existing features, and independent confirmation that follow-up prompts don't degrade prior work.

   • [claimed-docs] “See every page at once. Leave notes, sketch ideas, and send instructions straight to AI — all on one board.”
   • [claimed-docs] “Ask for design options, pick the one you want. AI shows previews before it touches anything.”
   • [community] “Base has resolve with AI functionality, which is far superior to anything I've seen outside of an IDE. It just works.”
   • [community] “Although Base44 seems to be a wrapper on ChatGpt but output is far superior. I tried 'adminLTE port to React' via both; Chatgpt gave me a ve…”
   • [community] “They make it seem like you can vibe code an entire web shop in one prompt. In reality they charge by the token so if you hit a wall trying t…”

   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

   Base44—none0/10

   Evidence shows Base44's editing model is prompt/AI-driven (e.g., 'Ask for design options, pick the one you want. AI shows previews before it touches anything' and 'send instructions straight to AI') rather than direct click-to-edit manipulation of text, style, or layout. No documentation or community evidence describes a designer selecting an element and editing it inline without going through an AI prompt.

   • [claimed-docs] “See every page at once. Leave notes, sketch ideas, and send instructions straight to AI — all on one board.”
   • [claimed-docs] “Set colors and fonts for your entire app from one place. Your entire app — updated everywhere at once.”
   • [claimed-docs] “Ask for design options, pick the one you want. AI shows previews before it touches anything.”

   proof ↗⚑ flag

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

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

   Base44~partialprobed5/10

   Base44 offers an SDK/CLI for CRUD on data entities, backend code/config management, and app MCP servers for external agents, giving strong programmatic access to backend/data operations. However, many UI-only capabilities (visual design board, theming/branding UI, AI-generated design previews, video generation, template publishing flow, login page customization) have no documented API/CLI equivalents, and there's no OpenAPI spec exposed (openapi probe returned 404s), suggesting API parity is partial rather than complete. missing for 10: documented API/CLI equivalents for visual design/branding tools, AI design preview workflow, media generation features, and a public OpenAPI spec confirming full UI-API parity.

   • [claimed-docs] “Use the SDK to build your own frontend or backend that uses Base44 as a backend service.”
   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal. Create new backend projects, sync data model…”
   • [claimed-docs] “Build full-stack apps with the SDK, CLI, and a managed backend.”
   • [claimed-docs] “const newTask = await base44.entities.Task.create({ title: "Complete project documentation", status: "pending", dueDate: "2024-12-31", });”
   • [claimed-docs] “entities: Work with your app's data entities using CRUD operations.”
   • [claimed-docs] “Your entire backend is defined in code and configuration files, making it easy for AI coding agents to build and manage your project.”
   • [claimed-docs] “App MCP lets external AI assistants like Claude, ChatGPT, and Cursor connect to your published app through its own Model Context Protocol (M…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.base44.com/openapi.json, https://docs.base44.com/swagger.json, https://docs.base44.com/…”
   • [claimed-docs] “See every page at once. Leave notes, sketch ideas, and send instructions straight to AI — all on one board.”
   • [claimed-docs] “Set colors and fonts for your entire app from one place. Your entire app — updated everywhere at once.”
   • [claimed-docs] “Ask for design options, pick the one you want. AI shows previews before it touches anything.”
   • [claimed-docs] “Describe a video, get one. Add it to any page — hero sections, onboarding screens, product previews.”

   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

   Base44~partialclaimed5/10

   The 'eject' CLI command lets a user clone an app's frontend code and backend resources into a new independent project with its own app ID, which supports a degree of platform exit, and GitHub sync/SDK access reinforce code portability. However, there is no explicit documentation of exporting the actual data records (database contents) in an open, standard format (e.g., CSV/JSON dump) — the Data page description only shows records in-app, and no export-to-open-format feature is described. Missing for 10: explicit data-record export in open formats (CSV/JSON/SQL dump), documentation confirming eject includes full data migration, independent verification that a full account can be exported and closed without lock-in.

   • [claimed-docs] “This command downloads the frontend code and backend resources from a selected app and creates a new project with its own app ID.”
   • [claimed-docs] “Clone an existing Base44 app into a separate local project. This command downloads the frontend code and backend resources from a selected a…”
   • [claimed-docs] “The Data page shows every table in your app as a card. Click a card to open its records.”
   • [claimed-docs] “Connect your Base44 app to GitHub for version control, local development, and collaboration.”

   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

   Base44—none0/10

   Base44 is a closed, hosted AI app-builder platform; no evidence anywhere in the pack indicates its own source code (platform/product source) is published under an open license. Evidence only covers exporting/ejecting user-built apps, CLI, SDK, and GitHub sync for user apps—not the openness of Base44's own codebase.

   • [claimed-docs] “This command downloads the frontend code and backend resources from a selected app and creates a new project with its own app ID.”
   • [claimed-docs] “Clone an existing Base44 app into a separate local project. This command downloads the frontend code and backend resources from a selected a…”
   • [claimed-docs] “Use the SDK to build your own frontend or backend that uses Base44 as a backend service.”
   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal. Create new backend projects, sync data model…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

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

   Base44—none0/10

   Evidence shows only that you can 'eject' an individual app's frontend/backend code into a new Base44-hosted project (still using Base44's platform with its own app ID), not that the Base44 platform/core service itself can be run on your own infrastructure. No mention of an open-source core, downloadable server, or self-hosting instructions exists in the pack.

   • [claimed-docs] “This command downloads the frontend code and backend resources from a selected app and creates a new project with its own app ID.”
   • [claimed-docs] “Clone an existing Base44 app into a separate local project. This command downloads the frontend code and backend resources from a selected a…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.base44.com/llms.txt # Base44 Documentation > Base44 is an AI-powered app builder. Describe your id…”

   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

   Base44—none0/10

   No evidence in the docs pack describes how credits/tokens are consumed per action or what plans include; the only relevant signal is a community complaint that costs can balloon before you realize it ('they charge by the token... run up a huge bill'), which reflects opacity rather than a documented usage/plan breakdown. missing for 10: any pricing page, credit/token cost table, plan comparison, or usage dashboard documentation.

   • [community] “They make it seem like you can vibe code an entire web shop in one prompt. In reality they charge by the token so if you hit a wall trying t…”

   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

   Base44—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location controls for Base44 apps; the docs focus on app building, CLI, SDK, and integrations without any privacy/data-location settings.

   ⚑ 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

   Base44—none0/10

   No evidence in the pack mentions any data-training opt-out, privacy controls over AI model training, or related policy language; the docs cover unrelated topics like CLI, SDK, domains, and login. Absence of evidence for this applicable privacy axis yields 'none'.

   ⚑ 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

   Base44—none0/10

   No evidence in the pack addresses data retention policies, data export, or account/data deletion controls; only unrelated features (data tables display, security incident, SSL) are mentioned. This is an applicable privacy axis for a SaaS app builder, so absence of evidence yields 'none'.

   ⚑ 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

   Base44—none0/10

   No evidence in the pack mentions telemetry, usage tracking, analytics collection, or any opt-out mechanism for Base44; the docs and community discussion cover unrelated features and a security vulnerability, not data collection controls.

   ⚑ 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

   Base44✓fullclaimed7/10

   Docs explicitly state you can turn a Figma frame into a working app and also start from an existing website and refine it in the app editor, directly matching the story's core capability. Missing for 10: no independent/hands-on corroboration of Figma import fidelity, and no detail on how much manual refinement is needed after import.

   • [claimed-docs] “Turn a Figma frame into a working app.”
   • [claimed-docs] “Begin from a website you already own and refine it in the app editor.”

   proof ↗⚑ flag

Generation

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

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

   Base44✓fullprobed8/10

   Base44 explicitly builds full-stack apps (frontend + managed backend with data entities, auth, business logic) from prompts, and community testimonials confirm producing 'fully functional apps' from prompts with 'two prompts and deploy.' missing for 10: independent technical benchmarking of true single-prompt full-stack generation and clearer boundary on how much backend logic vs just data models is generated.

   • [claimed-docs] “Build full-stack apps with the SDK, CLI, and a managed backend.”
   • [claimed-docs] “entities: Work with your app's data entities using CRUD operations.”
   • [claimed-docs] “All new Base44 apps come with custom login pages built in. You get ready-made login, register, forgot password, and reset password pages tha…”
   • [claimed-docs] “The Data page shows every table in your app as a card. Click a card to open its records.”
   • [community] “Although Base44 seems to be a wrapper on ChatGpt but output is far superior. I tried 'adminLTE port to React' via both; Chatgpt gave me a ve…”
   • [community] “I find it pretty cool. Even if it's simple to do the same with Cursor, but then deploying it somewhere and all the ceremonies. I quickly bui…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.base44.com/llms.txt # Base44 Documentation > Base44 is an AI-powered app builder. Describe your id…”

   proof ↗⚑ flag

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

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

   Base44✓fullprobed9/10

   Base44's core value proposition is prompt-to-app generation with a managed full-stack backend (data, auth, deploy, custom domain), well documented (base44-docs-17, docs-29, probe-1) and strongly corroborated by hands-on community reports of building fully functional apps from a couple of prompts (base44-comm-4, comm-5, comm-6). Some community skepticism exists around cost/complexity at scale (base44-comm-8) but this doesn't contradict the core capability. Missing for 10: independent benchmark/quantitative comparison of generated app quality and more first-party detail on limits of 'full-stack' completeness for complex apps.

   • [claimed-docs] “Build full-stack apps with the SDK, CLI, and a managed backend.”
   • [claimed-docs] “Your entire backend is defined in code and configuration files, making it easy for AI coding agents to build and manage your project.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.base44.com/llms.txt # Base44 Documentation > Base44 is an AI-powered app builder. Describe your id…”
   • [community] “Base has resolve with AI functionality, which is far superior to anything I've seen outside of an IDE. It just works.”
   • [community] “Although Base44 seems to be a wrapper on ChatGpt but output is far superior. I tried 'adminLTE port to React' via both; Chatgpt gave me a ve…”
   • [community] “I find it pretty cool. Even if it's simple to do the same with Cursor, but then deploying it somewhere and all the ceremonies. I quickly bui…”

   proof ↗⚑ flag

Programmatic generation

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

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

   Base44~partialprobed7/10

   Base44 offers a CLI (`base44 create`, sync, deploy) and an SDK with entity CRUD operations that let developers programmatically build and manage apps and their data, and states the backend is code/config-based so AI agents can manage projects. However, there's no evidence of a full public REST/HTTP 'platform API' for app generation (openapi/swagger endpoints all 404), so programmatic access is limited to the CLI/SDK wrapper rather than a documented direct API. Missing for 10: a public REST API spec for app creation, independent corroboration of programmatic app generation beyond CLI/SDK docs.

   • [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal. Create new backend projects, sync data model…”
   • [claimed-docs] “Build full-stack apps with the SDK, CLI, and a managed backend.”
   • [claimed-docs] “Create new Base44 backend projects with the create command. You can choose from available templates to get started quickly.”
   • [claimed-docs] “npm install -g base44@latest # Install the CLI base44 login # Authenticate base44 create # Create a project”
   • [claimed-docs] “entities: Work with your app's data entities using CRUD operations.”
   • [claimed-docs] “Your entire backend is defined in code and configuration files, making it easy for AI coding agents to build and manage your project.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.base44.com/openapi.json, https://docs.base44.com/swagger.json, https://docs.base44.com/…”

   proof ↗⚑ flag

Templates

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

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

   Base44✓fullclaimed8/10

   Base44 explicitly supports starting from community/public app templates (docs-10, docs-20) and CLI project creation from templates (docs-19), plus cloning existing apps via eject (docs-1/22) instead of a blank prompt. Missing for 10: independent/community corroboration of template quality or breadth, and no detail on template categories/curation.

   • [claimed-docs] “You can also publish your own public templates for others to use, reaching a wider audience while showcasing your skills.”
   • [claimed-docs] “Browse a wide range of ready-made templates created by talented creators in the community.”
   • [claimed-docs] “Create new Base44 backend projects with the create command. You can choose from available templates to get started quickly.”
   • [claimed-docs] “This command downloads the frontend code and backend resources from a selected app and creates a new project with its own app ID.”
   • [claimed-docs] “Clone an existing Base44 app into a separate local project. This command downloads the frontend code and backend resources from a selected a…”

   proof ↗⚑ flag