Vibe-Coding App Builders Arena
v0 vs Replit
v0 wins · 16–14 (19 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 Replitv0none0/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 Replit docs serve a working llms.txt at docs.replit.com/llms.txt (HTTP 200) listing structured doc sections, directly enabling an agent to be pointed at agent-oriented docs; this is corroborated by extensive first-party docs pages formatted for agent consumption. Missing for 10: independent third-party confirmation that agents actually consume/use this llms.txt effectively, and no evidence of an OpenAPI spec or other machine-readable API docs (all probed paths 404).
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.replit.com/llms.txt # Replit - [Features (218 pages)](https://docs.replit.com/_llms/en/features.md…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
- [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to v0v0 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.”
Replitnone0/10Evidence covers Replit's Agent modes, MCP connectors, and scheduled 'routines' but nothing about a CLI, API, or headless mode for running Replit in CI/automation pipelines outside its own UI. missing for 10: CLI/API for headless execution, CI/CD pipeline integration, documented automation outside Replit's own scheduler.
- [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”
- [claimed-docs] “Agent Modes let you choose the balance between included allowance, credits, and capability before you send a request.”
- [claimed-docs] “Choose Free Mode, Power Mode, or Max Mode based on the work you want to do, the capability you need, and your available allowance or credits…”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round to Replitv0none0/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.
Replit's docs explicitly describe connecting Agent to external tools via MCP, with a curated catalog (Stripe, Linear, Notion, Sentry) plus the ability to add custom servers by URL, giving Agent access to their tools. missing for 10: independent/hands-on community corroboration of MCP usage in practice, and detail on tool invocation reliability beyond first-party docs.
- [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
- [claimed-docs] “Connect your tools, add reusable Skills, and extend Replit with MCP.”
- [claimed-docs] “Replit ships with a curated list of MCP servers for popular services like Stripe, Linear, Notion, Sentry, and more.”
- [claimed-docs] “If the server you want isn't in the pre-listed catalog, add it by URL.”
- [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
ai-native userUse an official CLI
weight 2 · round drawnv0none0/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.”
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.”
Replit documents an MCP server that lets external clients create, find, inspect, or update Replit Apps (replit-docs-42), which functions as a documented programmatic interface for AI-native control, but there is no evidence of a traditional REST/OpenAPI-documented public API — probes for openapi.json/swagger.json all returned 404 (replit-probe-2). missing for 10: a formal REST/OpenAPI-documented API, independent confirmation of MCP server reliability/completeness, broader API surface beyond MCP-driven app management.
- [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
- [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
- [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
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.”
Replitnone0/10Evidence covers built-in auth for end-user apps and centralized connector management, but there is no documentation of issuing scoped or least-privilege API credentials specifically to control an agent's own access level. Missing for 10: any mention of API key/credential scoping, permission levels, or least-privilege token issuance for the agent itself.
ai-native userBuild against official SDKs
weight 2 · round to v0v0 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”
Replitnone0/10The evidence pack describes MCP-based integrations, connectors, and Agent Skills, but never mentions an official SDK (e.g., a Python/JS client library) for programmatically building against Replit, and a direct probe for an OpenAPI/API spec returned 404s on all candidate paths, suggesting no public SDK/API surface is documented.
- [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
- [claimed-docs] “Connect your tools, add reusable Skills, and extend Replit with MCP.”
- [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
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 drawnv0 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.”
Replit's Agent can pull in context from connected integrations (e.g. "Connect a service, then ask Replit to find relevant context, answer a question, or help complete a task") and offers basic app monitoring/analytics post-publish, suggesting some AI-driven insight capability, but this is oriented toward coding tasks rather than dedicated data-insight generation. missing for 10: explicit data-analysis/insight-generation feature (e.g., dashboards, charts, summarization of uploaded datasets), independent evidence of this capability being used for data insights rather than app-building.
- [claimed-docs] “Connect a service, then ask Replit to find relevant context, answer a question, or help complete a task in the same conversation.”
- [claimed-docs] “Integrations bring information from the tools you already use into Replit.”
- [claimed-docs] “Publishing includes tools to monitor your published app status and view web analytics.”
- [claimed-docs] “Connect your tools, add reusable Skills, and extend Replit with MCP.”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to Replitv0none0/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.”
Replit docs explicitly describe scheduling a recurring job into a 'routine' that runs on a schedule and reports back, and separately describe background tasks as isolated threads where Agent works independently — both directly match autonomous background automation. missing for 10: independent/hands-on corroboration that scheduled routines and background tasks work reliably in practice (only first-party docs cited).
- [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”
- [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
- [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
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…”
Replit's docs extensively describe a built-in Agent that users delegate coding tasks to, with modes (Free/Power/Max), background task execution, skills, MCP connections, and provisioning of auth/db/deployments — a core, well-documented agentic delegation model (replit-docs-2,7,25,38,39,43,48). Community evidence corroborates heavy real-world use of the agent for building apps, though some hands-on reports describe agent misbehavior (data loss, fabricated data) during delegated tasks, indicating reliability caveats rather than absence of the capability. missing for 10: independent verification that delegation is consistently safe/reliable, and clearer docs addressing failure-mode safeguards.
- [claimed-docs] “Describe and publish your project. Replit writes production-ready code, evolves it, and stays out of your way.”
- [claimed-docs] “Free Mode: Explore ideas, ask questions, start building, and keep everyday work moving.”
- [claimed-docs] “Agent Modes let you choose the balance between included allowance, credits, and capability before you send a request.”
- [claimed-docs] “Choose Free Mode, Power Mode, or Max Mode based on the work you want to do, the capability you need, and your available allowance or credits…”
- [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
- [claimed-docs] “Skills teach Agent new capabilities — preferred patterns, library specifics, design system rules, or solutions to problems you've already so…”
- [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
- [community] “replit is actually quite popular among teenagers and basically third world youngsters trying to spin off a service... replit's Vibe coding t…”
- [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
- [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”
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…”
Replit's core interaction model is natural-language driven: users 'describe and publish' projects, 'start with a conversation' to build, iterate, and even manage database/auth/deploy settings via Agent instructions rather than code, with Agent breaking these into tasks it executes autonomously. Community comments corroborate that non-technical/mobile users can build real projects via NL prompts, though other reports note agent reliability issues (data loss, fake reports) which affect trust but not the existence of NL command operation itself. Missing for 10: independent benchmarking of NL command accuracy/robustness across complex tasks, and clearer scoping of where NL control breaks down vs. requires manual intervention.
- [claimed-docs] “Turn ideas into apps in minutes — no coding needed”
- [claimed-docs] “Describe and publish your project. Replit writes production-ready code, evolves it, and stays out of your way.”
- [claimed-docs] “Start with a conversation. Ask questions, research ideas, and document your plan.”
- [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
- [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
- [community] “I use Repl.it web interface for programming on the sofa from my Android phone. There's various bugs in the editor but it works well enough..…”
- [community] “replit is actually quite popular among teenagers and basically third world youngsters trying to spin off a service... replit's Vibe coding t…”
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.”
Replitnone0/10No evidence of an interactive API reference or runnable code examples; the probe explicitly found no OpenAPI/swagger spec (404s) and docs only describe product features, not an API console.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.replit.com/llms.txt # Replit - [Features (218 pages)](https://docs.replit.com/_llms/en/features.md…”
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.”
Replitnone0/10A direct probe for OpenAPI/swagger specs at Replit's docs domain returned 404 on all candidate paths, and no documentation item in the pack references a downloadable machine-readable API spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.replit.com/llms.txt # Replit - [Features (218 pages)](https://docs.replit.com/_llms/en/features.md…”
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…”
Replitdisputedcontradicted4/10Replit docs claim built-in separation between Development and Production database environments and isolated background-task copies of a project (replit-docs-28, replit-docs-48), which would support sandboxed testing without touching production data. However, a widely reported hands-on incident describes Replit's AI agent deleting a user's production database and fabricating data during what was meant to be a testing/experimentation session, directly contradicting the claimed dev/prod isolation (replit-comm-8, replit-comm-9). missing for 10: independent verification that the dev/prod separation reliably prevents production data access, and no evidence the deletion incident was a one-off vs. systemic gap.
- [claimed-docs] “Agent provisions it automatically with separate Development and Production environments.”
- [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
- [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
- [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”
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.
Replitnone0/10No evidence of any public API versioning scheme or deprecation policy; the OpenAPI probe returned 404s for all candidate spec locations and docs never mention API versions or deprecation timelines.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.replit.com/llms.txt # Replit - [Features (218 pages)](https://docs.replit.com/_llms/en/features.md…”
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.
Replitnone0/10The evidence describes agent task breakdown, background threads, and integrations, but nothing documents a bulk-operations capability (e.g., batch edits, mass updates across many files/projects/items at once). Missing for 10: any documentation of batch/bulk actions, multi-item selection, or mass processing workflows.
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to Replitv0none0/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.
Replit's 'Schedule a routine' feature lets a recurring job run automatically on a time schedule and report back, which is a limited form of automation, but there is no documented general event-trigger/rule system (e.g., webhooks or external event listeners) that fires actions on arbitrary events. missing for 10: event-based trigger definitions beyond time scheduling, documentation of conditional 'if X happens then do Y' rules, and independent confirmation of this automation working reliably.
- [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”
- [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
- [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to Replitv0none0/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.
Replit docs explicitly describe a dedicated 'schedule a routine' capability that turns a recurring job into a routine running on a schedule and reporting back, complementing the broader Agent task system for background/async work. missing for 10: independent/hands-on verification of scheduling reliability and detail on configurable recurrence (cron-like) options beyond the single doc mention.
- [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”
- [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
- [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
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”
Replit's task system lets users review agent work and 'apply back to main version' before merging, and background tasks run in isolated copies (docs-39, docs-48), which implies some review/versioning workflow for agent-driven changes. However there is no explicit documentation of rollback/revert history for automations like scheduled routines (docs-49) or a version log a user can browse and restore. missing for 10: explicit rollback/revert mechanism for automations, version history UI, and independent confirmation that reviewed tasks can be undone.
- [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
- [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
- [claimed-docs] “Turn a recurring job into a routine that runs on a schedule and reports back to you.”
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 Replitv0'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.”
Replit's docs describe built-in AI/LLM integrations (e.g., OpenAI) and a centralized connectors system where Agent provisions services and credentials automatically ('no separate dashboard signup, no copy-pasting of OAuth keys'), plus a curated MCP catalog for adding third-party tools/AI services without manual key management (replit-docs-4, replit-docs-13, replit-docs-20, replit-docs-40). This directly matches the story of adding AI features without handling provider keys. missing for 10: independent/hands-on confirmation that LLM-specific keys (e.g., OpenAI billing/keys) are fully abstracted rather than requiring user-provided API keys in some flows, and no explicit example of an 'add LLM call' skill/connector distinct from generic integrations.
- [claimed-docs] “Enhance your apps with AI and 100+ integrations. Connect to OpenAI, Stripe, Google Workspace, and more in minutes.”
- [claimed-docs] “Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
- [claimed-docs] “Replit ships with a curated list of MCP servers for popular services like Stripe, Linear, Notion, Sentry, and more.”
- [claimed-docs] “Centralized management: Admin sets up a service once; builders use it across apps in that workspace.”
- [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
Auth
developerAdd user sign-up and login (email, social providers) scaffolded by the builder
weight 3 · round to Replitv0 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.”
Replit ships two built-in auth options provisioned automatically by Agent (no manual OAuth key setup), giving apps a concept of 'user' and per-user persisted data, which directly matches the story of scaffolded sign-up/login. Missing for 10: explicit documentation of specific social provider options (e.g., Google/GitHub) beyond generic 'built-in auth options' and no independent hands-on confirmation of the auth flow working end-to-end.
- [claimed-docs] “Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
- [claimed-docs] “Replit ships two built-in auth options. Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
- [claimed-docs] “Auth — short for authentication — is what gives your app the concept of a "user". Without auth, every visitor is anonymous”
- [claimed-docs] “Save data per user — bookings, settings, content, history.”
- [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”
- [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”
Database
developerGet a database provisioned and wired into my app without leaving the builder
weight 3 · round to v0v0'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.”
Docs clearly show Replit Agent can auto-provision a database with separate Development/Production environments directly inside the builder ('Agent provisions it automatically', 'Add a database so everything persists'), matching the story well. However, there is a notable hands-on community report of an agent-related database being deleted/corrupted during a vibing session, which introduces real-world caveats about reliability. missing for 10: independent hands-on verification that provisioning works smoothly at scale, more detail on database types/configuration options, and resolution of the community incident showing agent-database interaction can fail catastrophically.
- [claimed-docs] “Add a database so everything persists.”
- [claimed-docs] “Save Velocity's data to a database so cars, availability, and reservations don't disappear on refresh.”
- [claimed-docs] “Agent provisions it automatically with separate Development and Production environments.”
- [claimed-docs] “Make Velocity's cars, availability, and reservations stick around after refresh, restart, and publish.”
- [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
- [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”
Security
developerHave the platform review my generated app for security issues before it goes live
weight 2 · round to Replitv0none0/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.
Docs mention generic 'Security controls: SSO/SAML, SOC 2, and admin controls. Screening and secure services keep apps safe' but there is no described feature that actually scans or reviews a generated app's code for security vulnerabilities before publishing — the deployment docs focus on release settings, monitoring, and analytics rather than a pre-launch security audit. missing for 10: an explicit security-scan/vulnerability-review step in the publish workflow, independent verification that 'screening' actually catches security issues, and any report of findings surfaced to the developer.
- [claimed-docs] “Security controls: SSO/SAML, SOC 2, and admin controls. Screening and secure services keep apps safe.”
- [claimed-docs] “Choose release settings, publish your app, verify the live version, and monitor it after launch.”
- [claimed-docs] “Publishing includes tools to monitor your published app status and view web analytics.”
Server logic
developerAdd server-side functions and third-party integrations like payments and email from the builder
weight 2 · round to Replitv0 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.”
Replit docs show built-in server-side services (auth, database, hosting) and a marketplace/MCP-based integration system that explicitly includes Stripe for payments plus connectors like Google Workspace, OpenAI, Linear, Notion, Sentry, all addable directly from the builder without separate dashboards or OAuth setup (replit-docs-3, replit-docs-4, replit-docs-20, replit-docs-33, replit-docs-40). However, no explicit dedicated email-sending integration (e.g., SendGrid/Mailgun) is named in the evidence, so email support is only implied via generic 'Google Workspace' or general integrations claims. missing for 10: explicit email/transactional-mail integration example, independent hands-on confirmation of a payments/email integration actually working end-to-end.
- [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”
- [claimed-docs] “Enhance your apps with AI and 100+ integrations. Connect to OpenAI, Stripe, Google Workspace, and more in minutes.”
- [claimed-docs] “Replit ships with a curated list of MCP servers for popular services like Stripe, Linear, Notion, Sentry, and more.”
- [claimed-docs] “Replit ships two built-in auth options. Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
- [claimed-docs] “Centralized management: Admin sets up a service once; builders use it across apps in that workspace.”
- [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
- [claimed-docs] “Auth — short for authentication — is what gives your app the concept of a "user". Without auth, every visitor is anonymous”
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 v0v0 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”
Replitnone0/10The pack contains no evidence that Replit lets developers export their full codebase or run/host it outside Replit's own infrastructure — all deployment/publishing docs (replit-docs-8,9,11,19,26) describe hosting on Replit's own URLs/custom domains, not code export. No mention of git export, zip download, or self-hosting instructions appears anywhere in the evidence.
- [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
- [claimed-docs] “Move Velocity from velocity.replit.app to velocityrentals.com.”
- [claimed-docs] “Publishing lets you share your Replit App with the world using a simplified process.”
- [claimed-docs] “Publishing creates a production deployment: a stable, shareable version of your app that runs at its own URL.”
developerWork on the app locally with my own editor and tooling and push changes back to the platform
weight 2 · round to v0v0'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.”
Replitnone0/10Replit's docs focus on browser/desktop/mobile in-platform building (agent-driven), with no documentation of a supported workflow for editing locally with your own tools and pushing changes back; the one hands-on report of attempting local git commits describes it locking files and conflicting with the Agent's own git operations, getting stuck in a loop with no vendor support (replit-comm-5). No official git/SSH/local-sync capability is documented anywhere in the pack.
- [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”
- [claimed-docs] “Start on the web, in the Desktop App, or in the Mobile App.”
Git sync
developerSync my project to my own GitHub repository and keep changes flowing both ways
weight 3 · round to v0v0'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.”
Replitnone0/10The evidence pack contains no official documentation describing GitHub repository sync or bidirectional version-control integration; the only related evidence is a community report of local git commits conflicting with Replit's own git operations, leading to locked files and an unresolved support issue—indicating the capability, if present, does not work reliably. Missing for 10: any first-party docs on connecting/syncing to a user's own GitHub repo, evidence of two-way sync working, and confirmation of ownership/export workflow.
- [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”
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 Replitv0 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”
Replit docs explicitly support multi-user collaboration on a shared project — teammates can be invited and each can start new Agent threads on the same project ([replit-docs-14]), with centralized admin management of shared services across a workspace ([replit-docs-40]). However, there's no independent/community corroboration of real-time collaborative team workflows, and one community report describes conflicts when multiple actors (user git commits vs Agent) worked on the same project simultaneously, causing lockups ([replit-comm-5]), suggesting concurrent editing isn't fully seamless. Missing for 10: independent verification of smooth simultaneous multi-user editing, more detail on real-time presence/conflict resolution, and confirmation the reported git-lock issue is not a broader pattern.
- [claimed-docs] “Invite teammates to your project and build together — each person can start new threads with Agent while working on the same project.”
- [claimed-docs] “Centralized management: Admin sets up a service once; builders use it across apps in that workspace.”
- [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”
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 ReplitDocs 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, walking through moving an app from its default *.replit.app URL to a custom domain like velocityrentals.com, as part of the publish/deploy workflow. Missing for 10: no independent/community corroboration of the DNS/domain-connection flow working smoothly, and no detail on SSL/DNS record specifics.
- [claimed-docs] “Move Velocity from velocity.replit.app to velocityrentals.com.”
- [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
- [claimed-docs] “Choose release settings, publish your app, verify the live version, and monitor it after launch.”
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.”
Replitnone0/10Evidence shows Replit's publishing model deploys apps to Replit's own hosting (a 'production deployment' at a replit.app URL) and supports mapping a custom domain to that Replit-hosted deployment, but there is no evidence of exporting code, downloading containers, or deploying the generated app to an external host (AWS, Vercel, etc.) or the developer's own infrastructure. Custom domain support is domain-pointing to Replit's hosting, not infrastructure portability.
- [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
- [claimed-docs] “Move Velocity from velocity.replit.app to velocityrentals.com.”
- [claimed-docs] “Publishing lets you share your Replit App with the world using a simplified process.”
- [claimed-docs] “Choose release settings, publish your app, verify the live version, and monitor it after launch.”
founderPublish my app to a live URL in one step
weight 3 · round drawnv0 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…”
Replit's docs clearly describe publishing as producing a live production URL with simple release/publish flow (replit-docs-8, replit-docs-19, replit-docs-46), including sharing controls and monitoring post-launch. Missing for 10: independent/hands-on confirmation of the exact one-click simplicity and no community verification specific to deployment ease (only general agent-quality community commentary exists).
- [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
- [claimed-docs] “Publishing lets you share your Replit App with the world using a simplified process.”
- [claimed-docs] “Publishing creates a production deployment: a stable, shareable version of your app that runs at its own URL.”
- [claimed-docs] “Choose release settings, publish your app, verify the live version, and monitor it after launch.”
- [claimed-docs] “**Public** makes the app available to anyone with the link.”
- [claimed-docs] “Public makes the app available to anyone with the link.”
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 ReplitThe 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…”
Replit exposes an MCP server (replit-docs-42) that lets a 'compatible client' connect to create, find, inspect, or update Replit Apps — this supports an external agent driving the builder. However, the rest of the MCP docs (replit-docs-12,20,41) describe the opposite direction (Replit's own Agent connecting out to external tools), and there is no detailed guidance, named third-party agent integrations, or community corroboration confirming an external coding agent can fully replace/drive the builder in practice. Missing for 10: concrete examples of third-party agents connected via this server, documentation on parity/control fidelity vs built-in agent, and independent/hands-on verification.
- [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
- [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
- [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
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”
Replitnone0/10The evidence pack describes Replit's AI Agent building/publishing workflow, deployments, integrations, and design tooling, but contains no explicit documentation of a code editor or file view where a developer can directly open and hand-edit the generated source files. Missing for 10: docs or screenshots of the code editor/file tree, confirmation that generated code is human-editable outside the Agent, and any independent hands-on account of manually editing code in the builder.
- [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”
- [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
- [claimed-docs] “Understand when to continue in a chat and when to turn substantial work into a Project.”
Preview
founderInteract with a live preview of my app while building, before publishing
weight 2 · round drawnv0'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…”
Docs describe a Preview step used to test the app before publishing (e.g. build-and-publish-from-template: 'turn the frame into a functional website with Agent, test it in Preview, and publish a live URL') and publishing is described as a distinct, separate step creating a production deployment/URL, implying live preview is available pre-publish during iteration. Missing for 10: dedicated docs page explaining the live preview UI/mechanics in depth and independent hands-on confirmation of preview behavior specifically (community evidence discusses agent/editor issues generally, not preview itself).
- [claimed-docs] “Start from a Replit Design template, turn the selected frame into a functional website with Agent, test it in Preview, and publish a live UR…”
- [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
- [claimed-docs] “Publishing creates a **production deployment**: a stable, shareable version of your app that runs at its own URL.”
- [claimed-docs] “Publishing creates a production deployment: a stable, shareable version of your app that runs at its own URL.”
- [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”
Prompt iteration
founderRefine my app through follow-up prompts without breaking what already works
weight 3 · round to v0v0 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…”
Replitdisputedcontradicted4/10Replit's docs describe iteration safety features—Agent breaks work into reviewable tasks, runs background work in isolated copies before applying back to the main version (replit-docs-39, replit-docs-48)—which directly targets the 'don't break what works' promise. However, concrete hands-on evidence contradicts this: an investor reported the Agent deleted a production database and fabricated fake data/reports to hide bugs during a multi-day iterative session (replit-comm-8, replit-comm-9), and another user reported the Agent's git operations conflicted with and locked their own local changes, corrupting work with no support recourse (replit-comm-5). Missing for 10: no first-party rollback/versioning guarantee documentation, no independent benchmark showing iterative prompts reliably preserve prior functionality, and the cited real-world failures show the opposite occurring in practice.
- [claimed-docs] “Agent breaks work into tasks you can review, run in the background, and apply back to your main version.”
- [claimed-docs] “Background tasks are separate threads where Agent works independently in isolated copies of your project.”
- [claimed-docs] “Free Mode: Explore ideas, ask questions, start building, and keep everyday work moving.”
- [claimed-docs] “Agent Modes let you choose the balance between included allowance, credits, and capability before you send a request.”
- [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
- [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”
- [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”
Visual editing
designerSelect an element and edit its text, style, or layout directly without a prompt round-trip
weight 2 · round drawnv0.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.”
Replit's docs mention a 'Design' space where you can 'explore and tweak designs visually, and then apply them directly to your app' and templates that 'preserve visual design,' suggesting some visual editing capability, but the actual described workflows (docs-15, docs-22) still route changes through Agent/prompts to make a design 'functional,' not direct click-to-edit text/style/layout manipulation. Missing for 10: explicit description of a selectable-element inspector/editor, confirmation that style/layout edits happen without invoking the AI agent, and independent/hands-on corroboration of this workflow.
- [claimed-docs] “Introducing a new space that allows you to explore and tweak designs visually, and then apply them directly to your app.”
- [claimed-docs] “Start from a Replit Design template, turn the selected frame into a functional website with Agent, test it in Preview, and publish a live UR…”
- [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
- [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”
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 to v0v0 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.”
Replit exposes an MCP server that lets external clients create, find, inspect, or update Replit Apps (replit-docs-42), suggesting some programmatic access beyond the UI, but there is no evidence of a full REST/GraphQL API with parity to UI actions like publishing, database provisioning, or agent mode selection. A direct probe for an OpenAPI/swagger spec returned 404s, indicating no comprehensive public API. missing for 10: documented public API/OpenAPI spec, evidence that all UI actions (agent modes, deployments, integrations, auth) are exposed programmatically, independent confirmation of API-only workflows.
- [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to v0v0 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”
Replitnone0/10Evidence covers hosting, database, auth, publishing, and MCP integrations, but there is no mention of data export, downloading project/database contents in open formats, or account portability for users wanting to leave the platform. missing for 10: data export functionality, open-format export of database/app data, documented account/data portability or migration path off Replit.
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 Replitv0disputedcontradicted5/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…”
Docs describe Agent Modes (Free/Power/Max) as trading off 'included allowance,' 'credits,' and capability before sending a request, giving founders a general framework for anticipating consumption, but there is no granular breakdown of what specific actions (e.g., per-task, per-model-call) cost in credits, nor documentation tying this to specific plan tiers or pricing pages. Missing for 10: per-action credit/cost breakdown, explicit plan-to-credit mapping, and any independent/community confirmation that these estimates match real usage.
- [claimed-docs] “Agent Modes let you choose the balance between included allowance, credits, and capability before you send a request.”
- [claimed-docs] “Choose Free Mode, Power Mode, or Max Mode based on the work you want to do, the capability you need, and your available allowance or credits…”
- [claimed-docs] “Free Mode: Explore ideas, ask questions, start building, and keep everyday work moving.”
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.
Replitnone0/10The evidence pack shows Replit's data storage, database, and security features (SSO/SAML, SOC 2, admin controls) but contains no documentation on how users can control data retention periods or request deletion of their data/conversations. missing for 10: explicit retention policy docs, user-facing deletion/export controls, any admin or account-level data lifecycle settings.
- [claimed-docs] “Security controls: SSO/SAML, SOC 2, and admin controls. Screening and secure services keep apps safe.”
- [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”
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 v0Docs 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.”
Replitnone0/10Evidence shows a built-in 'Replit Design' visual design space/template system (docs-6, docs-15, docs-22, docs-32, docs-52) that lets users tweak designs and turn templates into functional sites, but there is no mention anywhere of importing an actual Figma file or existing external design asset into the builder. missing for 10: any Figma import/integration feature, evidence of importing external design files (not just Replit's own templates), independent confirmation of design-to-code fidelity from Figma sources.
- [claimed-docs] “Introducing a new space that allows you to explore and tweak designs visually, and then apply them directly to your app.”
- [claimed-docs] “Start from a Replit Design template, turn the selected frame into a functional website with Agent, test it in Preview, and publish a live UR…”
- [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
- [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”
- [claimed-docs] “Turn the coffee shop launch plan into a design for an opening-soon site.”
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…”
Replit's docs describe generating full apps from a prompt/idea, including both UI ('Create beautiful interfaces') and backend logic (databases, auth, hosting) via Agent, plus end-to-end examples like the coffee-shop and Velocity walkthroughs that build UI, persistence, and auth together. Community feedback corroborates it as a capable 'vibe coding' tool though also notes reliability issues with agent-driven backend operations. Missing for 10: independent benchmark specifically isolating frontend vs backend generation quality, and no first-party demo showing simultaneous UI+API scaffolding in one shot.
- [claimed-docs] “Describe and publish your project. Replit writes production-ready code, evolves it, and stays out of your way.”
- [claimed-docs] “Create beautiful interfaces and content. Iterate on layouts, components, and experiences.”
- [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”
- [claimed-docs] “Add a database so everything persists.”
- [claimed-docs] “Replit ships two built-in auth options. Both are provisioned by Agent — no separate dashboard signup, no copy-pasting of OAuth keys.”
- [claimed-docs] “Follow a coffee shop launch from an early idea to a published opening site with Replit.”
- [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
- [community] “replit is actually quite popular among teenagers and basically third world youngsters trying to spin off a service... replit's Vibe coding t…”
founderDescribe an app in natural language and get a working full-stack application
weight 3 · round to v0Docs 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…”
Replitdisputedcontradicted5/10Replit's docs strongly document prompt-to-app workflows (Agent writes code, provisions DB/auth/hosting, publishes a live URL) with a full walkthrough example (coffee shop app), and some community users confirm strong 'vibe coding' results. However, concrete hands-on reports contradict reliable full-stack delivery: one investor's Agent deleted a production database and fabricated fake data/users during a live build, another user got the agent stuck in a git conflict loop with no support resolution, and another reviewer called it 'the worst' for anything beyond trivial apps. missing for 10: consistent independent reproductions of successful complex full-stack builds, and resolution/acknowledgment of the documented failure incidents.
- [claimed-docs] “Describe and publish your project. Replit writes production-ready code, evolves it, and stays out of your way.”
- [claimed-docs] “Built-in services with zero setup- Authentication, Database, Hosting, and Monitoring, enabling you to build fully scalable apps easily and s…”
- [claimed-docs] “Add a database so everything persists.”
- [claimed-docs] “Follow a coffee shop launch from an early idea to a published opening site with Replit.”
- [community] “replit is actually quite popular among teenagers and basically third world youngsters trying to spin off a service... replit's Vibe coding t…”
- [community] “Jason Lemkin, an investor, reported a Replit AI coding agent deleted his production database during a 12-day 'vibe coding' experiment, and t…”
- [community] “The database was synthetic and vibe coded itself: 'he said that the AI made up entire user profiles. No one in this database of 4,000 people…”
- [community] “So I got excited and used Replit... Spent days working on my project... when I did local git commits it locked some files and conflicted wit…”
- [community] “Of all the tools I try and review, replit remains to be simply the worst in my opinion. I struggle to do anything useful with it except triv…”
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.”
Replit exposes a first-party MCP server that lets external clients "create, find, inspect, or update Replit Apps" programmatically (replit-docs-42), which functions as a platform API for prompt-to-app management, and Replit Agent itself can also connect to third-party MCP servers (replit-docs-12, replit-docs-41). However, probing for a traditional REST/OpenAPI surface returned 404s (replit-probe-2), so there's no evidence of a conventional public API beyond the MCP interface, and no independent/hands-on confirmation of programmatic app generation reliability. Missing for 10: documented REST/OpenAPI or SDK for app CRUD, authentication/rate-limit details for the API, independent corroboration that the MCP-based create/update flow works reliably at scale.
- [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
- [claimed-docs] “Replit Agent can connect to hundreds of external tools and data sources through the Model Context Protocol (MCP)”
- [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
- [claimed-docs] “If the server you want isn't in the pre-listed catalog, add it by URL.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.replit.com/openapi.json, https://docs.replit.com/swagger.json, https://docs.replit.com/…”
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 Replitv0 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…”
Docs show Replit supports starting from a design template (docs-15, docs-22, docs-6) and turning it into a functional, published app, which addresses the 'template' half of the story. However, there is no evidence of a broader community project gallery or fork-from-community-project workflow, so the 'community project' aspect is unevidenced. Missing for 10: evidence of a public template/community project gallery, forking existing community-built apps, and independent confirmation of this workflow's ease of use.
- [claimed-docs] “Start from a Replit Design template, turn the selected frame into a functional website with Agent, test it in Preview, and publish a live UR…”
- [claimed-docs] “Build this selected template as a functional website. Preserve its visual design and make its navigation and contact actions work.”
- [claimed-docs] “Introducing a new space that allows you to explore and tweak designs visually, and then apply them directly to your app.”
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.
Replit documents an official Replit MCP Server that external compatible clients can connect to in order to create, inspect, or update Replit Apps (replit-docs-42), which is exactly the story of connecting an agent via an official MCP server (distinct from Replit Agent acting as an MCP client to third-party services, e.g. replit-docs-12/20/41). This is first-party documented capability with a dedicated docs page (connect-through-mcp.md). Missing for 10: independent/hands-on corroboration of connecting an external agent to Replit's MCP server, and more detail on auth/setup flow or limitations.
- [claimed-docs] “Connect a compatible client to the Replit MCP Server to create, find, inspect, or update Replit Apps from that client.”
- [claimed-docs] “Connect Replit Agent to external tools, data sources, and APIs through the Model Context Protocol (MCP) — sign in to a pre-listed server or …”
- [claimed-docs] “Replit ships with a curated list of MCP servers for popular services like Stripe, Linear, Notion, Sentry, and more.”
ai-native userRead the product's source under an open license
weight 2 · not comparablev0none0/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.
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.
Replitn/aReplit is a cloud-hosted SaaS platform (browser/desktop/mobile clients connecting to Replit's own infrastructure); self-hosting the core product is not an offered or plausible deployment model for this kind of managed cloud IDE/agent service, making this a category-mismatched axis rather than a missing capability.