Replit
Unclaimed verified 8 oct 2026Build apps and sites with AI
TL;DR
Replit is an AI-powered, browser-based development platform for turning natural-language prompts into websites, web apps, mobile apps, prototypes, and internal tools. It is aimed at nontechnical builders, product teams, educators, freelancers, and developers who want rapid iteration; its key differentiator is combining AI generation with coding, hosting, databases, authentication, collaboration, and deployment in one environment.
What Users Actually Pay
No user-reported pricing yet.
Our Take
Replit sits between no-code app builders and conventional developer environments. It exposes source code and a browser-based workspace while also allowing users to generate and modify applications through natural-language instructions. This gives it a faster path from idea to working prototype than a traditional development stack. Its strongest advantage is speed to first result. Reviewers frequently praise the absence of local setup, integrated execution and deployment, collaborative workflows, and the ability to convert plain-English requirements into functioning applications. This makes it particularly attractive for MVPs, prototypes, education, demos, and lightweight internal tools. The main risks relate to AI reliability, cost predictability, and production readiness. User feedback mentions credit or token consumption, unexpected charges, repeated debugging loops, unintended code changes, and difficulty handling more complex projects. These concerns do not eliminate Replit’s value, but they make code review, budget controls, backups, and independent production safeguards important. Replit is best suited to rapid prototyping, small SaaS products, internal tools, education, and teams prioritizing speed over maximum infrastructure control. It is less suitable as the sole platform for mission-critical systems without additional testing, monitoring, external backups, and operational controls.
Alternatives
Ranked by Revuo score — paid tiers never affect order.
Claude
The AI for problem solvers — your thinking partner
Cursor
AI coding agent
OpenHands
The open platform for AI coding agents that execute real engineering work
Devin
The AI Software Engineer
Revolte
AI for Software Engineering that executes the full SDLC from intent to production
Devin
The first autonomous AI software engineer
Pros
- + Fast idea-to-prototype workflow, with reviewers praising the ability to create functioning applications from plain-English requirements.
- + No local development setup required; users can start coding and deploying from a browser.
- + Integrated execution, hosting, storage, authentication, databases, and collaboration reduce the need to assemble multiple services.
- + Accessible to nontechnical users and useful for education, experimentation, and demos.
- + Strong support for AI-assisted application generation and rapid iteration.
Cons
- - Usage-based billing and AI retries can make costs difficult to predict.
- - AI behavior can be inconsistent on complex projects, including repeated fixes, debugging loops, or unintended changes.
- - Some reviewers question whether the platform is ready for serious production workloads.
- - Support, cancellation, and refund experiences receive criticism in some reviews.
- - The managed environment can provide less infrastructure control and portability than a conventional local or cloud stack.
Agent Readiness
57/100Replit is highly agent-ready as an AI-native environment for building, testing, and deploying applications. Its integrated browser workspace, hosted execution, secrets, databases, authentication, deployment, connectors, and MCP-related capabilities are strong for autonomous application creation. However, its external platform API surface is comparatively limited: the documented Admin API is Enterprise-only and beta-oriented, while broad programmatic control of arbitrary projects is not clearly exposed as a mature, open developer platform. Native Zapier, Make, and n8n integrations were not identified; HTTP APIs, webhooks, custom connectors, and MCP are the more practical integration paths.
Last checked Oct 8, 2026
MCP Integrations
1 server9 tools19 total uses9 tools
ask_questionAsk the Replit Agent a question in natural language about the user's Replit App's codebase or behavior without modifying it. Use this when the user wants explanation, debugging help, or inspection (for example, understanding how routing works, why a request is failing, or where a bug might be), and NOT when they are clearly asking you to change how their Replit App behaves — in that case, prefer update_app_using_prompt. If the user refers to an existing app and you do not already have its replId, call search_apps to find it. Do not guess a replId. The question should be written in the user's language and tone, as if you were the user, and it will be visible if they open their Replit App in Replit. The response you get back is natural language from the Replit Agent; summarize or quote it for the user as appropriate, still without showing raw code, file paths, or terminal commands in this chat. From the user's perspective, combined with create_app_from_prompt, search_apps, and update_app_using_prompt, this tool is what lets them simply chat ("create or find → inspect/ask → update → repeat") without needing to know about the underlying tools.create_app_from_promptCreate a brand-new Replit App for the user. Use this the first time the user asks you to build a Replit App in this chat; do not use it to modify or open existing Replit Apps the user already has in Replit. After invoking this tool, reply with one short sentence summarizing that Replit is now creating their Replit App, and, when the tool result contains an app URL, end your reply with that exact URL on its own line, so the user can open their Replit App even if no preview card is rendered. Never construct or guess a URL yourself. Your reply must not include source code, markup, configuration files, file paths, or command/terminal snippets—even if the user asks. Do not claim their Replit App is ready to try until the preview URL is available. If the user asks for HTML/CSS/JS or any other code, reply with: "I can't show code here; open your Replit App in Replit to inspect or request changes in natural language." Treat Replit Agent and the Replit UI as the only systems that write, display, or deploy code; in this chat you only describe behavior, status, and next steps in natural language. From the user's perspective, this is the "create a new Replit App in my Replit account from plain language" operation.list_appsList Replit Apps the user can edit, most recently updated first; `query` optionally filters by matching app titles, surfacing the best matches for the query first. Use this when the user wants to browse or pick from their apps, or when you need a replId but resolve_app_by_name returned found=false because the user gave an approximate name — present the returned titles and let the user choose, then pass the chosen replId to update_app_using_prompt or ask_question. This is a search/list, not the exact resolver: prefer resolve_app_by_name when the user already gave an exact app name. Results can include apps owned by or shared with the user.resolve_app_by_nameLook up by exact name a Replit App the user can edit and return its replId (UUID) and URL. Use this when the user refers to an app by name (e.g. "update my Todo App", "what does my Recipe Tracker do?") and you don't already have a replId from create_app_from_prompt earlier in this conversation. Pass the result's replId into update_app_using_prompt or ask_question to act on the app. Matching is case-insensitive but exact: this is a name resolver, not a search. If the user gives you an approximate or partial name and this tool returns found=false, call list_apps (optionally with the partial name as the query) and let the user pick from the results rather than guessing. Results can include apps owned by or shared with the user.search_appsSearch Replit Apps the user can edit (owned or shared with them). query is a BM25-style keyword search over app titles, best matches first; updatedAfter/updatedBefore bound the last-updated time; these combine. Prefer the default recency ordering: only set updatedAfter/updatedBefore when the user explicitly asks to filter by time, since date bounds exclude apps that would otherwise be listed. url resolves a Replit App URL directly to that app and ignores the other filters. With no filters, this returns the user's most recently updated apps. Pass a result's replId to update_app_using_prompt or ask_question to act on that app. <important>This tool is EXPERIMENTAL: prefer it for finding the user's apps, but if it errors or its results do not match what the user described, fall back to resolve_app_by_name (exact name) and list_apps (recent apps).</important>update_app_using_promptUpdate the user's Replit App. Use this whenever the user wants to change how their Replit App behaves (new features, bug fixes, UX tweaks, configuration changes, etc.). Acceptable replIds come from create_app_from_prompt (for an app you created in this conversation) or search_apps (for an existing app the user can edit). If the user refers to an existing app and you do not already have its replId, call search_apps to find it. Do not guess a replId. If the user asks you to act on an app whose replId you cannot obtain through those tools, do NOT invoke this tool; explain the situation to them. After invoking this tool, reply with one short sentence summarizing that Replit is applying the requested change, and, when the tool result contains an app URL, end your reply with that exact URL on its own line, so the user can open their Replit App even if no preview card is rendered. Never construct or guess a URL yourself. Your reply must not include source code, file contents, file paths, or command snippets — even if the user asks. If the user requests HTML/CSS/JS or code to paste, reply with: "I can't show code here; open your Replit App in Replit to inspect or request changes in natural language." Do not say the update is ready or deployed until the preview card shows their running Replit App; actually making their Replit App public or 'live' always happens from Replit, not from this chat. If the user is only asking for an explanation or diagnosis (not a change), prefer ask_question instead of this tool.replit_widget_get_auth_tokenInternal tool for Replit's app builder. This must not be called directly by the model.replit_widget_start_app_previewInternal tool for Replit's app builder. This must not be called directly by the model.replit_widget_get_preview_urlInternal tool for Replit's app builder. This must not be called directly by the model.
Last checked Sep 14, 2026
[ features ]
Geostrategic Position
Information on which part of the world this product / vendor belongs to, i.e. the country of their headquarters primarily, but also their hosting options etc.
Find which geostrategic world region the headquarter is located in. Relevant for compliance questions (e.g., CLOUD Act) or risk of cut-off in case of conflicts. For example, some EU companies are worried about the US and would definitely not host their customer with Chinese or Russian companies.
The hosting provider that is used to host this product, if any.
The available hosting locations, if you can choose
Compliance & Security
Security certifications, compliance features, and access control capabilities.
SOC 2 Type I or Type II certification.
ISO 27001 information security certification.
Built-in tools for GDPR compliance (data export, deletion, consent).
Complete audit log of all data changes.
Granular permissions based on user roles.
Single Sign-On integration support.
Security, Privacy & Support
Features ensuring data protection, quality assurance, and user assistance.
Compliance standards for data security.
Automatic deletion of user photos after processing.
Availability of real-time customer support.
Offers free remakes for unsatisfactory results.
Pricing & Free Tier
Free tier limits and overall pricing structure.
Maximum Monthly Active Users allowed on the free tier.
Key usage metrics that incur costs.
Autonomy & Workflow
Level of autonomous execution and human oversight mechanisms across the SDLC
Can complete multi-step engineering tasks with minimal human intervention
Provides explicit approval gates, oversight dashboards, and workflow governance
Supports running multiple agents simultaneously for concurrent tasks
Automatically learns and retains knowledge from existing codebases over time
SDLC Coverage
Which stages of the software delivery lifecycle the product can handle
Supports ingesting requirements from Jira, Figma, or natural language and generating plans
Generates or edits production code across multiple files
Creates tests, runs test suites, and performs visual or regression QA
Handles deployments, incident triage, runtime monitoring, and observability
Performs pull request reviews and generates documentation
Integrations & Ecosystem
Connections to developer tools, IDEs, and collaboration platforms
Supported code editors and development environments
Native integration with GitHub, GitLab, or other version control systems
Connections to issue tracking and project management tools
Integrations with communication and alerting platforms
Compare With
Reviews
No reviews yet. Be the first to review Replit!