Lovable

Build full-stack apps by chatting with AI

by Lovable

Overview

Lovable turns a description into a working web application. New applications created from 13 May 2026 use TanStack Start, including server-side code; older applications use React and Vite.

A managed backend or Supabase can support the application, and you refine it by chatting or editing the interface. The plans bill per workspace rather than per seat, so members share one credit balance: Pro starts at $25 a month or $250 a year with 100 credits a month, Business at $50 a month or $500 a year with the same starting allowance, and any number of members can be invited.

One credit balance now covers building, chat, Cloud backend and hosting, in-app AI and some connectors, following the billing change announced on 13 June 2026, so model calls, traffic, compute and tool calls draw on the same pool and a fixed cost per message is not something we can promise. The free plan has five build credits a day up to 30 per calendar month, and workspaces also carry a temporary monthly allowance of 20 Cloud credits and 4 AI credits, which are credit amounts rather than dollars.

Source code can be synced to GitHub on every plan with new repositories private by default, and paid plans add a download of the codebase. What travels is the application: the Lovable editor and its AI agent are hosted and cannot be deployed into your own network, and moving the backend is separate work - there is no one-click migration from Cloud to your own Supabase, and Supabase to Cloud is not supported either.

Editor's take

A reasonable choice for a first version of a web app you intend to host yourself, and for teams that want to keep the source in GitHub. Budget separately for the backend move: the database, storage, auth and runtime services each need their own migration work, and the editor itself stays a hosted service.

Our reading of who this suits, based on the sources above. Opinion, offered to help you decide - not a lab result.

Key Features

Describe an app and get a Vite and React front end with a managed backend or Supabase
Per-workspace credits shared by unlimited invited members, not per seat
Pro $25 a month or $250 a year and Business $50 or $500, each starting at 100 credits a month. Annual plans charge the annual total up front and release credits monthly; Business follows the same $50 monthly and $500 annual structure
One balance covers building, chat, Cloud backend and hosting, in-app AI and some connectors since the 13 June 2026 billing change
GitHub sync on every plan with private repositories by default, plus a codebase download on paid plans
Custom domains and removal of platform branding require a paid plan; internal publishing and the Lovable API are listed at Business or Enterprise

Use Cases

A first working version of a web app to validate an idea
Internal tools with a database and sign-in
Prototypes that a developer will take over through GitHub
Small marketing or customer-facing apps with a managed backend

Pros

✓Source code can be synced to GitHub on every plan, with private repositories by default
✓Credits are billed per workspace with unlimited members rather than per seat
✓The generated application can be hosted elsewhere, and rights in what you build are yours

Cons

✕The editor and AI agent cannot be self-hosted or deployed into a customer network
✕Moving the backend is manual: data export, a new Supabase project and a schema rebuild, with no one-click path either way
✕When credits run out, builds stop and runtime AI fails, and Cloud backend services may pause while static pages keep serving
✕Importing an existing GitHub repository into Lovable is not supported, so a clone does not take over an established codebase
✕Cloud locks to a region once enabled, and removing it deletes the instance, which has to be backed up first

Frequently Asked Questions

Can I take the code with me?

All plans can sync code with Git; a paid plan also permits downloading the codebase as a .zip archive. Code export includes source and database migration files, but not database contents or uploaded storage, which require separate export. The application can be moved; Lovable’s editor and AI agent remain managed services and cannot be deployed into your VPC. No complete backup or migration was tested.

What do credits cover now?

Since the billing change announced on 13 June 2026 one workspace balance covers building, chat, the Cloud backend and hosting, in-app AI and some connectors, where older guidance described separate Cloud and AI wallets. Models, traffic, compute and tool calls consume different amounts, so a fixed cost per message is not something we can promise.

Can I move the backend off Lovable Cloud?

There is no one-click migration. Moving from Cloud to your own Supabase means exporting the data, connecting Supabase in a new Lovable project and rebuilding the schema, and remixing stays on Cloud rather than switching the backend. Moving from Supabase to Cloud is not supported either, Cloud locks its region once enabled, and removing Cloud deletes the instance permanently, so back up first.

Can Lovable take over my existing codebase?

Not from an arbitrary existing repository: the official FAQ says importing an existing GitHub repository to start a new Lovable project is not supported. GitHub sync keeps a project it created in step with a repository, which is the opposite direction.

What happens when credits run out?

