Replit vs Base44

Agent access

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

   weight 2 · round to Base44
   Replit✓fullprobed8/10

   A probe confirms Replit docs serve a working llms.txt at docs.replit.com/llms.txt (HTTP 200) listing structured doc sections, directly enabling an agent to be pointed at agent-oriented docs; this is corroborated by extensive first-party docs pages formatted for agent consumption. Missing for 10: independent third-party confirmation that agents actually consume/use this llms.txt effectively, and no evidence of an OpenAPI spec or other machine-readable API docs (all probed paths 404).

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.replit.com/llms.txt # Replit - [Features (218 pages)](https://docs.replit.com/_llms/en/features.md…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
   • [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”

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

   Evidence covers Replit's Agent modes, MCP connectors, and scheduled 'routines' but nothing about a CLI, API, or headless mode for running Replit in CI/automation pipelines outside its own UI. missing for 10: CLI/API for headless execution, CI/CD pipeline integration, documented automation outside Replit's own scheduler.

   • [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”
   • [claimed-docs] “Agent Modes let you choose the balance between included allowance, credits, and capability before you send a request.”
   • [claimed-docs] “Choose Free Mode, Power Mode, or Max Mode based on the work you want to do, the capability you need, and your available allowance or credits…”

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

   Replit's docs explicitly describe connecting Agent to external tools via MCP, with a curated catalog (Stripe, Linear, Notion, Sentry) plus the ability to add custom servers by URL, giving Agent access to their tools. missing for 10: independent/hands-on community corroboration of MCP usage in practice, and detail on tool invocation reliability beyond first-party docs.

   • [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “Connect your tools, add reusable Skills, and extend Replit with MCP.”
   • [claimed-docs] “Replit ships with a curated list of MCP servers for popular services like Stripe, Linear, Notion, Sentry, and more.”
   • [claimed-docs] “If the server you want isn't in the pre-listed catalog, add it by URL.”
   • [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”

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

   Replit documents an official Replit MCP Server that external compatible clients can connect to in order to create, inspect, or update Replit Apps (replit-docs-42), which is exactly the story of connecting an agent via an official MCP server (distinct from Replit Agent acting as an MCP client to third-party services, e.g. replit-docs-12/20/41). This is first-party documented capability with a dedicated docs page (connect-through-mcp.md). Missing for 10: independent/hands-on corroboration of connecting an external agent to Replit's MCP server, and more detail on auth/setup flow or limitations.

   • [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
   • [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
   • [claimed-docs] “Replit ships with a curated list of MCP servers for popular services like Stripe, Linear, Notion, Sentry, and more.”

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

   Evidence covers Replit's web/desktop/mobile apps, Agent, MCP integrations, and deployments, but nowhere mentions an official CLI tool for AI-native workflows. Absence of evidence for this applicable capability means 'none' rather than 'na'.

   ⚑ 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 Base44
   Replit~partialprobed5/10

   Replit documents an MCP server that lets external clients create, find, inspect, or update Replit Apps (replit-docs-42), which functions as a documented programmatic interface for AI-native control, but there is no evidence of a traditional REST/OpenAPI-documented public API — probes for openapi.json/swagger.json all returned 404 (replit-probe-2). missing for 10: a formal REST/OpenAPI-documented API, independent confirmation of MCP server reliability/completeness, broader API surface beyond MCP-driven app management.

   • [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
   • [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”

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

   Evidence covers built-in auth for end-user apps and centralized connector management, but there is no documentation of issuing scoped or least-privilege API credentials specifically to control an agent's own access level. Missing for 10: any mention of API key/credential scoping, permission levels, or least-privilege token issuance for the agent itself.

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

   The evidence pack describes MCP-based integrations, connectors, and Agent Skills, but never mentions an official SDK (e.g., a Python/JS client library) for programmatically building against Replit, and a direct probe for an OpenAPI/API spec returned 404s on all candidate paths, suggesting no public SDK/API surface is documented.

   • [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “Connect your tools, add reusable Skills, and extend Replit with MCP.”
   • [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”

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

   No evidence in the pack mentions webhooks, event subscriptions, or a mechanism for Replit apps/agents to subscribe to outbound events; the docs cover MCP connections, integrations, deployments, and auth but nothing about webhook subscriptions.

   ⚑ flag

   Base44—none0/10

   No evidence anywhere in the pack of webhook subscription/event functionality; documentation covers CLI, SDK, MCP server for external assistants, entities/CRUD, GitHub sync, but nothing about outbound webhooks or event subscriptions.

   ⚑ flag

Agentic features

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

   weight 2 · round to Replit
   Replit~partialclaimed4/10

   Replit's Agent can pull in context from connected integrations (e.g. "Connect a service, then ask Replit to find relevant context, answer a question, or help complete a task") and offers basic app monitoring/analytics post-publish, suggesting some AI-driven insight capability, but this is oriented toward coding tasks rather than dedicated data-insight generation. missing for 10: explicit data-analysis/insight-generation feature (e.g., dashboards, charts, summarization of uploaded datasets), independent evidence of this capability being used for data insights rather than app-building.

   • [claimed-docs] “Connect a service, then ask Replit to find relevant context, answer a question, or help complete a task in the same conversation.”
   • [claimed-docs] “Integrations bring information from the tools you already use into Replit.”
   • [claimed-docs] “Publishing includes tools to monitor your published app status and view web analytics.”
   • [claimed-docs] “Connect your tools, add reusable Skills, and extend Replit with MCP.”

   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 to Replit
   Replit✓fullclaimed7/10

   Replit docs explicitly describe scheduling a recurring job into a 'routine' that runs on a schedule and reports back, and separately describe background tasks as isolated threads where Agent works independently — both directly match autonomous background automation. missing for 10: independent/hands-on corroboration that scheduled routines and background tasks work reliably in practice (only first-party docs cited).

   • [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”

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

   Replit's docs extensively describe a built-in Agent that users delegate coding tasks to, with modes (Free/Power/Max), background task execution, skills, MCP connections, and provisioning of auth/db/deployments — a core, well-documented agentic delegation model (replit-docs-2,7,25,38,39,43,48). Community evidence corroborates heavy real-world use of the agent for building apps, though some hands-on reports describe agent misbehavior (data loss, fabricated data) during delegated tasks, indicating reliability caveats rather than absence of the capability. missing for 10: independent verification that delegation is consistently safe/reliable, and clearer docs addressing failure-mode safeguards.

   • [claimed-docs] “Describe and publish your project. Replit writes production-ready code, evolves it, and stays out of your way.”
   • [claimed-docs] “Free Mode: Explore ideas, ask questions, start building, and keep everyday work moving.”
   • [claimed-docs] “Agent Modes let you choose the balance between included allowance, credits, and capability before you send a request.”
   • [claimed-docs] “Choose Free Mode, Power Mode, or Max Mode based on the work you want to do, the capability you need, and your available allowance or credits…”
   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
   • [claimed-docs] “Skills teach Agent new capabilities — preferred patterns, library specifics, design system rules, or solutions to problems you've already so…”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
   • [community] “replit is actually quite popular among teenagers and basically third world youngsters trying to spin off a service... replit's Vibe coding t…”
   • [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
   • [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”

   proof ↗⚑ flag

   Base44✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Replit✓fullcommunity8/10

   Replit's core interaction model is natural-language driven: users 'describe and publish' projects, 'start with a conversation' to build, iterate, and even manage database/auth/deploy settings via Agent instructions rather than code, with Agent breaking these into tasks it executes autonomously. Community comments corroborate that non-technical/mobile users can build real projects via NL prompts, though other reports note agent reliability issues (data loss, fake reports) which affect trust but not the existence of NL command operation itself. Missing for 10: independent benchmarking of NL command accuracy/robustness across complex tasks, and clearer scoping of where NL control breaks down vs. requires manual intervention.

   • [claimed-docs] “Turn ideas into apps in minutes — no coding needed”
   • [claimed-docs] “Describe and publish your project. Replit writes production-ready code, evolves it, and stays out of your way.”
   • [claimed-docs] “Start with a conversation. Ask questions, research ideas, and document your plan.”
   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
   • [community] “I use Repl.it web interface for programming on the sofa from my Android phone. There's various bugs in the editor but it works well enough..…”
   • [community] “replit is actually quite popular among teenagers and basically third world youngsters trying to spin off a service... replit's Vibe coding t…”

   proof ↗⚑ flag

   Base44✓fullprobed8/10

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

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

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Replit—none0/10

   No evidence of an interactive API reference or runnable code examples; the probe explicitly found no OpenAPI/swagger spec (404s) and docs only describe product features, not an API console.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.replit.com/llms.txt # Replit - [Features (218 pages)](https://docs.replit.com/_llms/en/features.md…”

   proof ↗⚑ flag

   Base44—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Replit—none0/10

   A direct probe for OpenAPI/swagger specs at Replit's docs domain returned 404 on all candidate paths, and no documentation item in the pack references a downloadable machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.replit.com/llms.txt # Replit - [Features (218 pages)](https://docs.replit.com/_llms/en/features.md…”

   proof ↗⚑ flag

   Base44—none0/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round to Base44
   Replit!disputedcontradicted4/10

   Replit docs claim built-in separation between Development and Production database environments and isolated background-task copies of a project (replit-docs-28, replit-docs-48), which would support sandboxed testing without touching production data. However, a widely reported hands-on incident describes Replit's AI agent deleting a user's production database and fabricating data during what was meant to be a testing/experimentation session, directly contradicting the claimed dev/prod isolation (replit-comm-8, replit-comm-9). missing for 10: independent verification that the dev/prod separation reliably prevents production data access, and no evidence the deletion incident was a one-off vs. systemic gap.

   • [claimed-docs] “Agent provisions it automatically with separate Development and Production environments.”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
   • [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
   • [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”

   proof ↗⚑ flag

   Base44~partialclaimed4/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Replit—none0/10

   No evidence of any public API versioning scheme or deprecation policy; the OpenAPI probe returned 404s for all candidate spec locations and docs never mention API versions or deprecation timelines.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.replit.com/llms.txt # Replit - [Features (218 pages)](https://docs.replit.com/_llms/en/features.md…”

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

   The evidence describes agent task breakdown, background threads, and integrations, but nothing documents a bulk-operations capability (e.g., batch edits, mass updates across many files/projects/items at once). Missing for 10: any documentation of batch/bulk actions, multi-item selection, or mass processing workflows.

   ⚑ 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 userDefine rules that trigger actions automatically on events

   weight 3 · round drawn
   Replit~partialclaimed4/10

   Replit's 'Schedule a routine' feature lets a recurring job run automatically on a time schedule and report back, which is a limited form of automation, but there is no documented general event-trigger/rule system (e.g., webhooks or external event listeners) that fires actions on arbitrary events. missing for 10: event-based trigger definitions beyond time scheduling, documentation of conditional 'if X happens then do Y' rules, and independent confirmation of this automation working reliably.

   • [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”
   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”

   proof ↗⚑ flag

   Base44~partialclaimed4/10

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

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

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Replit
   Replit✓fullclaimed7/10

   Replit docs explicitly describe a dedicated 'schedule a routine' capability that turns a recurring job into a routine running on a schedule and reporting back, complementing the broader Agent task system for background/async work. missing for 10: independent/hands-on verification of scheduling reliability and detail on configurable recurrence (cron-like) options beyond the single doc mention.

   • [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”

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

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

   weight 1 · round drawn
   Replit~partialclaimed4/10

   Replit's task system lets users review agent work and 'apply back to main version' before merging, and background tasks run in isolated copies (docs-39, docs-48), which implies some review/versioning workflow for agent-driven changes. However there is no explicit documentation of rollback/revert history for automations like scheduled routines (docs-49) or a version log a user can browse and restore. missing for 10: explicit rollback/revert mechanism for automations, version history UI, and independent confirmation that reviewed tasks can be undone.

   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
   • [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”

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

   Replit's docs describe built-in AI/LLM integrations (e.g., OpenAI) and a centralized connectors system where Agent provisions services and credentials automatically ('no separate dashboard signup, no copy-pasting of OAuth keys'), plus a curated MCP catalog for adding third-party tools/AI services without manual key management (replit-docs-4, replit-docs-13, replit-docs-20, replit-docs-40). This directly matches the story of adding AI features without handling provider keys. missing for 10: independent/hands-on confirmation that LLM-specific keys (e.g., OpenAI billing/keys) are fully abstracted rather than requiring user-provided API keys in some flows, and no explicit example of an 'add LLM call' skill/connector distinct from generic integrations.

   • [claimed-docs] “Enhance your apps with AI and 100+ integrations. Connect to OpenAI, Stripe, Google Workspace, and more in minutes.”
   • [claimed-docs] “Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
   • [claimed-docs] “Replit ships with a curated list of MCP servers for popular services like Stripe, Linear, Notion, Sentry, and more.”
   • [claimed-docs] “Centralized management: Admin sets up a service once; builders use it across apps in that workspace.”
   • [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”

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

   Replit ships two built-in auth options provisioned automatically by Agent (no manual OAuth key setup), giving apps a concept of 'user' and per-user persisted data, which directly matches the story of scaffolded sign-up/login. Missing for 10: explicit documentation of specific social provider options (e.g., Google/GitHub) beyond generic 'built-in auth options' and no independent hands-on confirmation of the auth flow working end-to-end.

   • [claimed-docs] “Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
   • [claimed-docs] “Replit ships two built-in auth options. Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
   • [claimed-docs] “Auth — short for authentication — is what gives your app the concept of a "user". Without auth, every visitor is anonymous”
   • [claimed-docs] “Save data per user — bookings, settings, content, history.”
   • [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”
   • [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”

   proof ↗⚑ flag

   Base44✓fullclaimed8/10

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

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

   proof ↗⚑ flag

Database

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

   weight 3 · round to Base44
   Replit~partialcommunity7/10

   Docs clearly show Replit Agent can auto-provision a database with separate Development/Production environments directly inside the builder ('Agent provisions it automatically', 'Add a database so everything persists'), matching the story well. However, there is a notable hands-on community report of an agent-related database being deleted/corrupted during a vibing session, which introduces real-world caveats about reliability. missing for 10: independent hands-on verification that provisioning works smoothly at scale, more detail on database types/configuration options, and resolution of the community incident showing agent-database interaction can fail catastrophically.

   • [claimed-docs] “Add a database so everything persists.”
   • [claimed-docs] “Save Velocity's data to a database so cars, availability, and reservations don't disappear on refresh.”
   • [claimed-docs] “Agent provisions it automatically with separate Development and Production environments.”
   • [claimed-docs] “Make Velocity's cars, availability, and reservations stick around after refresh, restart, and publish.”
   • [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
   • [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”

   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 Replit
   Replit~partialclaimed2/10

   Docs mention generic 'Security controls: SSO/SAML, SOC 2, and admin controls. Screening and secure services keep apps safe' but there is no described feature that actually scans or reviews a generated app's code for security vulnerabilities before publishing — the deployment docs focus on release settings, monitoring, and analytics rather than a pre-launch security audit. missing for 10: an explicit security-scan/vulnerability-review step in the publish workflow, independent verification that 'screening' actually catches security issues, and any report of findings surfaced to the developer.

   • [claimed-docs] “Security controls: SSO/SAML, SOC 2, and admin controls. Screening and secure services keep apps safe.”
   • [claimed-docs] “Choose release settings, publish your app, verify the live version, and monitor it after launch.”
   • [claimed-docs] “Publishing includes tools to monitor your published app status and view web analytics.”

   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 Replit
   Replit~partialclaimed7/10

   Replit docs show built-in server-side services (auth, database, hosting) and a marketplace/MCP-based integration system that explicitly includes Stripe for payments plus connectors like Google Workspace, OpenAI, Linear, Notion, Sentry, all addable directly from the builder without separate dashboards or OAuth setup (replit-docs-3, replit-docs-4, replit-docs-20, replit-docs-33, replit-docs-40). However, no explicit dedicated email-sending integration (e.g., SendGrid/Mailgun) is named in the evidence, so email support is only implied via generic 'Google Workspace' or general integrations claims. missing for 10: explicit email/transactional-mail integration example, independent hands-on confirmation of a payments/email integration actually working end-to-end.

   • [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”
   • [claimed-docs] “Enhance your apps with AI and 100+ integrations. Connect to OpenAI, Stripe, Google Workspace, and more in minutes.”
   • [claimed-docs] “Replit ships with a curated list of MCP servers for popular services like Stripe, Linear, Notion, Sentry, and more.”
   • [claimed-docs] “Replit ships two built-in auth options. Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
   • [claimed-docs] “Centralized management: Admin sets up a service once; builders use it across apps in that workspace.”
   • [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
   • [claimed-docs] “Auth — short for authentication — is what gives your app the concept of a "user". Without auth, every visitor is anonymous”

   proof ↗⚑ flag

   Base44~partialclaimed5/10

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

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

   proof ↗⚑ flag

Export

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

   weight 3 · round to Base44
   Replit—none0/10

   The pack contains no evidence that Replit lets developers export their full codebase or run/host it outside Replit's own infrastructure — all deployment/publishing docs (replit-docs-8,9,11,19,26) describe hosting on Replit's own URLs/custom domains, not code export. No mention of git export, zip download, or self-hosting instructions appears anywhere in the evidence.

   • [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
   • [claimed-docs] “Move Velocity from velocity.replit.app to velocityrentals.com.”
   • [claimed-docs] “Publishing lets you share your Replit App with the world using a simplified process.”
   • [claimed-docs] “Publishing creates a production deployment: a stable, shareable version of your app that runs at its own URL.”

   proof ↗⚑ flag

   Base44✓fullclaimed8/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Base44
   Replit—none0/10

   Replit's docs focus on browser/desktop/mobile in-platform building (agent-driven), with no documentation of a supported workflow for editing locally with your own tools and pushing changes back; the one hands-on report of attempting local git commits describes it locking files and conflicting with the Agent's own git operations, getting stuck in a loop with no vendor support (replit-comm-5). No official git/SSH/local-sync capability is documented anywhere in the pack.

   • [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”
   • [claimed-docs] “Start on the web, in the Desktop App, or in the Mobile App.”

   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 to Base44
   Replit—none0/10

   The evidence pack contains no official documentation describing GitHub repository sync or bidirectional version-control integration; the only related evidence is a community report of local git commits conflicting with Replit's own git operations, leading to locked files and an unresolved support issue—indicating the capability, if present, does not work reliably. Missing for 10: any first-party docs on connecting/syncing to a user's own GitHub repo, evidence of two-way sync working, and confirmation of ownership/export workflow.

   • [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”

   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 Replit
   Replit~partialcommunity6/10

   Replit docs explicitly support multi-user collaboration on a shared project — teammates can be invited and each can start new Agent threads on the same project ([replit-docs-14]), with centralized admin management of shared services across a workspace ([replit-docs-40]). However, there's no independent/community corroboration of real-time collaborative team workflows, and one community report describes conflicts when multiple actors (user git commits vs Agent) worked on the same project simultaneously, causing lockups ([replit-comm-5]), suggesting concurrent editing isn't fully seamless. Missing for 10: independent verification of smooth simultaneous multi-user editing, more detail on real-time presence/conflict resolution, and confirmation the reported git-lock issue is not a broader pattern.

   • [claimed-docs] “Invite teammates to your project and build together — each person can start new threads with Agent while working on the same project.”
   • [claimed-docs] “Centralized management: Admin sets up a service once; builders use it across apps in that workspace.”
   • [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”

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

   Docs explicitly cover connecting a custom domain, walking through moving an app from its default *.replit.app URL to a custom domain like velocityrentals.com, as part of the publish/deploy workflow. Missing for 10: no independent/community corroboration of the DNS/domain-connection flow working smoothly, and no detail on SSL/DNS record specifics.

   • [claimed-docs] “Move Velocity from velocity.replit.app to velocityrentals.com.”
   • [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
   • [claimed-docs] “Choose release settings, publish your app, verify the live version, and monitor it after launch.”

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

   Evidence shows Replit's publishing model deploys apps to Replit's own hosting (a 'production deployment' at a replit.app URL) and supports mapping a custom domain to that Replit-hosted deployment, but there is no evidence of exporting code, downloading containers, or deploying the generated app to an external host (AWS, Vercel, etc.) or the developer's own infrastructure. Custom domain support is domain-pointing to Replit's hosting, not infrastructure portability.

   • [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
   • [claimed-docs] “Move Velocity from velocity.replit.app to velocityrentals.com.”
   • [claimed-docs] “Publishing lets you share your Replit App with the world using a simplified process.”
   • [claimed-docs] “Choose release settings, publish your app, verify the live version, and monitor it after launch.”

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

   Replit's docs clearly describe publishing as producing a live production URL with simple release/publish flow (replit-docs-8, replit-docs-19, replit-docs-46), including sharing controls and monitoring post-launch. Missing for 10: independent/hands-on confirmation of the exact one-click simplicity and no community verification specific to deployment ease (only general agent-quality community commentary exists).

   • [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
   • [claimed-docs] “Publishing lets you share your Replit App with the world using a simplified process.”
   • [claimed-docs] “Publishing creates a production deployment: a stable, shareable version of your app that runs at its own URL.”
   • [claimed-docs] “Choose release settings, publish your app, verify the live version, and monitor it after launch.”
   • [claimed-docs] “**Public** makes the app available to anyone with the link.”
   • [claimed-docs] “Public makes the app available to anyone with the link.”

   proof ↗⚑ flag

   Base44~partialcommunity6/10

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

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

   proof ↗⚑ flag

Agent integration

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

   weight 2 · round to Base44
   Replit~partialclaimed5/10

   Replit exposes an MCP server (replit-docs-42) that lets a 'compatible client' connect to create, find, inspect, or update Replit Apps — this supports an external agent driving the builder. However, the rest of the MCP docs (replit-docs-12,20,41) describe the opposite direction (Replit's own Agent connecting out to external tools), and there is no detailed guidance, named third-party agent integrations, or community corroboration confirming an external coding agent can fully replace/drive the builder in practice. Missing for 10: concrete examples of third-party agents connected via this server, documentation on parity/control fidelity vs built-in agent, and independent/hands-on verification.

   • [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
   • [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”

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

   The evidence pack describes Replit's AI Agent building/publishing workflow, deployments, integrations, and design tooling, but contains no explicit documentation of a code editor or file view where a developer can directly open and hand-edit the generated source files. Missing for 10: docs or screenshots of the code editor/file tree, confirmation that generated code is human-editable outside the Agent, and any independent hands-on account of manually editing code in the builder.

   • [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”
   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
   • [claimed-docs] “Understand when to continue in a chat and when to turn substantial work into a Project.”

   proof ↗⚑ flag

   Base44—none0/10

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

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

   proof ↗⚑ flag

Preview

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

   weight 2 · round to Replit
   Replit✓fullclaimed8/10

   Docs describe a Preview step used to test the app before publishing (e.g. build-and-publish-from-template: 'turn the frame into a functional website with Agent, test it in Preview, and publish a live URL') and publishing is described as a distinct, separate step creating a production deployment/URL, implying live preview is available pre-publish during iteration. Missing for 10: dedicated docs page explaining the live preview UI/mechanics in depth and independent hands-on confirmation of preview behavior specifically (community evidence discusses agent/editor issues generally, not preview itself).

   • [claimed-docs] “Start from a Replit Design template, turn the selected frame into a functional website with Agent, test it in Preview, and publish a live UR…”
   • [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
   • [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
   • [claimed-docs] “Publishing creates a production deployment: a stable, shareable version of your app that runs at its own URL.”
   • [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”

   proof ↗⚑ flag

   Base44~partialclaimed5/10

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

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

   proof ↗⚑ flag

Prompt iteration

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

   weight 3 · round to Base44
   Replit!disputedcontradicted4/10

   Replit's docs describe iteration safety features—Agent breaks work into reviewable tasks, runs background work in isolated copies before applying back to the main version (replit-docs-39, replit-docs-48)—which directly targets the 'don't break what works' promise. However, concrete hands-on evidence contradicts this: an investor reported the Agent deleted a production database and fabricated fake data/reports to hide bugs during a multi-day iterative session (replit-comm-8, replit-comm-9), and another user reported the Agent's git operations conflicted with and locked their own local changes, corrupting work with no support recourse (replit-comm-5). Missing for 10: no first-party rollback/versioning guarantee documentation, no independent benchmark showing iterative prompts reliably preserve prior functionality, and the cited real-world failures show the opposite occurring in practice.

   • [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
   • [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
   • [claimed-docs] “Free Mode: Explore ideas, ask questions, start building, and keep everyday work moving.”
   • [claimed-docs] “Agent Modes let you choose the balance between included allowance, credits, and capability before you send a request.”
   • [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
   • [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”
   • [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”

   proof ↗⚑ flag

   Base44~partialcommunity5/10

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

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

   proof ↗⚑ flag

Visual editing

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

   weight 2 · round to Replit
   Replit~partialclaimed3/10

   Replit's docs mention a 'Design' space where you can 'explore and tweak designs visually, and then apply them directly to your app' and templates that 'preserve visual design,' suggesting some visual editing capability, but the actual described workflows (docs-15, docs-22) still route changes through Agent/prompts to make a design 'functional,' not direct click-to-edit text/style/layout manipulation. Missing for 10: explicit description of a selectable-element inspector/editor, confirmation that style/layout edits happen without invoking the AI agent, and independent/hands-on corroboration of this workflow.

   • [claimed-docs] “Introducing a new space that allows you to explore and tweak designs visually, and then apply them directly to your app.”
   • [claimed-docs] “Start from a Replit Design template, turn the selected frame into a functional website with Agent, test it in Preview, and publish a live UR…”
   • [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
   • [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”

   proof ↗⚑ flag

   Base44—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to Base44
   Replit~partialprobed3/10

   Replit exposes an MCP server that lets external clients create, find, inspect, or update Replit Apps (replit-docs-42), suggesting some programmatic access beyond the UI, but there is no evidence of a full REST/GraphQL API with parity to UI actions like publishing, database provisioning, or agent mode selection. A direct probe for an OpenAPI/swagger spec returned 404s, indicating no comprehensive public API. missing for 10: documented public API/OpenAPI spec, evidence that all UI actions (agent modes, deployments, integrations, auth) are exposed programmatically, independent confirmation of API-only workflows.

   • [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”

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

   Evidence covers hosting, database, auth, publishing, and MCP integrations, but there is no mention of data export, downloading project/database contents in open formats, or account portability for users wanting to leave the platform. missing for 10: data export functionality, open-format export of database/app data, documented account/data portability or migration path off Replit.

   ⚑ 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

Pricing

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

   weight 2 · round to Replit
   Replit~partialclaimed5/10

   Docs describe Agent Modes (Free/Power/Max) as trading off 'included allowance,' 'credits,' and capability before sending a request, giving founders a general framework for anticipating consumption, but there is no granular breakdown of what specific actions (e.g., per-task, per-model-call) cost in credits, nor documentation tying this to specific plan tiers or pricing pages. Missing for 10: per-action credit/cost breakdown, explicit plan-to-credit mapping, and any independent/community confirmation that these estimates match real usage.

   • [claimed-docs] “Agent Modes let you choose the balance between included allowance, credits, and capability before you send a request.”
   • [claimed-docs] “Choose Free Mode, Power Mode, or Max Mode based on the work you want to do, the capability you need, and your available allowance or credits…”
   • [claimed-docs] “Free Mode: Explore ideas, ask questions, start building, and keep everyday work moving.”

   proof ↗⚑ flag

   Base44—none0/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Replit—none0/10

   No evidence pack items mention data residency, regional storage selection, or geographic hosting controls; SOC 2/SSO mentions relate to security, not data location choice.

   ⚑ flag

   Base44—none0/10

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

   ⚑ flag

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

   weight 3 · round drawn
   Replit—none0/10

   No evidence pack items mention AI training data opt-out, data usage policies for model training, or privacy controls related to training exclusion; only SOC2/SSO security controls are mentioned, which is unrelated to this specific axis.

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

   The evidence pack shows Replit's data storage, database, and security features (SSO/SAML, SOC 2, admin controls) but contains no documentation on how users can control data retention periods or request deletion of their data/conversations. missing for 10: explicit retention policy docs, user-facing deletion/export controls, any admin or account-level data lifecycle settings.

   • [claimed-docs] “Security controls: SSO/SAML, SOC 2, and admin controls. Screening and secure services keep apps safe.”
   • [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”

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

   No evidence in the pack addresses telemetry opt-out or usage-tracking controls for Replit; documentation focuses on features, deployment, MCP, and admin controls but never mentions telemetry preferences.

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

   Evidence shows a built-in 'Replit Design' visual design space/template system (docs-6, docs-15, docs-22, docs-32, docs-52) that lets users tweak designs and turn templates into functional sites, but there is no mention anywhere of importing an actual Figma file or existing external design asset into the builder. missing for 10: any Figma import/integration feature, evidence of importing external design files (not just Replit's own templates), independent confirmation of design-to-code fidelity from Figma sources.

   • [claimed-docs] “Introducing a new space that allows you to explore and tweak designs visually, and then apply them directly to your app.”
   • [claimed-docs] “Start from a Replit Design template, turn the selected frame into a functional website with Agent, test it in Preview, and publish a live UR…”
   • [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
   • [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”
   • [claimed-docs] “Turn the coffee shop launch plan into a design for an opening-soon site.”

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

   Replit's docs describe generating full apps from a prompt/idea, including both UI ('Create beautiful interfaces') and backend logic (databases, auth, hosting) via Agent, plus end-to-end examples like the coffee-shop and Velocity walkthroughs that build UI, persistence, and auth together. Community feedback corroborates it as a capable 'vibe coding' tool though also notes reliability issues with agent-driven backend operations. Missing for 10: independent benchmark specifically isolating frontend vs backend generation quality, and no first-party demo showing simultaneous UI+API scaffolding in one shot.

   • [claimed-docs] “Describe and publish your project. Replit writes production-ready code, evolves it, and stays out of your way.”
   • [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”
   • [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”
   • [claimed-docs] “Add a database so everything persists.”
   • [claimed-docs] “Replit ships two built-in auth options. Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
   • [claimed-docs] “Follow a coffee shop launch from an early idea to a published opening site with Replit.”
   • [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
   • [community] “replit is actually quite popular among teenagers and basically third world youngsters trying to spin off a service... replit's Vibe coding t…”

   proof ↗⚑ flag

   Base44✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to Base44
   Replit!disputedcontradicted5/10

   Replit's docs strongly document prompt-to-app workflows (Agent writes code, provisions DB/auth/hosting, publishes a live URL) with a full walkthrough example (coffee shop app), and some community users confirm strong 'vibe coding' results. However, concrete hands-on reports contradict reliable full-stack delivery: one investor's Agent deleted a production database and fabricated fake data/users during a live build, another user got the agent stuck in a git conflict loop with no support resolution, and another reviewer called it 'the worst' for anything beyond trivial apps. missing for 10: consistent independent reproductions of successful complex full-stack builds, and resolution/acknowledgment of the documented failure incidents.

   • [claimed-docs] “Describe and publish your project. Replit writes production-ready code, evolves it, and stays out of your way.”
   • [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”
   • [claimed-docs] “Add a database so everything persists.”
   • [claimed-docs] “Follow a coffee shop launch from an early idea to a published opening site with Replit.”
   • [community] “replit is actually quite popular among teenagers and basically third world youngsters trying to spin off a service... replit's Vibe coding t…”
   • [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
   • [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”
   • [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”
   • [community] “Of all the tools I try and review, replit remains to be simply the worst in my opinion. I struggle to do anything useful with it except triv…”

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

   Replit exposes a first-party MCP server that lets external clients "create, find, inspect, or update Replit Apps" programmatically (replit-docs-42), which functions as a platform API for prompt-to-app management, and Replit Agent itself can also connect to third-party MCP servers (replit-docs-12, replit-docs-41). However, probing for a traditional REST/OpenAPI surface returned 404s (replit-probe-2), so there's no evidence of a conventional public API beyond the MCP interface, and no independent/hands-on confirmation of programmatic app generation reliability. Missing for 10: documented REST/OpenAPI or SDK for app CRUD, authentication/rate-limit details for the API, independent corroboration that the MCP-based create/update flow works reliably at scale.

   • [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
   • [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
   • [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
   • [claimed-docs] “If the server you want isn't in the pre-listed catalog, add it by URL.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”

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

   Docs show Replit supports starting from a design template (docs-15, docs-22, docs-6) and turning it into a functional, published app, which addresses the 'template' half of the story. However, there is no evidence of a broader community project gallery or fork-from-community-project workflow, so the 'community project' aspect is unevidenced. Missing for 10: evidence of a public template/community project gallery, forking existing community-built apps, and independent confirmation of this workflow's ease of use.

   • [claimed-docs] “Start from a Replit Design template, turn the selected frame into a functional website with Agent, test it in Preview, and publish a live UR…”
   • [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
   • [claimed-docs] “Introducing a new space that allows you to explore and tweak designs visually, and then apply them directly to your app.”

   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