Lovable vs Base44

Agent access

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

   weight 2 · round drawn
   Lovable✓fullprobed9/10

   Direct probe evidence confirms Lovable serves an llms.txt file at docs.lovable.dev/llms.txt with a 200 response and structured summary content, directly satisfying the story of pointing an agent at agent-oriented docs; docs also show broader agent-friendly integrations (MCP server, custom MCP, API) reinforcing agenticness. Missing for 10: no independent/community corroboration that external agents actually consume this llms.txt successfully.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.lovable.dev/llms.txt # Lovable Documentation > Lovable Documentation — Build full-stack websites w…”
   • [claimed-docs] “your AI agent can create projects, send messages to Lovable, inspect code, deploy apps, and more, all without leaving the client you're alre…”
   • [claimed-docs] “Lovable can read from it as live context while you build: internal CRMs, private APIs, company knowledge bases, or niche third-party tools.”

   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
   Lovable~partialclaimed3/10

   Lovable exposes an MCP server that lets external AI agents create projects, send messages, inspect code, and deploy programmatically, and a 'Build with URL' API for pre-filled prompts, which could enable some automated/programmatic triggering — but there is no documentation of a CLI, headless run mode, or CI/pipeline integration for automated builds. missing for 10: CLI/headless execution mode, explicit CI pipeline support, documentation of non-interactive automated runs.

   • [claimed-docs] “your AI agent can create projects, send messages to Lovable, inspect code, deploy apps, and more, all without leaving the client you're alre…”
   • [claimed-docs] “The Lovable API Build with URL feature lets you create links that open Lovable with a prompt already written, and optionally with reference …”
   • [claimed-docs] “Turn a published Lovable app into an MCP server for ChatGPT, Claude, and other AI assistants. Configure tools, sign-in, permissions, and acc…”

   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 Lovable
   Lovable✓fullclaimed8/10

   Lovable explicitly supports plugging in MCP servers via custom MCP connectors and MCP registries, letting the app 'read from it as live context' from internal CRMs, private APIs, or third-party tools, and lets members pick servers from a registry to connect as chat connectors. missing for 10: independent/hands-on verification of connecting a third-party MCP server and using its tools in a live build, and more detail on tool invocation mechanics.

   • [claimed-docs] “Lovable can read from it as live context while you build: internal CRMs, private APIs, company knowledge bases, or niche third-party tools.”
   • [claimed-docs] “members then pick servers from it and connect them as chat connectors in a couple of clicks, instead of finding and pasting each server's UR…”
   • [claimed-docs] “the ClickHouse app + chat connector lets your Lovable app run SQL queries against your ClickHouse database over the HTTP interface”
   • [claimed-docs] “You get everything in the web app plus local MCP server support, multi-project tabs, and keyboard shortcuts.”

   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 userConnect an agent via an official MCP server

   weight 3 · round to Lovable
   Lovable✓fullclaimed8/10

   Lovable documents an official MCP server integration: an AI agent can create projects, send messages to Lovable, inspect code, deploy apps, and more via the Lovable MCP server, plus local MCP server support in the desktop app and the ability to turn published apps into MCP servers for ChatGPT/Claude. Missing for 10: independent/hands-on confirmation that the official MCP server works as documented, and more detail on setup/auth flow beyond the docs summary.

   • [claimed-docs] “your AI agent can create projects, send messages to Lovable, inspect code, deploy apps, and more, all without leaving the client you're alre…”
   • [claimed-docs] “You get everything in the web app plus local MCP server support, multi-project tabs, and keyboard shortcuts.”
   • [claimed-docs] “Turn a published Lovable app into an MCP server for ChatGPT, Claude, and other AI assistants. Configure tools, sign-in, permissions, and acc…”
   • [claimed-docs] “Turn a published Lovable app into an MCP server for ChatGPT, Claude, and other AI assistants.”

   proof ↗⚑ flag

   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

5. ai-native userUse an official CLI

   weight 2 · round to Base44
   Lovable—none0/10

   The evidence pack covers Lovable's web app, desktop app, mobile app, MCP server integrations, Git sync, and API-based URL building, but no official CLI tool is mentioned anywhere in the docs or community evidence.

   ⚑ 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

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

   weight 3 · round to Lovable
   Lovable✓fullprobed8/10

   Lovable documents an official MCP server that lets an AI agent create projects, send messages, inspect code, and deploy apps entirely programmatically without leaving the agent's client, which is precisely a documented public interface for AI-native control; there's also a 'Build with URL' API for prompt-driven project creation. Missing for 10: a traditional REST/OpenAPI spec (probe confirms no openapi.json found) and independent third-party corroboration of agents actually driving Lovable via this API.

   • [claimed-docs] “your AI agent can create projects, send messages to Lovable, inspect code, deploy apps, and more, all without leaving the client you're alre…”
   • [claimed-docs] “The Lovable API Build with URL feature lets you create links that open Lovable with a prompt already written, and optionally with reference …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.lovable.dev/openapi.json, https://docs.lovable.dev/swagger.json, https://docs.lovable.d…”

   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

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

   weight 2 · round to Lovable
   Lovable~partialclaimed4/10

   Lovable lets you turn a published app into an MCP server and 'configure tools, sign-in, permissions, and access' for the AI assistants that connect, and enterprise plans add 'granular access controls' and centralized identity — both gesture at scoping what an agent can do. However, there's no documented mechanism for issuing discrete, least-privilege API keys/tokens (e.g., scoped, expiring, revocable credentials) specifically for an agent to use Lovable's own APIs. Missing for 10: explicit scoped/short-lived API credential issuance, per-agent token management, revocation/audit workflow tied to individual credentials.

   • [claimed-docs] “Turn a published Lovable app into an MCP server for ChatGPT, Claude, and other AI assistants. Configure tools, sign-in, permissions, and acc…”
   • [claimed-docs] “Turn a published Lovable app into an MCP server for ChatGPT, Claude, and other AI assistants.”
   • [claimed-docs] “centralized identity, granular access controls, workspace-wide security oversight, scheduled Deep scans, audit logs, regional code hosting”

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

