Base44 vs Floot

Agent access

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

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

   Floot✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

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

   Floot—none0/10

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

   ⚑ flag

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

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

   Floot—none0/10

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

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

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   Base44✓fullclaimed7/10

   Base44 documents 'App MCP', letting external AI assistants like Claude, ChatGPT, and Cursor connect to a published Base44 app via its own official MCP server, directly matching the story. Missing for 10: independent/hands-on verification of the MCP server working in practice and more detail on setup/config beyond the single doc page.

   • [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

   Floot✓fullprobed7/10

   Floot documents an official remote MCP server that can be added to Cursor, VS Code, Zed, or any MCP-compatible client, with concrete tool capabilities (get_logs, query_database, execute_sql, create_checkpoint, generate_image) exposed via that server. This is first-party documentation only, with no independent/hands-on corroboration of the MCP connection working in practice. Missing for 10: independent or community verification of the MCP server working end-to-end, and more detail on authentication/setup reliability.

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

   proof ↗⚑ flag

5. ai-native userUse an official CLI

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

   Floot—none0/10

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

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

   proof ↗⚑ flag

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

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

   Floot~partialprobed7/10

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

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

   proof ↗⚑ flag

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

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

   Floot—none0/10

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

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

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

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

   Floot—none0/10

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

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

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

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

   Floot—none0/10

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

   ⚑ flag

Agentic features

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

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

   Floot—none0/10

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

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

   proof ↗⚑ flag

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

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

   Floot—none0/10

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

   ⚑ flag

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

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

   Floot✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

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

   Floot✓fullprobed8/10

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

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

   proof ↗⚑ flag

Api quality

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

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

   Floot—none0/10

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

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

   proof ↗⚑ flag

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

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

   Floot—none0/10

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

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

   proof ↗⚑ flag

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

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

   Floot—none0/10

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

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

   proof ↗⚑ flag

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

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

   Floot—none0/10

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

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

   proof ↗⚑ flag

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

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

   Floot—none0/10

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

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

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Base44
   Base44~partialclaimed4/10

   Docs mention AI agents that can 'update records, trigger workflows, and connect to tools' in response to chat, implying some action-triggering capability, but there is no documentation of a rule/event definition system (e.g., 'when X happens, do Y') or automated triggers outside of chat-initiated agent actions. Missing for 10: explicit event/trigger rule builder, documented conditions for automatic triggering, and independent evidence of automation-depth beyond chat-driven agent actions.

   • [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

   Floot—none0/10

   Evidence covers Floot's AI-assisted app-building tools (logs, DB queries, checkpoints, image generation, MCP integration) but nothing describes user-defined rules/triggers that automatically fire actions on events (e.g., webhooks, event-condition-action automation). No workflow-automation or trigger/rule engine is documented.

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

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

   Floot—none0/10

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

   ⚑ flag

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

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

   Floot~partialclaimed5/10

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

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

   proof ↗⚑ flag

Ai features

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

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

   Floot—none0/10

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

   ⚑ flag

Auth

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

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

   Floot—none0/10

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

   ⚑ flag

Database

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

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

   Floot✓fullprobed7/10

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

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

   proof ↗⚑ flag

Security

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

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

   Floot—none0/10

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

   ⚑ flag

Server logic

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

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

   Floot~partialclaimed6/10

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

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

   proof ↗⚑ flag

Export

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

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

   Floot✓fullclaimed8/10

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

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

   proof ↗⚑ flag

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

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

   Floot~partialclaimed5/10

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

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

   proof ↗⚑ flag

Git sync

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

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

   Floot—none0/10

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

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

   proof ↗⚑ flag

Collaboration

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

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

   Floot—none0/10

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

   ⚑ flag

Domains

1. founderConnect a custom domain to my published app

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

   Floot—none0/10

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

   ⚑ flag

Publish

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

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

   Floot~partialclaimed6/10

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

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

   proof ↗⚑ flag

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

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

   Floot~partialprobed6/10

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

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

   proof ↗⚑ flag

Agent integration

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

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

   Floot~partialprobed6/10

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

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

   proof ↗⚑ flag

Code editing

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

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

   Floot—none0/10

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

   ⚑ flag

Preview

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

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

   Floot~partialclaimed5/10

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

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

   proof ↗⚑ flag

Prompt iteration

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

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

   Floot~partialclaimed5/10

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

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

   proof ↗⚑ flag

Visual editing

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

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

   Floot—none0/10

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

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

   proof ↗⚑ flag

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

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

   Floot~partialprobed5/10

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

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

   proof ↗⚑ flag

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

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

   Floot~partialclaimed6/10

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

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

   proof ↗⚑ flag

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

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

   Floot—none0/10

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

   ⚑ flag

4. ai-native userSelf-host the core product

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

   Floot~partialclaimed5/10

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

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

   proof ↗⚑ flag

Pricing

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

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

   Floot—none0/10

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

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

   proof ↗⚑ flag

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

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

   Floot—none0/10

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

   ⚑ flag

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

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

   Floot—none0/10

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

   ⚑ flag

3. ai-native userControl data retention and deletion

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

   Floot—none0/10

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

   ⚑ flag

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

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

   Floot—none0/10

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

   ⚑ flag

Design import

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

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

   Floot—none0/10

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

   ⚑ flag

Generation

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

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

   Floot✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

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

   Floot✓fullprobed8/10

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

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

   proof ↗⚑ flag

Programmatic generation

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

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

   Floot~partialprobed6/10

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

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

   proof ↗⚑ flag

Templates

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

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

   Floot—none0/10

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

   ⚑ flag