Builds pause, runtime AI fails and Cloud backend services may pause. Static pages can keep serving, which does not mean sign-in, the database or AI still work, and a paused database cannot be accessed or exported while it is paused. Deployment cost also varies with runtime use, so the monthly plan price is not the whole production cost.

How are Lovable API endpoints and MCP creation billed?

Creating a workspace-scoped Lovable API key requires a Business or Enterprise plan and workspace owner/admin role; the account email must be verified before API calls. Owners/admins on all plans may register OAuth clients, while sensitive OAuth scopes require Business/Enterprise. Current management/deployment endpoints, including deployment builds, do not consume AI build credits. AI project creation/editing uses the separate MCP server; this is not an all-API/MCP-free guarantee.

Source: lovable official lov-api

Task guides for this product

T6 · Compare builders for GitHub sync and custom domains

Key facts and where they come from

PriceNot established: The plan documentation confirms plan/credit tiers, but applicable purchase region and account-specific current checkout conditions remain unestablished. The previously read USD amount is not promoted to a global purchasable quote.Source: Lovable - subscription plans · Lovable - pricing
AvailabilityNot established: Hosting/deployment and workspace/API entry points are documented, but current country-by-country Lovable subscription access and eligibility remain unestablished; deployment region is not distribution policy.Source: Lovable - ownership and hosting · Lovable - subscription plans
Commercial useDocumented: Lovable states that users own the applications, code and content they create and may modify, use commercially and host them, subject to third-party rights and open-source licences. The generated application can be self-hosted; Lovable’s editor and AI agent remain managed services and cannot be deployed in a customer VPC.Source: Lovable - ownership and hosting
Training on your dataDocumented: Free and Pro can opt out of training while Business and Enterprise are excluded by default.Source: Lovable - subscription plans
API billingDocumented: Creating a workspace-scoped Lovable API key requires a Business or Enterprise plan and workspace owner/admin role; the account email must be verified before API calls. Owners/admins on all plans may register OAuth clients, while sensitive OAuth scopes require Business/Enterprise. Current management/deployment endpoints, including deployment builds, do not consume AI build credits. AI project creation/editing uses the separate MCP server; this is not an all-API/MCP-free guarantee.Source: lovable official lov-api
Export formatsDocumented: Git sync is available on all Lovable plans, while downloading a codebase as a .zip file requires a paid plan. Code export includes source code and database migration files, but not database contents or uploaded storage files; those need separate export. A code archive is not a complete backup or a verified migration.Source: Lovable - ownership and hosting
Usage limitsDocumented: A workspace balance covers building, chat, Cloud hosting and backend, in-app AI and Managed-by-Lovable connectors. Usage-specific grants are spent first, then general credits. No available credits can pause builds and Cloud services or cause runtime AI failures. Historical scope read on 2026-09-23, not rechecked in full on 2026-10-15: Free has 5 build credits a day capped at 30 per calendar month, and Pro and Business have 5 a day with no monthly cap in that table; a workspace also carries a temporary 20 Cloud credits and 4 AI credits a month. One balance covers building, chat, Cloud backend and hosting, in-app AI and some connectors, with Build and Run shown as views. When the balance reaches zero, builds pause, runtime AI fails and Cloud services may pause, and a paused database cannot be accessed or exported.Source: Lovable - credits and usage

Official sources

The vendor pages we read for the claims on this page, what each one states, and the day we read it.