8. ai-native userBuild against official SDKs

   weight 2 · round to Base44
   Lovable—none0/10

   Lovable documents an MCP server integration and a lightweight 'Build with URL' API for triggering prompts, but there is no evidence of an official SDK (e.g., Python/JS client libraries) for developers to build against, and probes for an OpenAPI/swagger spec all returned 404s. missing for 10: dedicated SDK packages/docs, published API reference, and independent confirmation of programmatic SDK usage.

   • [claimed-docs] “The Lovable API Build with URL feature lets you create links that open Lovable with a prompt already written, and optionally with reference …”
   • [claimed-docs] “your AI agent can create projects, send messages to Lovable, inspect code, deploy apps, and more, all without leaving the client you're alre…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.lovable.dev/openapi.json, https://docs.lovable.dev/swagger.json, https://docs.lovable.d…”

   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

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Lovable—none0/10

   Lovable's docs describe it acting as an MCP client/server, database/backend features, and integrations (GitHub, Slack, ClickHouse), but there is no evidence of a webhook subscription mechanism for external systems to receive events from Lovable projects or the platform itself.

   ⚑ 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 drawn
   Lovable—none0/10

   Lovable's docs describe database creation, SQL querying, and AI connectors for building AI features into apps, but there is no evidence that Lovable itself analyzes a user's data and proactively surfaces AI-generated insights or suggestions inside the product experience.

   • [claimed-docs] “For direct database access, use the SQL editor at Cloud tab → SQL editor”
   • [claimed-docs] “For direct database access, use the SQL editor at **Cloud tab → SQL editor**”
   • [claimed-docs] “Lovable's built-in AI connector handles that setup for you, so you can add AI features to your app by describing what you want to build.”
   • [claimed-docs] “Describe the data your app needs in chat, and Lovable creates the tables and schema for you.”

   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
   Lovable—none0/10

   Lovable's Build/Agent mode executes tasks end-to-end but only when explicitly invoked by a user prompt (docs-4, docs-29, docs-30), not as a background/scheduled automation. The only autonomous background action found is enterprise 'scheduled Deep scans' for security auditing (docs-46), which is a narrow compliance feature, not a general-purpose automation/scheduling capability for building autonomous background workflows.

   • [claimed-docs] “Build mode (previously Agent mode) is Lovable's autonomous execution mode, designed to implement changes directly in your project. When you …”
   • [claimed-docs] “Build mode (previously Agent mode) is Lovable’s autonomous execution mode, designed to implement changes directly in your project. When you …”
   • [claimed-docs] “Lovable working on a request doesn't block you. Send a follow-up, a correction, or a new idea at any time to steer the work”
   • [claimed-docs] “centralized identity, granular access controls, workspace-wide security oversight, scheduled Deep scans, audit logs, regional code hosting”

   proof ↗⚑ 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
   Lovable✓fullcommunity8/10

   Lovable's core interaction model is a chat-based AI assistant with an explicit 'Build mode' (formerly Agent mode) described as an autonomous execution mode that takes ownership of tasks end-to-end, applies changes via diffs, and lets users issue follow-ups asynchronously while it works. Community use (PM prototyping, internal dashboards) corroborates people actually delegating build tasks to it via chat, and docs show it can also perform actions like publish/deploy from chat commands. Missing for 10: independent benchmark or hands-on validation of the autonomy claims (e.g., how well it handles complex multi-step tasks unattended) and a clearer sense of failure/success rate limits.

   • [claimed-docs] “Build mode (previously Agent mode) is Lovable's autonomous execution mode, designed to implement changes directly in your project. When you …”
   • [claimed-docs] “Build mode (previously Agent mode) is Lovable's autonomous execution mode, designed to implement changes directly in your project.”
   • [claimed-docs] “Build mode (previously Agent mode) is Lovable’s autonomous execution mode, designed to implement changes directly in your project. When you …”
   • [claimed-docs] “Lovable working on a request doesn't block you. Send a follow-up, a correction, or a new idea at any time to steer the work”
   • [claimed-docs] “Lovable applies changes directly to your project when using Build mode. All modifications are visible through file diffs and summaries.”
   • [claimed-docs] “you describe what you want in the chat panel on the left, and you watch your app take shape in the preview on the right”
   • [claimed-docs] “you can also ask Lovable to run project actions from chat, for example publish my app, deploy this project, ship it, or find me a domain for…”
   • [claimed-docs] “Ask Lovable to publish, deploy, ship, or go live, and it handles the deploy for you while respecting all publish-related workspace settings …”
   • [community] “"I'm using Lovable heavily for PM prototyping and it's great. I think, if anything, current subscription may be too cheap!"”
   • [community] “Startup CTO uses Lovable heavily for internal dashboards/CRUD tools; saved the equivalent of two full-time developers, but generated code is…”

   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 to Lovable
   Lovable✓fullcommunity9/10

   Lovable's entire interaction model is natural-language: users describe apps, request auth, database schemas, publishing, and even run project actions ('publish my app', 'deploy this project') directly from chat, with the agent taking ownership of execution end to end. This is corroborated across docs (chat panel, Build mode, database/auth generation) and independent usage reports confirming real prototyping via prompts, though quality of generated output is debated. Missing for 10: no independent benchmark of command breadth/reliability beyond anecdotal community reports.

   • [claimed-docs] “You describe what you want to build, and Lovable generates a working application that includes frontend, backend, database, authentication, …”
   • [claimed-docs] “Build mode (previously Agent mode) is Lovable's autonomous execution mode, designed to implement changes directly in your project. When you …”
   • [claimed-docs] “Build mode (previously Agent mode) is Lovable’s autonomous execution mode, designed to implement changes directly in your project. When you …”
   • [claimed-docs] “Describe the data your app needs in chat, and Lovable creates the tables and schema for you.”
   • [claimed-docs] “you describe what you want in the chat panel on the left, and you watch your app take shape in the preview on the right”
   • [claimed-docs] “you can also ask Lovable to run project actions from chat, for example publish my app, deploy this project, ship it, or find me a domain for…”
   • [claimed-docs] “Ask Lovable to publish, deploy, ship, or go live, and it handles the deploy for you while respecting all publish-related workspace settings …”
   • [community] “"I'm using Lovable heavily for PM prototyping and it's great. I think, if anything, current subscription may be too cheap!"”
   • [community] “Startup CTO uses Lovable heavily for internal dashboards/CRUD tools; saved the equivalent of two full-time developers, but generated code is…”

   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 userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Lovable—none0/10

   Lovable is an app-building platform, not an API-first product, but a machine-readable API spec is still a fair ask for AI-native consumption of its own API/MCP surface; the probe explicitly found all OpenAPI candidate paths returning 404, and no docs mention an OpenAPI or equivalent machine-readable spec being downloadable.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.lovable.dev/openapi.json, https://docs.lovable.dev/swagger.json, https://docs.lovable.d…”

   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

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

   weight 1 · round drawn
   Lovable~partialclaimed4/10

   Lovable offers workarounds like GitHub branch testing outside production (lovable-docs-14/20) and 'drafts' as separate copies with independent chat/preview (lovable-docs-34), which can approximate sandboxed testing, but there is no explicit built-in staging/sandbox database or environment separation from production data in the Cloud backend docs. missing for 10: dedicated staging/sandbox database environment, explicit dev/prod data isolation in Cloud backend, first-party documentation of a sandbox testing mode.

   • [claimed-docs] “you can export and sync your project to GitHub: back up your code, review changes in pull requests, work locally in your IDE, test features …”
   • [claimed-docs] “back up your code, review changes in pull requests, work locally in your IDE, test features on branches, and deploy outside Lovable”
   • [claimed-docs] “When several people build in the same project, each of you can work in your own draft: a separate copy of the project with its own chat and …”
   • [claimed-docs] “Lovable hosts your app and includes a built-in backend (Cloud) with database, authentication, storage, edge functions, and AI, no infrastruc…”

   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

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

   weight 2 · round drawn
   Lovable—none0/10

   No evidence of a versioned API or a documented deprecation policy; probe for OpenAPI spec returned 404 on all candidate paths, and docs mention a 'Lovable API' for build-with-url links only without versioning/deprecation info.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.lovable.dev/openapi.json, https://docs.lovable.dev/swagger.json, https://docs.lovable.d…”
   • [claimed-docs] “The Lovable API Build with URL feature lets you create links that open Lovable with a prompt already written, and optionally with reference …”

   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
   Lovable—none0/10

   The evidence pack describes app-building, database schema creation, and SQL editor access, but nothing about performing bulk operations across many items (e.g., batch editing records, bulk API calls, mass content operations) as a distinct AI-native capability. No feature, doc, or community report addresses bulk operations at scale.

   ⚑ 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
   Lovable—none0/10

   No evidence of any scheduling, cron, or recurring-workflow capability in Lovable's docs; the product focuses on chat-driven app generation, edge functions, and one-off deploys with no mention of scheduled/recurring job execution.

   ⚑ 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 Lovable
   Lovable~partialclaimed5/10

   Lovable supports Git sync/export to GitHub or GitLab enabling version control, PR review, and branch-based testing (lovable-docs-14, lovable-docs-20, lovable-docs-33), and the Telegram bot integration mentions checking 'edit history' (lovable-docs-51). However, this is framed around app/code versioning, not specifically 'automations' as a distinct artifact, and there's no dedicated in-app rollback UI, automation-specific version history, or diff-based rollback mechanism described beyond Git-based workflows. missing for 10: native in-app rollback/version history UI independent of Git, explicit automation-specific versioning (vs. general app code), and independent/hands-on confirmation that rollback works reliably in practice.

   • [claimed-docs] “you can export and sync your project to GitHub: back up your code, review changes in pull requests, work locally in your IDE, test features …”
   • [claimed-docs] “back up your code, review changes in pull requests, work locally in your IDE, test features on branches, and deploy outside Lovable”
   • [claimed-docs] “Git sync connects a Lovable project to a repository you own on GitHub or GitLab, and keeps the two in sync automatically”
   • [claimed-docs] “Check edit history and review what changed... Query your project database with read-only queries”
   • [claimed-docs] “Work locally in your IDE. Clone the repository, edit and commit locally, and push. Your changes sync back into Lovable.”

   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 Lovable
   Lovable✓fullclaimed8/10

   Lovable's docs explicitly describe a built-in AI connector that handles LLM/agent setup so users can add AI features by describing them, without managing provider keys, as part of the built-in Cloud backend (database, auth, storage, edge functions, AI). Missing for 10: independent/hands-on verification of the AI connector's provider-key management and details on supported models/providers.

   • [claimed-docs] “Lovable's built-in AI connector handles that setup for you, so you can add AI features to your app by describing what you want to build.”
   • [claimed-docs] “Lovable hosts your app and includes a built-in backend (Cloud) with database, authentication, storage, edge functions, and AI, no infrastruc…”
   • [claimed-docs] “Lovable hosts your app and includes a built-in backend (Cloud) with a database, storage, authentication, realtime, and functions.”

   proof ↗⚑ 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 Lovable
   Lovable✓fullclaimed9/10

   Docs explicitly describe generating signup/login pages wired to the backend with row-level security, and managing sign-in via email, phone, Google, Apple, Microsoft, and SAML SSO through the built-in Cloud backend (Supabase-based). This directly matches the story of scaffolding auth with email and social providers via the builder. Missing for 10: independent hands-on confirmation that social provider login actually works end-to-end (community evidence focuses on other aspects like performance/security disclaimers, not auth scaffolding specifically).

   • [claimed-docs] “Ask Lovable to add login, and it generates the signup and login pages, wires them to your backend, and protects user data with row level sec…”
   • [claimed-docs] “Ask Lovable to add login, and it generates the signup and login pages, wires them to your backend, and protects user data with row level sec…”
   • [claimed-docs] “Manage your app's users and configure how they sign in: email, phone, Google, Apple, Microsoft, and SAML SSO, all part of the built-in backe…”
   • [claimed-docs] “Lovable hosts your app and includes a built-in backend (Cloud) with database, authentication, storage, edge functions, and AI, no infrastruc…”
   • [claimed-docs] “The built-in backend utilizes Supabase's open-source foundation, which means you get a production-ready environment from day one, without ne…”

   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 drawn
   Lovable✓fullclaimed8/10

   Lovable's built-in Cloud backend provisions a database automatically as part of app generation, lets users describe data in chat to create tables/schema, and exposes a SQL editor for direct access, all without leaving the builder; it's built on Supabase's foundation so no separate setup is needed. missing for 10: independent/hands-on confirmation specifically validating the database provisioning flow (community evidence discusses other pain points, not this one).

   • [claimed-docs] “Lovable hosts your app and includes a built-in backend (Cloud) with database, authentication, storage, edge functions, and AI, no infrastruc…”
   • [claimed-docs] “Lovable hosts your app and includes a built-in backend (Cloud) with a database, storage, authentication, realtime, and functions.”
   • [claimed-docs] “Describe the data your app needs in chat, and Lovable creates the tables and schema for you.”
   • [claimed-docs] “For direct database access, use the SQL editor at **Cloud tab → SQL editor**”
   • [claimed-docs] “The built-in backend utilizes Supabase's open-source foundation, which means you get a production-ready environment from day one, without ne…”

   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 Lovable
   Lovable✓fullcommunity7/10

   Lovable ships built-in Basic and Deep security scanners specifically for reviewing generated apps for vulnerabilities, with enterprise tiers adding scheduled Deep scans and audit logs, directly matching the pre-launch security review story. Missing for 10: independent/hands-on verification that the scanners catch real vulnerabilities, and community commentary (disclaimer requiring users to take responsibility for security, reports of abandoned apps with exposed data) raises doubt about how effective the review is in practice.

   • [claimed-docs] “Lovable includes two built-in security scanners, Basic scan and Deep scan, plus optional connectors for additional coverage.”
   • [claimed-docs] “Lovable includes two built-in security scanners, Basic scan and Deep scan, plus optional connectors for additional coverage”
   • [claimed-docs] “Lovable includes two built-in security scanners, **Basic scan** and **Deep scan**, plus optional connectors for additional coverage.”
   • [claimed-docs] “Lovable provides two built-in security scanners: Basic scan and Deep scan.”
   • [claimed-docs] “centralized identity, granular access controls, workspace-wide security oversight, scheduled Deep scans, audit logs, regional code hosting”
   • [community] “Signed up for Lovable, picked a template, got a disclaimer to 'take responsibility over project security, compliance, data, operations' with…”
   • [community] “"Lovable is marketed to non developers, so their core users wouldn't understand a security flow if it flashed red... Several were made on lo…”

   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 Lovable
   Lovable~partialclaimed6/10

   Lovable's built-in Cloud backend explicitly includes edge/serverless functions and supports connecting third-party services via chat connectors, custom MCP servers, and an AI connector (lovable-docs-27, -31, -40, -41, -44), and Build mode lets developers add these directly from the builder chat (lovable-docs-4, -29). However, no evidence specifically documents built-in payments or email-sending integrations (e.g., Stripe, Resend/SendGrid) — missing for 10: explicit payments integration docs, explicit transactional email integration docs, and independent confirmation these work end-to-end.

   • [claimed-docs] “Lovable hosts your app and includes a built-in backend (Cloud) with database, authentication, storage, edge functions, and AI, no infrastruc…”
   • [claimed-docs] “Lovable hosts your app and includes a built-in backend (Cloud) with a database, storage, authentication, realtime, and functions.”
   • [claimed-docs] “Lovable's built-in AI connector handles that setup for you, so you can add AI features to your app by describing what you want to build.”
   • [claimed-docs] “Lovable can read from it as live context while you build: internal CRMs, private APIs, company knowledge bases, or niche third-party tools.”
   • [claimed-docs] “the ClickHouse app + chat connector lets your Lovable app run SQL queries against your ClickHouse database over the HTTP interface”
   • [claimed-docs] “Build mode (previously Agent mode) is Lovable's autonomous execution mode, designed to implement changes directly in your project. When you …”

   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 drawn
   Lovable✓fullcommunity8/10

   Lovable explicitly supports downloading the full codebase or syncing to GitHub/GitLab, working locally in an IDE, and deploying outside Lovable via Git sync/export (lovable-docs-10, 14, 20, 33). Community comments (e.g. switching a Lovable-built site to Cursor/Astro) corroborate that exported code can be worked with outside the platform, though with quality caveats. Missing for 10: independent verification of a fully self-hostable backend (Supabase-based Cloud features may require re-setup outside Lovable), and no first-party doc detailing a clean 'run anywhere' deployment guide beyond GitHub sync.

   • [claimed-docs] “If you only need a copy of your code, you can download your code directly from Lovable: use the Download codebase section in Project setting…”
   • [claimed-docs] “you can export and sync your project to GitHub: back up your code, review changes in pull requests, work locally in your IDE, test features …”
   • [claimed-docs] “back up your code, review changes in pull requests, work locally in your IDE, test features on branches, and deploy outside Lovable”
   • [claimed-docs] “Git sync connects a Lovable project to a repository you own on GitHub or GitLab, and keeps the two in sync automatically”
   • [claimed-docs] “Work locally in your IDE. Clone the repository, edit and commit locally, and push. Your changes sync back into Lovable.”
   • [community] “Friend built a niche news site with Lovable using WordPress as headless CMS; Lovable built a monstrosity with Cloudflare workers, no proper …”

   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 drawn
   Lovable✓fullclaimed8/10

   Docs explicitly describe the Git sync workflow: clone repo, edit and commit locally in your own IDE, push changes, and they sync back into Lovable, plus code download and PR-based review/branch workflows for integrating with existing engineering tooling. Missing for 10: independent/hands-on confirmation that the local push-back sync works reliably without conflicts; community evidence focuses on generated code quality rather than the git-sync round-trip experience.

   • [claimed-docs] “Work locally in your IDE. Clone the repository, edit and commit locally, and push. Your changes sync back into Lovable.”
   • [claimed-docs] “Git sync connects a Lovable project to a repository you own on GitHub or GitLab, and keeps the two in sync automatically”
   • [claimed-docs] “you can export and sync your project to GitHub: back up your code, review changes in pull requests, work locally in your IDE, test features …”
   • [claimed-docs] “back up your code, review changes in pull requests, work locally in your IDE, test features on branches, and deploy outside Lovable”
   • [claimed-docs] “If you only need a copy of your code, you can download your code directly from Lovable: use the Download codebase section in Project setting…”

   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
   Lovable✓fullclaimed8/10

   Lovable's Git sync explicitly connects a project to a repo you own on GitHub/GitLab and keeps them in sync automatically, supporting bidirectional flow (clone, edit, commit, push locally, changes sync back into Lovable) plus PR review workflows. missing for 10: independent/hands-on confirmation of sync reliability and edge-case handling (merge conflicts, large diffs) beyond first-party docs.

   • [claimed-docs] “Each project represents a single application and produces a codebase that can be synced to GitHub or GitLab with Git sync and integrated int…”
   • [claimed-docs] “Work locally in your IDE. Clone the repository, edit and commit locally, and push. Your changes sync back into Lovable.”
   • [claimed-docs] “you can export and sync your project to GitHub: back up your code, review changes in pull requests, work locally in your IDE, test features …”
   • [claimed-docs] “back up your code, review changes in pull requests, work locally in your IDE, test features on branches, and deploy outside Lovable”
   • [claimed-docs] “Git sync connects a Lovable project to a repository you own on GitHub or GitLab, and keeps the two in sync automatically”

   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 Lovable
   Lovable✓fullclaimed8/10

   Lovable explicitly supports shared workspaces where teams can invite designers, developers, and others to collaborate in real time, with everyone seeing changes live, plus multi-person editing via separate drafts and workspace-level skills/enterprise access controls for teams. Missing for 10: independent hands-on validation of multi-user concurrency at scale and conflict resolution details beyond the 'draft' mechanism.

   • [claimed-docs] “Lovable lets you build websites together. Invite your designer, developer, agency, or anyone else. Everyone sees changes as they happen.”
   • [claimed-docs] “When several people build in the same project, each of you can work in your own draft: a separate copy of the project with its own chat and …”
   • [claimed-docs] “Invite your designer, developer, agency, or anyone else. Everyone sees changes as they happen.”
   • [claimed-docs] “Define a skill once at the workspace level, and Lovable can use it across every project in that workspace.”
   • [claimed-docs] “Anyone with an email address can sign up for free... Lovable automatically creates your first personal workspace on the free plan”
   • [claimed-docs] “centralized identity, granular access controls, workspace-wide security oversight, scheduled Deep scans, audit logs, regional code hosting”

   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
   Lovable✓fullclaimed8/10

   Lovable's docs explicitly cover custom domain connection, including buying, connecting, verifying, troubleshooting, and managing custom domains for a published app, replacing the default lovable.app URL. Missing for 10: independent/hands-on confirmation of the domain connection flow working smoothly (community evidence is silent on this specific feature).

   • [claimed-docs] “A custom domain lets you use your own domain or subdomain for your Lovable project instead of the default xxx.lovable.app URL.”
   • [claimed-docs] “A custom domain lets you use your own domain or subdomain for your Lovable project instead of the default xxx.lovable.app URL”
   • [claimed-docs] “A **custom domain** lets you use your own domain or subdomain for your Lovable project instead of the default `xxx.lovable.app` URL.”
   • [claimed-docs] “Learn how to buy, connect, verify, troubleshoot, and manage custom domains in Lovable.”
   • [claimed-docs] “Publishing turns your Lovable project into a live web app by deploying a snapshot to a URL you can share.”

   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 Lovable
   Lovable~partialclaimed6/10

   Docs confirm you can sync/export the generated codebase to GitHub/GitLab and explicitly state this lets you 'deploy outside Lovable' or download the code directly, satisfying the core ask, but Lovable's native workflow is oriented toward its own hosted 'Publish' and custom-domain features rather than first-class one-click integrations with external hosts (Vercel, AWS, etc.). Missing for 10: documented native deploy integrations/CI templates for specific external hosts, and independent hands-on confirmation that exported code deploys cleanly elsewhere.

   • [claimed-docs] “you can export and sync your project to GitHub: back up your code, review changes in pull requests, work locally in your IDE, test features …”
   • [claimed-docs] “back up your code, review changes in pull requests, work locally in your IDE, test features on branches, and deploy outside Lovable”
   • [claimed-docs] “If you only need a copy of your code, you can download your code directly from Lovable: use the Download codebase section in Project setting…”
   • [claimed-docs] “Git sync connects a Lovable project to a repository you own on GitHub or GitLab, and keeps the two in sync automatically”
   • [claimed-docs] “Code: Your app's source code, which you can browse, edit, and download.”

   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 Lovable
   Lovable✓fullclaimed9/10

   Lovable's docs describe one-step publishing ("Publishing takes two clicks") that deploys a snapshot to a shareable live URL, plus chat-driven publish commands like 'publish my app' or 'ship it', directly matching the founder story. Custom domain support further extends this to branded URLs. Missing for 10: independent hands-on confirmation of the publish flow's simplicity (only vendor docs, no third-party corroboration of the exact one-click experience).

   • [claimed-docs] “Publishing turns your Lovable project into a live web app by deploying a snapshot to a URL you can share.”
   • [claimed-docs] “Publishing takes two clicks, and the defaults work for most projects”
   • [claimed-docs] “Ask Lovable to publish, deploy, ship, or go live, and it handles the deploy for you while respecting all publish-related workspace settings …”
   • [claimed-docs] “you can also ask Lovable to run project actions from chat, for example publish my app, deploy this project, ship it, or find me a domain for…”
   • [claimed-docs] “Build your first app and put it live on the web with about ten minutes of hands-on time. There is nothing to install and nothing to configur…”

   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 drawn
   Lovable✓fullclaimed7/10

   Lovable ships an official MCP server (and desktop-app local MCP support) that lets an external AI agent create projects, send messages, inspect code, and deploy apps 'without leaving the client you're already working in,' which is exactly the story of connecting one's own coding agent to drive the project instead of/alongside the built-in one. Git sync also lets developers edit locally in their own IDE/agent and sync back into Lovable. Missing for 10: independent/hands-on evidence validating the MCP-driven workflow works well in practice, and more detail on how fully an external agent can 'replace' Build mode versus just issuing commands to it.

   • [claimed-docs] “your AI agent can create projects, send messages to Lovable, inspect code, deploy apps, and more, all without leaving the client you're alre…”
   • [claimed-docs] “You get everything in the web app plus local MCP server support, multi-project tabs, and keyboard shortcuts.”
   • [claimed-docs] “Git sync connects a Lovable project to a repository you own on GitHub or GitLab, and keeps the two in sync automatically”
   • [claimed-docs] “Work locally in your IDE. Clone the repository, edit and commit locally, and push. Your changes sync back into Lovable.”

   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 Lovable
   Lovable!disputedcontradicted5/10

   First-party docs explicitly state the Code tab lets you 'browse, edit, and download' source, and Build mode diffs are shown in-editor, supporting direct in-app code editing. However, an independent hands-on account reports that a Lovable project came with copy/paste disabled, directly undercutting the claim that generated code can be freely edited inside the builder. missing for 10: independent corroboration that in-editor code editing works unrestricted, clarification on why copy/paste was disabled in the reported case.

   • [claimed-docs] “Code: Your app's source code, which you can browse, edit, and download.”
   • [claimed-docs] “Lovable applies changes directly to your project when using Build mode. All modifications are visible through file diffs and summaries.”
   • [community] “Signed up for Lovable, picked a template, got a disclaimer to 'take responsibility over project security, compliance, data, operations' with…”

   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 Lovable
   Lovable✓fullclaimed8/10

   Docs describe the core editor experience: users describe changes in chat and watch the app take shape in a live preview panel before publishing, with Build mode applying changes visibly via diffs and a separate explicit publish step. This directly matches the founder story of interacting with a live preview pre-publish. Missing for 10: no independent/hands-on account specifically confirming the live-preview interaction quality or responsiveness, and no detail on preview limitations (e.g., for complex backend/data scenarios).

   • [claimed-docs] “you describe what you want in the chat panel on the left, and you watch your app take shape in the preview on the right”
   • [claimed-docs] “Lovable applies changes directly to your project when using Build mode. All modifications are visible through file diffs and summaries.”
   • [claimed-docs] “Publishing turns your Lovable project into a live web app by deploying a snapshot to a URL you can share.”
   • [claimed-docs] “Ask Lovable to publish, deploy, ship, or go live, and it handles the deploy for you while respecting all publish-related workspace settings …”
   • [claimed-docs] “Lovable working on a request doesn't block you. Send a follow-up, a correction, or a new idea at any time to steer the work”

   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 drawn
   Lovable~partialcommunity5/10

   Docs confirm iterative refinement is core to Lovable's Build mode—users can send follow-ups, corrections, or new ideas at any time, with changes shown via diffs/summaries (lovable-docs-30, lovable-docs-43, lovable-docs-55)—but there's no explicit documentation of regression-safety or guarantees that new prompts won't break existing features. Community reports are mixed: some founders/PMs praise it for prototyping (lovable-comm-5, lovable-comm-13), while others note code quality degrades and complexity becomes unwieldy as apps grow (lovable-comm-9, lovable-comm-10), and one report cites frequent abandonment past 60-70% functionality (lovable-comm-7), suggesting iterative stability is not fully reliable at scale. missing for 10: explicit non-regression testing/safeguards, first-party evidence addressing 'without breaking existing functionality', and stronger independent confirmation of stable iterative editing on complex apps.

   • [claimed-docs] “Lovable working on a request doesn't block you. Send a follow-up, a correction, or a new idea at any time to steer the work”
   • [claimed-docs] “Lovable applies changes directly to your project when using Build mode. All modifications are visible through file diffs and summaries.”
   • [claimed-docs] “you describe what you want in the chat panel on the left, and you watch your app take shape in the preview on the right”
   • [community] “Startup CTO uses Lovable heavily for internal dashboards/CRUD tools; saved the equivalent of two full-time developers, but generated code is…”
   • [community] “"I recently used lovable to create the scaffolding for an app. It did a great job, far better than I expected. However, it also squishes eve…”
   • [community] “"I don't get how this company makes money. Everyone who uses these tools is just building prototypes. They get to 60-70% functionality, but …”
   • [community] “"I'm using Lovable heavily for PM prototyping and it's great. I think, if anything, current subscription may be too cheap!"”

   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 drawn
   Lovable—none0/10

   All documented editing evidence describes prompt/chat-driven generation (chat panel + preview, Build/Agent mode acting on instructions) and code-level editing via IDE/download, not a visual direct-manipulation editor where a designer selects an element and tweaks text/style/layout inline without a prompt. No docs or community reports mention a click-to-select/inline style editor.

   • [claimed-docs] “you describe what you want in the chat panel on the left, and you watch your app take shape in the preview on the right”
   • [claimed-docs] “Lovable applies changes directly to your project when using Build mode. All modifications are visible through file diffs and summaries.”
   • [claimed-docs] “Code: Your app's source code, which you can browse, edit, and download.”
   • [claimed-docs] “Build mode (previously Agent mode) is Lovable's autonomous execution mode, designed to implement changes directly in your project. When you …”

   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 drawn
   Lovable~partialprobed5/10

   Lovable exposes an official MCP server (and 'Build with URL' prompt links) letting an AI agent create projects, send messages, inspect code, and deploy apps 'without leaving the client' (lovable-docs-37, lovable-docs-53), which gives some programmatic parity with core chat/build/deploy actions. However, the probe found no public REST/OpenAPI spec (lovable-probe-2), and there's no evidence the API/MCP surface covers other UI capabilities like custom domains, security scans, collaboration/invites, billing, or database SQL editor access. Missing for 10: a documented general-purpose REST/GraphQL API, MCP/API coverage of domains, security scanning, collaboration, and billing equivalent to the UI.

   • [claimed-docs] “your AI agent can create projects, send messages to Lovable, inspect code, deploy apps, and more, all without leaving the client you're alre…”
   • [claimed-docs] “The Lovable API Build with URL feature lets you create links that open Lovable with a prompt already written, and optionally with reference …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.lovable.dev/openapi.json, https://docs.lovable.dev/swagger.json, https://docs.lovable.d…”

   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 Lovable
   Lovable~partialclaimed6/10

   Lovable lets users download or Git-sync the full generated codebase (open, standard code) and export to GitHub/GitLab for use outside the platform, which covers the 'code' portion of data export. However, the app's data (database records, user data) lives in Supabase-backed Cloud, and no docs describe a bulk data-export mechanism or open-format export of stored application data itself—only SQL editor access within the platform. missing for 10: documented database/data export (e.g., dump/backup) in open formats, and any evidence of a clean full account data export beyond code.

   • [claimed-docs] “Work locally in your IDE. Clone the repository, edit and commit locally, and push. Your changes sync back into Lovable.”
   • [claimed-docs] “If you only need a copy of your code, you can download your code directly from Lovable: use the Download codebase section in Project setting…”
   • [claimed-docs] “you can export and sync your project to GitHub: back up your code, review changes in pull requests, work locally in your IDE, test features …”
   • [claimed-docs] “back up your code, review changes in pull requests, work locally in your IDE, test features on branches, and deploy outside Lovable”
   • [claimed-docs] “Git sync connects a Lovable project to a repository you own on GitHub or GitLab, and keeps the two in sync automatically”
   • [claimed-docs] “For direct database access, use the SQL editor at **Cloud tab → SQL editor**”
   • [claimed-docs] “The built-in backend utilizes Supabase's open-source foundation, which means you get a production-ready environment from day one, without ne…”

   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 userSelf-host the core product

   weight 3 · round drawn
   Lovable—none0/10

   Lovable is presented throughout its docs as a fully hosted SaaS (Cloud backend, hosted publish/deploy, workspace plans) with no mention of a self-hostable core product, on-prem deployment, or open-source distribution; you can only export/download generated app code, not the Lovable platform itself.

   • [claimed-docs] “Lovable hosts your app and includes a built-in backend (Cloud) with database, authentication, storage, edge functions, and AI, no infrastruc…”
   • [claimed-docs] “Lovable hosts your app and includes a built-in backend (Cloud) with a database, storage, authentication, realtime, and functions.”
   • [claimed-docs] “Build your first app and put it live on the web with about ten minutes of hands-on time. There is nothing to install and nothing to configur…”
   • [claimed-docs] “Anyone with an email address can sign up for free... Lovable automatically creates your first personal workspace on the free plan”
   • [claimed-docs] “centralized identity, granular access controls, workspace-wide security oversight, scheduled Deep scans, audit logs, regional code hosting”

   proof ↗⚑ 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 Lovable
   Lovable~partialclaimed5/10

   Lovable docs mention a dedicated 'Plans & credit usage' settings page to track credit balance, usage, and top-ups (lovable-docs-59), which addresses the general need to monitor consumption. However there is no evidence of granular documentation showing what each specific action or message costs in credits, nor a clear breakdown of what different plans include, and no independent/community confirmation of pricing transparency. missing for 10: per-action credit cost breakdown, plan comparison details, independent user confirmation of pricing clarity.

   • [claimed-docs] “Use Settings → Plans & credit usage to understand your credit balance, track credit usage, add credits, and manage top-ups.”

   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 to Lovable
   Lovable~partialclaimed4/10

   Lovable's enterprise docs mention 'regional code hosting' as one of several enterprise features, indicating some data residency control exists for enterprise customers, but there's no detail on which regions, how it's configured, or whether it applies to database/user data (vs just code) or non-enterprise plans. missing for 10: region selection details, database/data storage residency (not just code hosting), self-serve availability for non-enterprise users, independent confirmation.

   • [claimed-docs] “centralized identity, granular access controls, workspace-wide security oversight, scheduled Deep scans, audit logs, regional code hosting”

   proof ↗⚑ 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
   Lovable—none0/10

   No evidence pack item mentions data usage for AI training, opt-out settings, or any privacy policy language addressing this concern. Missing for 10: any documentation on training data opt-out, privacy policy statements, or enterprise data-handling guarantees regarding model training.

   ⚑ 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
   Lovable—none0/10

   No evidence describes data retention policies, deletion workflows, or user controls for purging stored data/chat history; enterprise docs mention audit logs and regional hosting but not retention/deletion controls specifically.

   ⚑ 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
   Lovable—none0/10

   No evidence in the pack mentions telemetry, analytics opt-out, or usage-tracking controls for Lovable users; docs focus on app-building features, security scanners, and integrations without any privacy/tracking settings mentioned.

   ⚑ 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 Base44
   Lovable—none0/10

   No evidence in the pack shows Lovable can import a Figma file or existing design file and implement it; the closest mentions are attaching reference images/web pages to a prompt (lovable-docs-53) and a community comment contrasting Figma mockups with Lovable prototypes (lovable-comm-13), neither of which describes actual Figma file import.

   • [claimed-docs] “The Lovable API Build with URL feature lets you create links that open Lovable with a prompt already written, and optionally with reference …”
   • [community] “"As a product designer, I'm seriously looking at using Lovable for quick ideation and prototyping. Showing users a series of Figma screens c…”

   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 drawn
   Lovable✓fullcommunity8/10

   Docs clearly describe generating a full app—frontend, backend, database, authentication—from a single natural-language prompt (lovable-docs-1, lovable-docs-27, lovable-docs-32, lovable-docs-5), with autonomous end-to-end execution (lovable-docs-4/29). Community reports corroborate real backend/CRUD apps being built (lovable-comm-9), though quality concerns exist (messy code, abandoned production use). Missing for 10: independent hands-on verification of true backend logic complexity beyond CRUD/dashboards, and confirmation that generated backend logic scales beyond prototypes.

   • [claimed-docs] “You describe what you want to build, and Lovable generates a working application that includes frontend, backend, database, authentication, …”
   • [claimed-docs] “Lovable hosts your app and includes a built-in backend (Cloud) with database, authentication, storage, edge functions, and AI, no infrastruc…”
   • [claimed-docs] “Describe the data your app needs in chat, and Lovable creates the tables and schema for you.”
   • [claimed-docs] “Ask Lovable to add login, and it generates the signup and login pages, wires them to your backend, and protects user data with row level sec…”
   • [claimed-docs] “Build mode (previously Agent mode) is Lovable's autonomous execution mode, designed to implement changes directly in your project. When you …”
   • [community] “Startup CTO uses Lovable heavily for internal dashboards/CRUD tools; saved the equivalent of two full-time developers, but generated code is…”

   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
   Lovable~partialcommunity7/10

   Docs strongly support the core story: natural-language prompts generate a full-stack app (frontend, backend, database, auth, integrations) with built-in Cloud/Supabase backend and one-click publish (lovable-docs-1, lovable-docs-27, lovable-docs-31, lovable-docs-58). However, hands-on community reports show real caveats — generated apps can have performance/architecture problems (lovable-comm-1), code quality issues like unwieldy single-file structures and type-safety shortcuts (lovable-comm-9, lovable-comm-10), and reports that most projects stall at 60-70% functionality before production (lovable-comm-7, lovable-comm-8). Missing for 10: independent benchmark of end-to-end reliability across varied app types, and resolution of the production-readiness skepticism raised by users.

   • [claimed-docs] “You describe what you want to build, and Lovable generates a working application that includes frontend, backend, database, authentication, …”
   • [claimed-docs] “Lovable hosts your app and includes a built-in backend (Cloud) with database, authentication, storage, edge functions, and AI, no infrastruc…”
   • [claimed-docs] “Lovable hosts your app and includes a built-in backend (Cloud) with a database, storage, authentication, realtime, and functions.”
   • [claimed-docs] “Ask Lovable to publish, deploy, ship, or go live, and it handles the deploy for you while respecting all publish-related workspace settings …”
   • [community] “Friend built a niche news site with Lovable using WordPress as headless CMS; Lovable built a monstrosity with Cloudflare workers, no proper …”
   • [community] “Startup CTO uses Lovable heavily for internal dashboards/CRUD tools; saved the equivalent of two full-time developers, but generated code is…”
   • [community] “"I recently used lovable to create the scaffolding for an app. It did a great job, far better than I expected. However, it also squishes eve…”
   • [community] “"I don't get how this company makes money. Everyone who uses these tools is just building prototypes. They get to 60-70% functionality, but …”
   • [community] “"Lovable is a nice Website or App builder. Nothing for professionals, unless they want to build an prototype. Even building MVPs is nearly i…”

   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
   Lovable~partialprobed6/10

   Lovable exposes a documented MCP server ('your AI agent can create projects, send messages to Lovable, inspect code, deploy apps, and more') and a 'Build with URL' feature for prompt-driven app creation, giving AI-native users a programmatic path to generate and manage apps. However, there is no traditional REST/GraphQL platform API — probe checks for openapi/swagger endpoints all returned 404 — so programmatic management is limited to MCP tool calls rather than a full API surface. Missing for 10: a documented public REST/GraphQL API with endpoints for project CRUD, deployment, and management outside the MCP/chat paradigm, and independent evidence of developers using it at scale.

   • [claimed-docs] “your AI agent can create projects, send messages to Lovable, inspect code, deploy apps, and more, all without leaving the client you're alre…”
   • [claimed-docs] “The Lovable API Build with URL feature lets you create links that open Lovable with a prompt already written, and optionally with reference …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.lovable.dev/openapi.json, https://docs.lovable.dev/swagger.json, https://docs.lovable.d…”

   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
   Lovable~partialclaimed5/10

   Docs mention 'Remixing' lets you create your own independent copy of an existing project to edit freely, which supports starting from a community project instead of a blank prompt, but there is no evidence of an explicit template gallery/marketplace or curated starter templates. missing for 10: dedicated template library/gallery, curated starter templates, independent confirmation of remix discoverability.

   • [claimed-docs] “Remixing creates your own independent copy that you can edit freely, on any plan.”

   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