Vibe-Coding App Builders Arena
v0 vs Base44
Base44 wins · 11–14 (25 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to Base44v0none0/10No evidence that v0 publishes an llms.txt file or agent-oriented docs endpoint that other agents can be pointed at; the docs.md probe shows a markdown version of a page but not a standardized llms.txt/agent-discovery mechanism referenced anywhere in the pack.
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.”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round drawnv0 provides a programmatic API/SDK (v0-sdk) allowing chat/code-gen calls to be scripted, and GitHub integration runs CI checks and can auto-fix CI failures, suggesting some automation-friendly hooks; but there's no documented headless CLI mode or explicit CI-runner integration pattern (e.g., GitHub Actions example) for orchestrating v0 itself within a pipeline. missing for 10: a documented CLI/headless mode, an official CI/CD pipeline example (e.g., GitHub Actions), and independent confirmation of running v0 fully unattended in automation.
- [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
- [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
- [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
- [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
- [claimed-docs] “CI checks: See whether checks are running, passing, skipped, or failing.”
- [claimed-docs] “v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
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”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round drawnv0none0/10No evidence that v0 supports connecting to MCP servers or consuming their tools; docs mention integrations with databases, backend services, and AI providers but never reference MCP. missing for 10: any mention of MCP protocol/server support, documented tool-use via MCP, or third-party MCP connector.
Base44none0/10Evidence 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…”
ai-native userUse an official CLI
weight 2 · round to Base44v0none0/10Evidence shows a v0 API and a JavaScript/TypeScript SDK (v0-sdk) for programmatic access, but no official command-line interface tool is documented anywhere in the pack.
- [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
- [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
- [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
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”
ai-native userDrive the product through a documented public API
weight 3 · round to v0v0 documents a full public API (v0.app/docs/api/platform) offering programmatic access to code generation, chat, project management, and deployment, backed by an official SDK (vercel/v0-sdk) with concrete code examples (chats.create, streaming reads, API key/OIDC auth). This is corroborated by GitHub SDK evidence, not just marketing docs. Missing for 10: independent third-party developer reports/tutorials building production integrations on the API, and more detail on API rate limits/versioning.
- [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
- [claimed-docs] “Custom chat interfaces - Build your own UI for v0's AI-powered code generation”
- [claimed-docs] “Start with existing files (fast, no tokens)”
- [claimed-docs] “GitHub integration for repository imports”
- [claimed-docs] “Export capabilities for backup and migration”
- [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
- [github] “const result = readV0Stream(serverResult.toResponse())”
- [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
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/…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnv0none0/10Evidence shows only a single API key (V0_API_KEY) or OIDC-based server auth for the v0 SDK, with no mention of scoped, role-based, or least-privilege credential issuance for agents. Missing for 10: any documentation of granular permission scopes, per-agent tokens, or restricted API key capabilities.
- [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
- [claimed-docs] “Securely store sensitive information like API keys, tokens, and other credentials.”
Base44none0/10Evidence 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…”
ai-native userBuild against official SDKs
weight 2 · round to Base44v0 provides an official v0-sdk on GitHub with documented API usage (v0.chats.create, streaming, API key auth) plus a Platform API documented for programmatic access to chat, code generation, and project management. missing for 10: independent/hands-on developer corroboration of SDK reliability, multi-language SDK support, and deeper API reference coverage beyond quickstart snippets.
- [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
- [github] “const result = readV0Stream(serverResult.toResponse())”
- [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
- [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
- [claimed-docs] “Custom chat interfaces - Build your own UI for v0's AI-powered code generation”
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/…”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnv0none0/10No evidence of a webhooks subscription/event system in v0's docs or API pack; the API is described as request/response (create chats, streaming) with no mention of webhook endpoints or event subscriptions.
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to v0v0 offers some AI-driven analysis of a user's own data in the sense of reading logs, diagnosing build failures, and applying fixes, and it 'plans, creates tasks, and connects to databases as it builds,' which is a narrow form of AI-generated insight/suggestion from data within the product. However, there is no evidence of broader data-insight features (e.g., analytics, trend/insight surfacing from business or usage data) beyond code/log diagnostics, and no independent corroboration of this specific capability. Missing for 10: dedicated data-insight/analytics features, independent hands-on evidence of 'insights' beyond build-error fixing.
- [claimed-docs] “v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
- [claimed-docs] “Automatically fix errors in your code with intelligent diagnostics.”
- [claimed-docs] “select Fix with v0 or Fix Build. v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
- [claimed-docs] “v0 plans, creates tasks, and connects to databases as it builds.”
Base44none0/10Base44 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.”
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnv0none0/10v0's docs describe on-demand code generation, GitHub integration, deployments, and API access, but there is no evidence of scheduled/triggered automations or background agentic tasks that run autonomously without a user-initiated chat or API call (e.g., no cron jobs, webhooks, or persistent background workers are described). The closest features (auto-fix on CI failure, 'Fix with v0') are triggered by user action or CI events within a user-initiated flow, not autonomous background automation.
- [claimed-docs] “v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
- [claimed-docs] “select Fix with v0 or Fix Build. v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
- [claimed-docs] “open the branch menu and select Fix Conflicts, Fix CI, or Fix CI + Conflicts.”
- [claimed-docs] “v0 plans, creates tasks, and connects to databases as it builds.”
Base44none0/10Base44'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…”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnv0 is itself a built-in AI assistant that users delegate coding/build tasks to: docs show it plans, creates tasks, connects to databases, diagnoses and fixes build/CI errors autonomously (v0-docs-35, v0-docs-9/17/20, v0-docs-26), and community reports confirm a full 'dev-to-deploy' delegation experience with an MVP built end-to-end (v0-comm-1). Missing for 10: independent benchmarking of autonomous task delegation beyond anecdote, and no detail on multi-step task planning transparency.
- [claimed-docs] “v0 plans, creates tasks, and connects to databases as it builds.”
- [claimed-docs] “v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
- [claimed-docs] “Automatically fix errors in your code with intelligent diagnostics.”
- [claimed-docs] “select Fix with v0 or Fix Build. v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
- [claimed-docs] “open the branch menu and select Fix Conflicts, Fix CI, or Fix CI + Conflicts.”
- [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”
- [probe] “PROBE docs-md: HTTP 200 at https://v0.app/docs.md --- title: What is v0? description: v0 is an AI agent that helps anyone create real code a…”
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…”
ai-native userOperate the product with natural-language commands
weight 2 · round drawnv0's core interaction model is natural-language chat: docs and SDK show building apps from prompts like 'Build me a personal website', plus NL-driven fixes, migrations, and mockup-to-UI conversion, and community reports confirm fast prompt-to-deploy workflows in practice. Missing for 10: independent evidence on breadth/reliability of more complex multi-step NL commands and any documented failure modes for ambiguous instructions.
- [claimed-docs] “Create custom hooks and functionality”
- [claimed-docs] “Turn mockups into real, high-fidelity user interfaces that reflect user flows and constraints.”
- [claimed-docs] “v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
- [claimed-docs] “Quickly scaffold full-stack apps or components following best practices and modern standards.”
- [claimed-docs] “Migrate to the latest Next.js features”
- [claimed-docs] “Automatically fix errors in your code with intelligent diagnostics.”
- [claimed-docs] “v0 plans, creates tasks, and connects to databases as it builds.”
- [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
- [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”
- [probe] “PROBE docs-md: HTTP 200 at https://v0.app/docs.md --- title: What is v0? description: v0 is an AI agent that helps anyone create real code a…”
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…”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnv0none0/10v0 does publish API docs and an SDK with code snippets (v0-docs-4, v0-gh-1, v0-gh-2), but there is no evidence of an interactive API reference (e.g., a browsable console with runnable/try-it examples) — only static documentation pages and GitHub code samples. missing for 10: an interactive API console, in-browser runnable examples, evidence of a Swagger/OpenAPI-style explorer.
- [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
- [claimed-docs] “Custom chat interfaces - Build your own UI for v0's AI-powered code generation”
- [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
- [github] “const result = readV0Stream(serverResult.toResponse())”
- [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
Base44none0/10Base44 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/…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnv0none0/10v0 documents a REST-like API platform and SDK (v0-docs-4, v0-gh-1) but no evidence anywhere shows a downloadable OpenAPI/Swagger spec or other machine-readable API description; missing for 10: OpenAPI/JSON schema file, published spec endpoint, or SDK auto-generation from spec.
- [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
- [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
- [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
Base44none0/10A 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…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to v0v0 supports isolated branches and preview deployments that are separate from the production URL, letting changes be reviewed/tested before they affect production (v0-docs-38, v0-docs-39, v0-docs-29, v0-docs-11). However, there is no explicit sandbox/staging environment for data (e.g., a separate database or mock data layer) — integrations like Supabase/Neon/Upstash appear to connect directly to real backend services rather than a sandboxed copy. Missing for 10: explicit data-isolation/sandbox environment separate from production databases, first-party documentation of a test/staging data layer, and independent confirmation that production data is never touched during preview/testing.
- [claimed-docs] “Preview deployments are built from working branches.”
- [claimed-docs] “work on isolated branches, preview changes, run CI, and publish through pull requests”
- [claimed-docs] “When multiple chats share a Project, deploying from any of them updates the same production URL.”
- [claimed-docs] “One Project shares deployment, hosting, domains, and environment variables for the chats connected to it.”
- [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase, and AI mod…”
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…”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnv0none0/10While v0 documents an API platform (v0-docs-4, v0-docs-19) and an SDK (v0-gh-1..3), there is no evidence of API versioning scheme or a documented deprecation policy anywhere in the evidence pack.
Base44none0/10No 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.”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnv0none0/10The evidence shows v0's API can programmatically create individual chats/projects, but there is no documentation or example of performing bulk/batch operations across many items at once (e.g., batch generation, bulk edits, mass deployment). Nothing in the docs or SDK references batching, looping over collections, or multi-item transactions.
Base44none0/10The 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.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to Base44v0none0/10The evidence describes v0's code generation, GitHub integration, deployment, and API capabilities, but nothing shows a rules/trigger engine where users define 'on event X, do action Y' automations. Missing for 10: any documented rule engine, event triggers, or workflow automation configuration beyond routine CI/deployment fixes.
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…”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnv0none0/10No evidence anywhere in the pack of scheduling, cron-like triggers, or recurring workflow automation in v0; the product is oriented around chat-driven code generation, deployment, and API-triggered chats, not scheduled/recurring jobs.
ai-native userVersion, review, and roll back my automations
weight 1 · round to v0v0's GitHub integration gives git-based version control (isolated branches, commits, PRs, CI checks) which supports versioning and review of generated projects, and branch/PR mechanics implicitly allow reverting to prior states. However, there is no explicit 'rollback' feature or chat/version history UI documented specifically for automations, and 'automations' as a distinct concept (vs. generated code) isn't addressed. Missing for 10: dedicated rollback/undo capability, explicit versioning of automations (not just code), and independent evidence of review/rollback workflows in practice.
- [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
- [claimed-docs] “The Duplicate Branch dialog creates a new chat and branch containing the current branch's commits.”
- [claimed-docs] “open the branch menu and select Fix Conflicts, Fix CI, or Fix CI + Conflicts.”
- [claimed-docs] “CI checks: See whether checks are running, passing, skipped, or failing.”
- [claimed-docs] “work on isolated branches, preview changes, run CI, and publish through pull requests”
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…”
Backend data — stories about backend data in this arenaBackend data
Stories about backend data in this arena
Ai features
ai-native userAdd AI features like LLM calls and agents to my generated app without managing provider keys myself
weight 2 · round to Base44v0's project integrations explicitly include 'AI model providers' alongside databases like Upstash and Neon, and v0 can securely store API keys/tokens for connected services, suggesting some ability to wire in LLM/agent providers without manual key wrangling in code — but v0-docs-44 implies the user still supplies and stores the provider key themselves rather than v0 fully abstracting key management, and there's no dedicated doc on built-in LLM/agent calling with zero-config provider access. missing for 10: explicit documentation of a first-party managed LLM/agent provider (no user-supplied key required), hands-on confirmation that AI features work without configuring provider credentials.
- [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase, and AI mod…”
- [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase”
- [claimed-docs] “Securely store sensitive information like API keys, tokens, and other credentials.”
- [claimed-docs] “v0 plans, creates tasks, and connects to databases as it builds.”
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…”
Auth
developerAdd user sign-up and login (email, social providers) scaffolded by the builder
weight 3 · round to Base44v0 integrates with backend services like Supabase (which typically provide auth) and one community report describes building an app 'with auth, roles' using v0, suggesting the builder can scaffold authentication flows. However, there is no first-party documentation specifically describing sign-up/login scaffolding, social provider integration, or auth templates. Missing for 10: explicit docs on email/social auth scaffolding, named auth provider integrations (e.g., Auth.js, Clerk), and independent verification of social login flows.
- [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”
- [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase, and AI mod…”
- [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase”
- [claimed-docs] “Connect to backend to build rich, data driven applications.”
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.”
Database
developerGet a database provisioned and wired into my app without leaving the builder
weight 3 · round to Base44v0's Project docs explicitly describe connecting databases (Neon Postgres, Upstash Redis) and backend services (Supabase) directly within a Project, with v0 stated to 'plan, create tasks, and connect to databases as it builds,' and secrets/env vars are managed within the same Project without leaving the tool. This matches the story of provisioning and wiring a database inline in the builder. Missing for 10: no independent/hands-on report confirming the actual provisioning flow works smoothly, and no detail on whether v0 auto-creates the database instance or just connects an existing one.
- [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase, and AI mod…”
- [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase”
- [claimed-docs] “Connect your project to third-party services to give your Project access to external data and functionality.”
- [claimed-docs] “Connect to backend to build rich, data driven applications.”
- [claimed-docs] “v0 plans, creates tasks, and connects to databases as it builds.”
- [claimed-docs] “Securely store sensitive information like API keys, tokens, and other credentials.”
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…”
Security
developerHave the platform review my generated app for security issues before it goes live
weight 2 · round drawnv0none0/10No evidence pack item mentions any security review, vulnerability scanning, or pre-launch security audit feature; deployment features focus on CI/build fixes and hosting, not security review. Missing for 10: any documented security scanning/review capability, evidence of vulnerability detection, or pre-deploy security checklist.
Base44none0/10No 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”
Server logic
developerAdd server-side functions and third-party integrations like payments and email from the builder
weight 2 · round drawnv0 docs show clear support for connecting projects to backend services and third-party integrations (Supabase, Upstash Redis, Neon Postgres, AI providers) and securely storing API keys/credentials, plus a general 'third-party services for external data and functionality' hook, which covers server-side function-like backend connections. However, no evidence specifically confirms out-of-the-box payments (e.g., Stripe) or email (e.g., Resend/SendGrid) integrations, nor detailed docs on writing custom server-side functions beyond generic 'connect to backend' language. Missing for 10: explicit payment-provider integration examples, explicit email-service integration examples, and documentation of custom server-side function authoring within the builder.
- [claimed-docs] “Connect to backend to build rich, data driven applications.”
- [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase, and AI mod…”
- [claimed-docs] “Connect your project to third-party services to give your Project access to external data and functionality.”
- [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase”
- [claimed-docs] “Securely store sensitive information like API keys, tokens, and other credentials.”
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.”
Code ownership — stories about code ownership in this arenaCode ownership
Stories about code ownership in this arena
Export
developerExport the full source code and run or host the app outside the platform
weight 3 · round to Base44v0 lets users connect a project to GitHub, push code directly to a repo, import existing GitHub code, and the API platform docs explicitly list 'Export capabilities for backup and migration,' meaning the generated code is not locked into the platform and can be run/hosted elsewhere. This is first-party documented but lacks independent hands-on verification of exporting and self-hosting outside Vercel's infrastructure. missing for 10: independent/community confirmation of exporting and successfully self-hosting a v0 app outside Vercel, and details on the exact export format/process.
- [claimed-docs] “Connect to GitHub and push code directly to your repository.”
- [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
- [claimed-docs] “To start from code already on GitHub, use Import from GitHub.”
- [claimed-docs] “Export capabilities for backup and migration”
- [claimed-docs] “GitHub integration for repository imports”
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.”
developerWork on the app locally with my own editor and tooling and push changes back to the platform
weight 2 · round to Base44v0's GitHub integration lets developers connect a project to a repo, work on isolated branches, push code directly, and open PRs — enabling a workflow where code can be edited locally and pushed back to sync with the platform. Missing for 10: explicit mention of a local CLI/dev-server workflow and independent confirmation that locally-pushed commits are correctly re-synced into the v0 chat/build pipeline.
- [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
- [claimed-docs] “To start from code already on GitHub, use Import from GitHub.”
- [claimed-docs] “To start from code already on GitHub, use Import from GitHub. Importing creates a chat at the selected base branch”
- [claimed-docs] “Connect to GitHub and push code directly to your repository.”
- [claimed-docs] “work on isolated branches, preview changes, run CI, and publish through pull requests”
- [claimed-docs] “CI checks: See whether checks are running, passing, skipped, or failing.”
- [claimed-docs] “open the branch menu and select Fix Conflicts, Fix CI, or Fix CI + Conflicts.”
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.”
Git sync
developerSync my project to my own GitHub repository and keep changes flowing both ways
weight 3 · round drawnv0's docs describe robust two-way GitHub sync: connecting a project to a repo, working on isolated branches, previewing, running CI, publishing via PRs, importing existing GitHub code, and resolving conflicts/CI failures directly from v0 (v0-docs-2,3,26,27,30,39). This covers both directions of the sync story (v0→GitHub via branches/PRs, GitHub→v0 via import) with first-party specificity. Missing for 10: independent/hands-on community verification that the bidirectional sync works reliably in practice beyond vendor docs.
- [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
- [claimed-docs] “To start from code already on GitHub, use Import from GitHub.”
- [claimed-docs] “open the branch menu and select Fix Conflicts, Fix CI, or Fix CI + Conflicts.”
- [claimed-docs] “To start from code already on GitHub, use Import from GitHub. Importing creates a chat at the selected base branch”
- [claimed-docs] “CI checks: See whether checks are running, passing, skipped, or failing.”
- [claimed-docs] “work on isolated branches, preview changes, run CI, and publish through pull requests”
- [claimed-docs] “The Duplicate Branch dialog creates a new chat and branch containing the current branch's commits.”
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…”
Collaboration teams — stories about collaboration teams in this arenaCollaboration teams
Stories about collaboration teams in this arena
Collaboration
founderMy team can work on the same project together in a shared workspace
weight 2 · round to v0v0 supports Projects with shared deployments, environment variables, and multiple chats connected to one project, plus a Shared Credit Pool for team plans, suggesting basic team collaboration on a shared project. However there's no evidence of real-time co-editing, granular roles/permissions, comments, or explicit multi-user workspace management beyond credit pooling. missing for 10: evidence of real-time multi-user collaboration, role-based permissions, in-app commenting/review, and explicit documentation of team workspace setup beyond credit sharing.
- [claimed-docs] “One Project shares deployment, hosting, domains, and environment variables for the chats connected to it.”
- [claimed-docs] “You can connect multiple chats to the same Project. This is useful when working different parts of one Project”
- [claimed-docs] “When multiple chats share a Project, deploying from any of them updates the same production URL.”
- [claimed-docs] “Shared Credit Pool credits are shared among all team members”
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”
Deploy domains — stories about deploy domains in this arenaDeploy domains
Stories about deploy domains in this arena
Domains
founderConnect a custom domain to my published app
weight 2 · round to Base44Docs mention that Projects share 'deployment, hosting, domains, and environment variables' implying custom domain support exists at the project level, but there is no explicit guidance, UI flow, or confirmation of connecting a custom domain to a published app. missing for 10: dedicated custom-domain setup docs, DNS/verification steps, hands-on confirmation that a founder can attach their own domain.
- [claimed-docs] “One Project shares deployment, hosting, domains, and environment variables for the chats connected to it.”
- [claimed-docs] “Deploy with one click to secure, scalable infrastructure powered by Vercel.”
- [claimed-docs] “Go live instantly with one-click deployment to production in seconds.”
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.”
Publish
developerDeploy the generated app to an external host or my own infrastructure
weight 1 · round to v0v0 emphasizes one-click deploy to Vercel's own infrastructure and GitHub push/export code, which allows deploying elsewhere via exported code, but there is no first-party support or documentation for direct deployment to non-Vercel hosts (e.g., AWS, Netlify, self-hosted servers) beyond pushing code to a repo. missing for 10: explicit support/instructions for deploying to external hosts or self-managed infrastructure beyond GitHub push, independent confirmation that exported/GitHub code deploys successfully outside Vercel.
- [claimed-docs] “Deploy with one click to secure, scalable infrastructure powered by Vercel.”
- [claimed-docs] “Connect to GitHub and push code directly to your repository.”
- [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
- [claimed-docs] “Export capabilities for backup and migration”
- [claimed-docs] “Go live instantly with one-click deployment to production in seconds.”
Base44none0/10Base44'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.”
founderPublish my app to a live URL in one step
weight 3 · round to v0v0 docs explicitly describe one-click deploy to production via Vercel infrastructure, with project-level shared deployment URLs and instant go-live claims, corroborated by a community account of a full dev-to-deploy cycle to real users. Missing for 10: independent third-party verification of the exact one-step publish flow and no hands-on confirmation of custom domain setup ease.
- [claimed-docs] “Deploy with one click to secure, scalable infrastructure powered by Vercel.”
- [claimed-docs] “Go live instantly with one-click deployment to production in seconds.”
- [claimed-docs] “When multiple chats share a Project, deploying from any of them updates the same production URL.”
- [claimed-docs] “One Project shares deployment, hosting, domains, and environment variables for the chats connected to it.”
- [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”
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…”
Iteration editing — stories about iteration editing in this arenaIteration editing
Stories about iteration editing in this arena
Agent integration
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 Base44The v0 API/SDK exposes programmatic access to v0's generation capabilities (e.g. v0.chats.create()) and GitHub integration for code sync, which could let an external tool or script drive v0 programmatically, but there is no evidence of a documented way to plug a third-party coding agent (e.g. Claude Code, Cursor) into a v0 project to replace or run alongside the built-in agent inside the builder UI. Missing for 10: explicit 'bring your own agent' support, agent-swap or multi-agent orchestration inside a v0 project, and any first-party or community confirmation of this working end-to-end.
- [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
- [claimed-docs] “Custom chat interfaces - Build your own UI for v0's AI-powered code generation”
- [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
- [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
- [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
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.”
Code editing
developerOpen and edit the generated source code directly inside the builder
weight 2 · round drawnv0none0/10The evidence pack describes visual controls, live preview, GitHub push/pull, and export capabilities, but never explicitly confirms an in-builder code editor where developers can directly view and edit the generated source files. Missing for 10: explicit documentation or screenshot of a code/editor pane inside the v0 builder, hands-on confirmation of direct code editing (not just prompting or visual controls).
- [claimed-docs] “Fine-tune every detail with visual controls and live preview.”
- [claimed-docs] “Connect to GitHub and push code directly to your repository.”
- [claimed-docs] “Export capabilities for backup and migration”
Base44none0/10Evidence 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…”
Preview
founderInteract with a live preview of my app while building, before publishing
weight 2 · round to v0v0's docs explicitly describe live preview with visual controls while iterating ('Fine-tune every detail with visual controls and live preview') and preview deployments built from working branches before publishing, matching the founder's need to see a live app preview pre-publish. Community evidence corroborates rapid build-to-preview workflows, though it's not preview-specific. Missing for 10: independent hands-on account specifically describing the live-preview interaction (vs generation speed) and detail on preview fidelity/limitations.
- [claimed-docs] “Fine-tune every detail with visual controls and live preview.”
- [claimed-docs] “Preview deployments are built from working branches.”
- [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”
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.”
Prompt iteration
founderRefine my app through follow-up prompts without breaking what already works
weight 3 · round drawnv0 supports iterative refinement (chat-based prompts, automatic error fixing, isolated branches, project structure preserving deployment/config) and community reports confirm fast, incremental build-to-deploy cycles, but no evidence explicitly addresses preserving existing functionality across follow-up prompts or preventing regressions. missing for 10: explicit regression-safety guarantees, hands-on evidence that follow-up prompts don't break prior working features, independent testing of iterative stability.
- [claimed-docs] “Automatically fix errors in your code with intelligent diagnostics.”
- [claimed-docs] “v0 reads the relevant logs, diagnoses the failure, and applies a fix.”
- [claimed-docs] “You can connect multiple chats to the same Project. This is useful when working different parts of one Project”
- [claimed-docs] “One Project shares deployment, hosting, domains, and environment variables for the chats connected to it.”
- [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”
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…”
Visual editing
designerSelect an element and edit its text, style, or layout directly without a prompt round-trip
weight 2 · round to v0v0.app claims 'Fine-tune every detail with visual controls and live preview' (v0-docs-7), suggesting some direct-manipulation UI, but nearly all other documentation describes chat/prompt-driven generation and iteration cycles rather than click-to-select element editing. Missing for 10: explicit documentation or demo of selecting an element on canvas and editing its text/style/layout inline, independent corroboration that this bypasses the prompt loop, and detail on what 'visual controls' actually cover.
- [claimed-docs] “Fine-tune every detail with visual controls and live preview.”
Base44none0/10Evidence 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.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round drawnv0 explicitly claims the API gives 'programmatic access to all of v0's capabilities' including chat, project management, and deployment (v0-docs-4), backed by SDK examples (v0-gh-1/2/3) and API docs on GitHub import and export (v0-docs-37, v0-docs-43). However, many UI-specific workflows (Figma/screenshot cloning, CI/conflict-fix buttons, command palette search, iOS app, visual style controls) are only documented as UI features with no API equivalent shown, and no independent test confirms true 1:1 parity. missing for 10: API-exposed equivalents for design import (Figma/screenshots), GitHub PR/CI-fix actions, and independent verification that API surface matches UI feature set.
- [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
- [claimed-docs] “GitHub integration for repository imports”
- [claimed-docs] “Export capabilities for backup and migration”
- [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
- [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
- [claimed-docs] “Custom chat interfaces - Build your own UI for v0's AI-powered code generation”
- [claimed-docs] “Clone pages with screenshots or Figma files”
- [claimed-docs] “open the branch menu and select Fix Conflicts, Fix CI, or Fix CI + Conflicts.”
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.”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnv0 lets users push/export generated code to GitHub in a standard, open format (docs-2, docs-31, docs-39), and the API docs mention generic 'Export capabilities for backup and migration' (docs-43), supporting a degree of data portability. However there's no concrete evidence of exporting full account data (chat history, project settings, credentials) in open formats, and no independent confirmation the export path is complete or lock-in-free. Missing for 10: evidence of exporting non-code data (chats, project metadata, integrations config), a documented full-account export/download feature, and independent verification that migrated projects run outside v0/Vercel without further dependency.
- [claimed-docs] “Connect a v0 project to GitHub to keep its code in a repository, work on isolated branches, preview changes, run CI, and publish through pul…”
- [claimed-docs] “Connect to GitHub and push code directly to your repository.”
- [claimed-docs] “work on isolated branches, preview changes, run CI, and publish through pull requests”
- [claimed-docs] “Export capabilities for backup and migration”
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.”
ai-native userRead the product's source under an open license
weight 2 · round drawnv0none0/10v0 is a closed, proprietary hosted product (with an SDK client library on GitHub, not the core product source); there is no evidence the v0 application/model itself is released under an open license. missing for 10: any statement of an open-source license for v0's core product/source code.
Base44none0/10Base44 is a closed, hosted AI app-builder platform; no evidence anywhere in the pack indicates its own source code (platform/product source) is published under an open license. Evidence only covers exporting/ejecting user-built apps, CLI, SDK, and GitHub sync for user apps—not the openness of Base44's own codebase.
- [claimed-docs] “This command downloads the frontend code and backend resources from a selected app and creates a new project with its own app ID.”
- [claimed-docs] “Clone an existing Base44 app into a separate local project. This command downloads the frontend code and backend resources from a selected a…”
- [claimed-docs] “Use the SDK to build your own frontend or backend that uses Base44 as a backend service.”
- [claimed-docs] “The Base44 CLI is a command-line tool for building and managing Base44 apps from your terminal. Create new backend projects, sync data model…”
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits
Free-tier ceilings, usage caps, and rate limits before you have to pay
Pricing
founderUnderstand what credits or tokens each action consumes and what my plan includes
weight 2 · round to v0v0disputedcontradicted5/10Docs describe a credits/plan system (Premium $20/month, shared credit pools, ability to buy more credits) and even flag one action as token-free (v0-docs-10, v0-docs-23, v0-docs-42, v0-docs-25), but no documentation breaks down per-action credit costs. A hands-on community report contradicts the idea that users can predict consumption, describing unexpectedly high usage-based costs (~$50 in a weekend, '>$20/day') versus flat subscription alternatives (v0-comm-3), showing the credit model is opaque in practice. missing for 10: a clear per-action credit/token cost table, first-party UI showing real-time credit usage, and corroborating community confirmation that costs are predictable.
- [claimed-docs] “You can buy more credits any time (Premium, Plus, and Business plans).”
- [claimed-docs] “Premium: $20/month. For higher limits and power users.”
- [claimed-docs] “Shared Credit Pool credits are shared among all team members”
- [claimed-docs] “Start with existing files (fast, no tokens)”
- [community] “Cost complaint: 'V0 is pay by usage... we talking > +$20/day vs $XX/month' for a subscription-based alternative like Copilot; spent about $5…”
Base44none0/10No 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…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnv0none0/10No evidence in the pack mentions data residency, regional storage options, or any data-location controls for v0; the docs focus on code generation, deployment, GitHub integration, and pricing, none of which address where data is stored.
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnv0none0/10No evidence in the pack addresses data-training opt-out, privacy controls, or any statement about whether user data/code is used to train AI models; nothing mentions a privacy policy toggle or enterprise no-training guarantee.
ai-native userControl data retention and deletion
weight 2 · round drawnv0none0/10No evidence in the pack addresses data retention policies, deletion controls, or privacy settings for user data/chats/projects in v0; only export capabilities for backup/migration are mentioned, which is unrelated to retention/deletion control. Missing for 10: documented data retention policy, user-facing deletion/export-of-data controls, opt-out of training data usage, any privacy/compliance documentation.
Base44none0/10No 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'.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnv0none0/10No evidence pack item mentions telemetry, analytics opt-out, or usage tracking controls for v0; nothing addresses privacy settings of this kind.
Prompt to app — stories about prompt to app in this arenaPrompt to app
Stories about prompt to app in this arena
Design import
designerImport a Figma file or existing design and have the builder implement it
weight 2 · round to Base44Docs explicitly claim ability to 'Clone pages with screenshots or Figma files' and 'Create high-fidelity UIs from your wireframes or mockups,' directly supporting the story, but this is first-party doc text only with no workflow detail, screenshots, or independent hands-on confirmation of Figma import fidelity. Missing for 10: detailed Figma import workflow documentation, independent/community verification that Figma import works as claimed, and coverage of fidelity/limitations when translating Figma designs to code.
- [claimed-docs] “Clone pages with screenshots or Figma files”
- [claimed-docs] “Create high-fidelity UIs from your wireframes or mockups.”
- [claimed-docs] “Turn mockups into real, high-fidelity user interfaces that reflect user flows and constraints.”
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.”
Generation
developerGenerate both frontend UI and backend logic from a single prompt
weight 3 · round drawnv0 docs and community evidence show single-prompt generation of both frontend UI and connected backend logic (databases, auth, Supabase/Neon/Upstash integrations) plus full-stack scaffolding and deployment, corroborated by a hands-on HN report of building a full app with auth/roles/export from prompt to deployed MVP. missing for 10: no controlled benchmark of backend logic correctness/robustness, and no independent review specifically validating backend code quality (community feedback focuses mostly on UI generation and cost).
- [claimed-docs] “Quickly scaffold full-stack apps or components following best practices and modern standards.”
- [claimed-docs] “Connect to backend to build rich, data driven applications.”
- [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase, and AI mod…”
- [claimed-docs] “v0 plans, creates tasks, and connects to databases as it builds.”
- [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase”
- [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”
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…”
founderDescribe an app in natural language and get a working full-stack application
weight 3 · round to Base44Docs and API show natural-language-to-app generation, full-stack scaffolding, backend/database integrations, and one-click deployment (v0-docs-15, v0-docs-24, v0-docs-28, v0-docs-32, v0-gh-1). A first-hand community report confirms a working MVP built and deployed quickly from a prompt (v0-comm-1). Missing for 10: broader independent benchmarking on complex, non-trivial apps and evidence addressing the noted design-sameness limitation (v0-comm-4).
- [claimed-docs] “Quickly scaffold full-stack apps or components following best practices and modern standards.”
- [claimed-docs] “Connect to backend to build rich, data driven applications.”
- [claimed-docs] “Available integrations include databases like Upstash for Redis and Neon for Serverless Postgres, backend services like Supabase, and AI mod…”
- [claimed-docs] “Go live instantly with one-click deployment to production in seconds.”
- [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
- [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”
- [probe] “PROBE docs-md: HTTP 200 at https://v0.app/docs.md --- title: What is v0? description: v0 is an AI agent that helps anyone create real code a…”
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…”
Programmatic generation
ai-native userGenerate and manage apps programmatically through a platform API
weight 3 · round to v0v0 documents a platform API that gives programmatic access to chat/code generation, project management, and deployment (v0-docs-4), and the official v0-sdk on GitHub shows concrete code for creating chats and streaming results with API-key auth (v0-gh-1, v0-gh-2, v0-gh-3), directly matching the 'generate and manage apps programmatically' story. Missing for 10: independent/hands-on corroboration of the API in production use and more detail on full app lifecycle management (list/delete/update) via the API beyond chat creation.
- [claimed-docs] “The v0 API gives you programmatic access to all of v0's capabilities, letting you integrate v0's AI-powered code generation, chat interface,…”
- [claimed-docs] “Custom chat interfaces - Build your own UI for v0's AI-powered code generation”
- [claimed-docs] “Start with existing files (fast, no tokens)”
- [claimed-docs] “GitHub integration for repository imports”
- [claimed-docs] “Export capabilities for backup and migration”
- [github] “const response = await v0.chats.create({ message: 'Build me a personal website', })”
- [github] “const result = readV0Stream(serverResult.toResponse())”
- [github] “Set V0_API_KEY, or deploy server-side code on Vercel with OIDC enabled, then use the default client.”
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/…”
Templates ecosystem — stories about templates ecosystem in this arenaTemplates ecosystem
Stories about templates ecosystem in this arena
Templates
founderStart from a template or community project instead of a blank prompt
weight 2 · round to Base44v0 supports starting from existing code via 'Import from GitHub' and 'Start with existing files (no tokens)', which lets founders begin from a pre-existing project rather than a blank prompt, and community testimony confirms it solves the 'blank canvas problem'. However there is no evidence of a curated template gallery or a community-project showcase/marketplace to browse and remix, which is the core of the story. Missing for 10: a dedicated template/starter gallery, community project discovery or remix feature, and evidence of founders actually starting from such templates.
- [claimed-docs] “To start from code already on GitHub, use Import from GitHub.”
- [claimed-docs] “To start from code already on GitHub, use Import from GitHub. Importing creates a chat at the selected base branch”
- [claimed-docs] “Start with existing files (fast, no tokens)”
- [community] “Built a feature-rich internal app (time tracker w/ auth, roles, export) and had a working MVP in users' hands by Monday. 'The speed was incr…”
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…”
Not comparable on these axes
ai-native userConnect an agent via an official MCP server
weight 3 · not comparablev0n/av0 is itself an AI coding agent/assistant product; per category rules, serving as an MCP server is a different product role (client vs server) and no evidence shows v0 exposing an official MCP server endpoint. The GitHub/API integrations shown are v0 acting as an agent connecting to other services, not v0 being connected to as an MCP server.
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…”
ai-native userSelf-host the core product
weight 3 · not comparablev0n/av0 is a hosted SaaS AI code-generation product; there is no evidence of any self-hosted/on-prem deployment option, and self-hosting the core product is not a fair axis for this cloud-only offering type (analogous to asking a SaaS platform to be self-hostable when it ships no such artifact). No evidence pack items even mention self-hosting the core service (only exporting generated app code or connecting to external backends), so this is a category mismatch rather than a failed capability.
Base44none0/10Evidence shows only that you can 'eject' an individual app's frontend/backend code into a new Base44-hosted project (still using Base44's platform with its own app ID), not that the Base44 platform/core service itself can be run on your own infrastructure. No mention of an open-source core, downloadable server, or self-hosting instructions exists in the pack.
- [claimed-docs] “This command downloads the frontend code and backend resources from a selected app and creates a new project with its own app ID.”
- [claimed-docs] “Clone an existing Base44 app into a separate local project. This command downloads the frontend code and backend resources from a selected a…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.base44.com/llms.txt # Base44 Documentation > Base44 is an AI-powered app builder. Describe your id…”