Lovable - subscription plans ↗
The plan table enables Lovable API for Business/Enterprise and code downloads for Pro and higher. API eligibility is not a complete rate or balance-inclusion contract, and the document does not define country distribution. Historical registered scope read on 2026-10-15, not rechecked in full on 2026-10-15: The Lovable subscription-plan tables explicitly price Pro and Business in USD. Pro starts at 100 monthly credits for US$25 billed monthly or US$250 billed annually; Business starts at the same allowance for US$50 monthly or US$500 annually. Annual totals are charged yearly, while credits are issued monthly. The page does not establish a complete purchase-region or account-specific checkout quote. Free and Pro can opt out of training while Business and Enterprise are excluded by default. The plan feature table lists Lovable API access on Business and Enterprise, not Free or Pro. That eligibility row does not state whether consumer subscription credits cover every API operation or whether additional API charges apply.
Read on October 15, 2026
Lovable - pricing ↗
Billing is per workspace rather than per seat and any number of members can be invited to share the credits; some regions may see a different monthly cap on daily allowances, so the workspace checkout is the reference.
Read on September 23, 2026
Lovable - credits and usage ↗
Historical registered scope from 2026-09-23; the entire statement was not re-read on 2026-10-15: Free has 5 build credits a day capped at 30 per calendar month, and Pro and Business have 5 a day with no monthly cap in that table; a workspace also carries a temporary 20 Cloud credits and 4 AI credits a month. One balance covers building, chat, Cloud backend and hosting, in-app AI and some connectors, with Build and Run shown as views. When the balance reaches zero, builds pause, runtime AI fails and Cloud services may pause, and a paused database cannot be accessed or exported. Official body read on 2026-10-15, limited to this scope: A workspace balance covers building, chat, Cloud hosting/backend, in-app AI and Managed-by-Lovable connectors. Usage-specific grants apply first, then general credits. Zero available credits can pause builds, fail runtime AI and pause Cloud; actual project costs remain untested. A workspace balance covers building, chat, Cloud hosting and backend, in-app AI and Managed-by-Lovable connectors. Usage-specific grants are spent first, then general credits. No available credits can pause builds and Cloud services or cause runtime AI failures. Historical scope read on 2026-09-23, not rechecked in full on 2026-10-15: Free has 5 build credits a day capped at 30 per calendar month, and Pro and Business have 5 a day with no monthly cap in that table; a workspace also carries a temporary 20 Cloud credits and 4 AI credits a month. One balance covers building, chat, Cloud backend and hosting, in-app AI and some connectors, with Build and Run shown as views. When the balance reaches zero, builds pause, runtime AI fails and Cloud services may pause, and a paused database cannot be accessed or exported.
Read on October 15, 2026
Lovable - billing change announcement ↗
The 13 June 2026 announcement of the move from separate Cloud and AI wallets to one credit balance, which supersedes the older wording that a subscription covered only building.
Read on September 23, 2026
Lovable - ownership and hosting ↗
Code portability, hosting and ownership options are documented, but they do not establish country-by-country access to Lovable subscriptions. Historical registered scope read on 2026-10-15, not rechecked in full on 2026-10-15: Lovable states that users own the applications, code and content they create and may modify, use commercially and host them, subject to third-party rights and open-source licences. The generated application can be self-hosted; Lovable’s editor and AI agent remain managed services and cannot be deployed in a customer VPC. Git sync is available on all Lovable plans, while downloading a codebase as a .zip file requires a paid plan. Code export includes source code and database migration files, but not database contents or uploaded storage files; those need separate export. A code archive is not a complete backup or a verified migration. New Lovable apps created from 13 May 2026 use TanStack Start, including server-side code; older applications use React and Vite. This date boundary must be retained when describing the generated framework.
Read on October 15, 2026
Lovable - GitHub integration ↗
GitHub service is available on every plan with new repositories private by default and two-way sync once connected; paid plans add a codebase download. Importing an arbitrary existing repository to start a Lovable project is not supported, and GitHub Enterprise Server is an Enterprise option that requires the Lovable public IP to reach it.
Read on September 23, 2026
Lovable - Cloud migration FAQ ↗
No one-click migration from Cloud to your own Supabase: data has to be exported and the schema rebuilt in a new project, and remix stays on Cloud. Supabase to Cloud is not supported either. Cloud locks to a region once enabled, and removing it permanently deletes the instance, so back up first.
Read on September 23, 2026
lovable official lov-api ↗
Creating a workspace-scoped Lovable API key requires a Business or Enterprise plan and workspace owner/admin role; the account email must be verified before API calls. Owners/admins on all plans may register OAuth clients, while sensitive OAuth scopes require Business/Enterprise. Current management/deployment endpoints, including deployment builds, do not consume AI build credits. AI project creation/editing uses the separate MCP server; this is not an all-API/MCP-free guarantee.
Read on October 15, 2026

Compare with other tools in Code Tools

Product	Maker	Pricing	Launched	Shared tags
Bolt.new	StackBlitz	Freemium	2024-09	App builder, Full-stack
v0	Vercel	Freemium	2023	App builder
Claude Code	Anthropic	Paid	2025-02-24	—
Devin Desktop	Cognition	Freemium	2024-11-13	—
Replit Agent	Replit	Freemium	2024-09	—
Cursor	Cursor	Freemium	2023-03	—