Bolt
- Best for
- A browser-first build with a documented GitHub handoff and built-in hosting.
- Not ideal for
- A project that assumes switching its database later will be effortless.
From prompt to a runnable app
Which AI app builder fits the app you need to deliver?
Bolt, Lovable, Replit and v0 can help turn a brief into a runnable product. Code, hosting, data and ongoing ownership do not move together with a prompt, though. Start with your delivery path, then check the conditions behind each choice.
This guide is about generating and publishing a site or app, not IDE code completion, debugging or refactoring assistants.
Choose a starting path
Lovable
- Best for
- A web app that benefits from repository sync and a deliberate publish step.
- Not ideal for
- A team expecting Git sync alone to move its database, files and credentials.
Replit
- Best for
- A project that needs Git workflows and a choice among documented deployment modes.
- Not ideal for
- A team assuming its subscription fixes the total cost of Agent and app runtime.
v0
- Best for
- A Vercel-oriented project that wants branch-based GitHub review before publishing.
- Not ideal for
- A project requiring a documented, complete database and backend migration path today.
Compare the delivery boundaries
Each cell summarizes the relevant official documentation, not a hands-on account, app or migration test by this directory. Open the source to check its scope.
| Decision point | Bolt | Lovable | Replit | v0 |
|---|---|---|---|---|
| Code and Git handoff | GitHub connection and code sync. Documented Official source | Two-way repository sync and code download. Documented Official source | Git-backed version control and GitHub workflows. Documented Official source | Working branches and pull-request review with GitHub. Documented Official source |
| Hosting and deployment | Built-in hosting; a documented Netlify path has prerequisites. Documented Official source | Publish a snapshot to a lovable.app URL; later edits need republishing. Documented Official source | Static, Autoscale, Reserved VM and Scheduled deployment modes. Documented Official source | Vercel preview deployments and a linked production publish path. Documented Official source |
| Data and backend move | Supabase options depend on plan; changing backend later takes extra steps. Depends on setup Official source | Cloud database export is documented; files, secrets and services need separate work. Depends on setup Official source | Database export and scenario-specific dump/restore are documented, not whole-app migration. Depends on setup Official source | Database integrations are documented; a complete exit path is not established. Not established Official source |
| Integrations | Documents GitHub, Stripe, Expo, Supabase and other paths; eligibility varies. Depends on setup Official source | Connector and direct API paths; permissions and credentials vary. Depends on setup Official source | Managed, connector and bring-your-own-key paths; plan access varies. Depends on setup Official source | Documents databases, external APIs and Stripe; provider setup remains separate. Documented Official source |
| Cost boundary | AI tokens and hosting allowances differ; subscription is not total app cost. Depends on setup Official source | Build, Cloud, AI and connectors may consume different credits. Depends on setup Official source | Agent, third-party services and cloud usage can draw on credits. Depends on setup Official source | Plan credits and model usage vary; connected Vercel services can cost extra. Depends on setup Official source |
| Who maintains it? | Security checks help, but do not replace owner review and service configuration. Depends on setup Official source | Automated scans do not guarantee application security. Depends on setup Official source | A shared-responsibility model leaves app and account duties to assess. Depends on setup Official source | Publishing depends on GitHub/Vercel roles; ongoing operations are not fully specified. Depends on setup Official source |
Boundaries worth checking
- A Git repository mainly hands off code. Check database contents, files, secrets, domains and runtime settings separately.
- v0 documents database integrations, but the reviewed source does not establish a complete exit procedure. That proves neither portability nor lock-in.
- Replit, Bolt and Lovable document particular data moves with conditions; none of those sources establishes a one-click whole-app migration.
- A subscription is not a total app cost. Build usage, hosting, databases and third-party services can be billed separately.
Five questions before you choose
- Are you delivering a static site, a backend app, or a prototype that engineers will take over?
- Who controls the repository, deployment account, domain, secrets and database backups?
- If you leave the platform, how will you move and verify resources beyond source code?
- Which connectors, deployment options and allowances apply to your actual account?
- Who will own security review, spend monitoring, fixes and recovery drills after launch?
Sources and review date
This guide summarizes official documentation reviewed on October 13, 2026. Prices, allowances and account entitlements may change. Recheck checkout and project-specific eligibility with each provider.
If your main task is code completion, debugging or refactoring inside an IDE, use the developer-tools guide instead.
Explore developer tools