What is Lovable?
By Mari Luukkainen · 10 min read · Last updated
On this page
- What does Lovable do?
- Who is Lovable for?
- How does a first Lovable session go?
- Is Lovable free? Prices and limits (checked 4 November 2026)
- What went wrong with Lovable security?
- Where else does Lovable break?
- Who owns the code, and how do you leave Lovable?
- A one-hour test you run before paying
- What are the alternatives to Lovable?
- Frequently asked questions
Lovable is an AI app builder that runs in your browser. You describe a web app in a chat, Lovable writes the code, shows a live preview next to the chat and publishes it to a lovable.app address. Its built-in backend, Lovable Cloud, adds a database, user logins and file storage. Lovable has a free plan.
I have not used Lovable. I build in Cursor and Claude Code. Everything below comes from Lovable's own documentation and pricing, checked on 4 November 2026, and from public incident records, each linked where it is used. The test near the end is a small app you build yourself to judge it.
Ask AI about this pageChatGPTClaudePerplexityGoogle AI ModeGrok
What does Lovable do?
Lovable calls itself "a full-stack AI development platform for building, iterating on, and deploying web applications using natural language" (docs). In practice a project has three parts:
| Part | What it is | Source |
|---|---|---|
| The editor | Chat on the left, live preview on the right. Build mode writes code, Plan mode writes a plan you approve first, Chat mode discusses without changing code | Quick start, Plan mode |
| The code | New apps created from 13 May 2026 use TanStack Start, which renders pages on the server. Older apps use React and Vite and build to static files | Ownership docs |
| Lovable Cloud | The built-in backend: database, authentication, storage, realtime and edge functions. It "utilizes Supabase's open-source foundation" | Cloud docs |
Every change is saved as a version you can restore. Git sync with GitHub, GitLab or Bitbucket is available on every plan, including Free (plans).
Who is Lovable for?
Based on what the docs describe, Lovable is good for:
- Founders and marketers who want a working web app or landing page without installing anything.
- Prototypes you want to show people this week, on a real URL.
- Apps that need logins and saved data but no unusual infrastructure, because Cloud sets up the backend from the chat.
It is a weaker fit for:
- Native phone apps. Lovable builds web apps.
- Teams that need the editor itself on their own servers. The docs say the Lovable platform "cannot be self-hosted or deployed inside a customer VPC" (ownership docs).
- People who want to learn to code. On the Free plan you cannot edit the code at all, and on paid plans the chat stays the main way to work.
How does a first Lovable session go?
Lovable's quick start says a first app takes about ten minutes of hands-on time (quick start). These are its steps, with prompts you can paste.
- Sign up at lovable.dev with email, Google, GitHub or Apple. You land on the Free plan.
- Type the first prompt below into the box with Build selected. Leave out logins and the database for now.
- Wait a few minutes while the first version builds. The preview appears on the right.
- Click every button in the preview and switch to the mobile view.
- Ask for one change at a time. For text and small visual changes, select the element in the preview and edit it directly.
- Click Publish, pick the lovable.app address and publish again. The live site is a snapshot: later changes only go live when you click Publish changes.
- Connect Git sync to GitHub from the project settings, so a copy of the code lives in a repository you control from day one.
Build a website for Northside Bike Repair, a small bicycle repair shop.
Pages: home with three services and prices, a "How it works" section, opening hours, and a contact form with name, email, bike type and a message.
Use realistic sample content. Mobile first, simple design, no gradients.
No login or database yet.Add a "Today's wait time" line under the opening hours that I can edit later. Do not change any other section.When the site works, add the backend in its own step. This prompt asks for the access rules explicitly, which matters for the incidents described below:
Add customer accounts with email and password.
Logged-in customers can book a repair slot: date, time and bike type. Save bookings in the database.
Each customer must only see and change their own bookings. The shop owner account sees all bookings on /admin.
Show me the row level security policies you created, in plain language, table by table.Before publishing the version with data, open the Security view and run the Deep scan. The Quick scan runs on its own when you open the publish dialog, but the Deep scan, which reviews the app's code and permissions, only runs when you start it (security docs).
Is Lovable free? Prices and limits (checked 4 November 2026)
Yes, there is a Free plan. It gives 5 build credits a day, up to 30 a month, so in practice you get daily credits for the first six days of a month. It also includes a monthly grant of 20 Cloud credits and 4 AI credits, and publishing to a lovable.app address is free on every plan (plans, quick start).
| Plan | Price | What you get | Source |
|---|---|---|---|
| Free | $0 | 5 build credits a day (30 a month), 20 Cloud and 4 AI credits a month, Git sync. No code editing, no code download, no custom domain, "Edit with Lovable" badge stays | Plans |
| Pro | From $25 a month for 100 credits ($250 a year), up to $2,250 a month for 10,000 | Plus the 5 daily credits without a monthly cap, code editing and download, custom domains, badge removal, credit rollover and top-ups | Plans |
| Business | From $50 a month for 100 credits ($500 a year), up to $4,300 a month for 10,000 | Pro features plus SSO, role-based access, security center, data excluded from AI training by default | Plans |
| Enterprise | By contract | No daily or monthly grants; audit logs, SCIM, scheduled security scans | Plans |
Annual billing gives two months free. Monthly plan credits expire two months after they are issued (pricing). Students and teachers get 50% off Pro with 100 credits, billed monthly, for up to 12 months.
Credits pay for more than building. Hosting and the built-in backend use run credits: database work, AI calls, file storage, traffic and compute. The 20-credit Cloud grant and 4-credit AI grant cover the first part each month, and Lovable labels both grants a "temporary offering, subject to change" (project usage). A live app with users costs credits even in months when you do not build anything.
What went wrong with Lovable security?
Two incidents are on the public record.
CVE-2025-48757: missing row level security (2025)
On 20 March 2025 Matt Palmer found that apps built with Lovable were exposing their Supabase databases. He scanned 1,645 Lovable projects and found 303 vulnerable endpoints across 170 of them, about 10%. Exposed data included names, phone numbers, subscriptions, API keys and payment details. He reported it to Lovable on 21 March and published on 29 May 2025 (Palmer's statement).
The NVD lists it as CVE-2025-48757, CVSS 9.3: "An insufficient database Row-Level Security policy in Lovable through 2025-04-15 allows remote unauthenticated attackers to read or write to arbitrary database tables of generated sites." Lovable disputes the CVE and says each customer is responsible for their own project's security (NVD).
Public project code and chats (2026)
On 22 April 2026 Lovable wrote that between 3 February and 20 April 2026, "public project chat history and source code could potentially be accessed by any Lovable user provided they had a project link." It shipped a fix within two hours of the report, said private projects and Lovable Cloud were not affected, and admitted that "Our first public response was dismissive" (Lovable).
What to take from both: keep projects private, never paste API keys into the chat, and test your access rules yourself. Lovable's docs say its scans "do not replace a thorough security review" (security docs).
Where else does Lovable break?
- The agent changes your database without asking. In Cloud's backend permissions, "Modify database" (schema and policy changes) defaults to Always allow. You can switch it to Ask each time in the settings (Cloud docs).
- Fix loops cost credits. Each attempt to fix a bug is a build message. Describe the symptom precisely, and roll back to a working version instead of asking for the fifth fix.
- Your work may train models. The plan comparison lists "Workspace data excluded from AI model training by default" only on Business and Enterprise. On Free and Pro it says "Opt out per account" (plans).
- Data is not in the code export. Git sync and the zip contain source files and database migration files, not the rows or uploaded files (ownership docs).
Who owns the code, and how do you leave Lovable?
Lovable's docs say "Your apps, code, and content you create with Lovable are yours" and that the platform is "intentionally built so that you are never locked in" (ownership docs). That is a vendor claim, and you can check it in your first week. The code moves easily. The backend is the harder part: if you move Lovable Cloud, the supported destinations are managed Supabase and self-hosted Supabase. Moving to plain PostgreSQL or another provider means building authentication, storage and functions yourself, and Lovable does not support it.
- Connect Git sync to a GitHub repository (all plans). The zip download needs a paid plan.
- Clone the repository and run it locally. For TanStack Start apps you need a host that runs server code, not only static files.
- Export the database and download storage files separately (database export).
- Create your own Supabase project, import the data and point the app's environment variables at it.
- Replace anything that still calls Lovable: AI features and app connectors keep billing your Lovable credits until you do (external hosting).
- Open the repository in an editor or coding agent and continue from there.
This project was built in Lovable. Do not change anything yet.
List every place the code calls a Lovable service, Supabase, or an environment variable, with the file and line.
Then tell me what I need to replace or configure to run it with my own Supabase project and my own hosting.A one-hour test you run before paying
I designed this test and have not run it. It checks the three things that went wrong for other people: access rules, exports and cost.
Build a lunch poll for a small office.
Anyone can sign up with email and password. A logged-in user can create a poll with a question and up to five options, share a link, and vote once per poll.
Users see results only for polls they created or voted in. Nobody can see who voted for what, except the poll creator.
Mobile first, plain design.- Make two accounts in two browsers. Can account B open account A's poll results without voting?
- Open the published app in a private window, logged out. Does any poll data load?
- Ask Lovable to list the row level security policies. Do they match the rules in the prompt?
- Run the Deep scan. Note what it finds that you did not.
- Connect Git sync and check that the repository has the code and the migration files.
- Check how many credits the build and the fixes used.
If step 1 or 2 fails, the app is not ready for real users, whatever the scan says.
What are the alternatives to Lovable?
| If you want | Look at | Read |
|---|---|---|
| A builder with a full online workspace, shell and mobile apps | Replit | Replit AI app builder |
| A builder that hides more of the code, owned by Wix | Base44 | [Base44 AI app builder](/base44-ai-app-builder) |
| Other browser builders compared side by side | Bolt.new, v0, Bubble | Best AI app builders |
| To work on the exported code on your own computer | Cursor, Claude Code, Copilot | What is Cursor, best vibe coding tools |
Frequently asked questions
Can I use my own Supabase project instead of Lovable Cloud?
Yes. Lovable has a Supabase integration that connects a Supabase project you own, as an alternative to the built-in backend.
Can I write prompts in a language other than English?
Yes. Lovable's quick start says you can describe what you want in plain language, in any language.
Can I bring a project from Bolt, Replit or v0 into Lovable?
Yes. Lovable documents imports from Replit, Manus, Bolt, Base44, v0 or any ZIP of code. It migrates the code and moves the database and users to Lovable's built-in backend.
Is there a Lovable desktop or mobile app?
Yes, both. Lovable's docs also list Slack and Telegram as places where you can chat with it.
What happens to my published app if I cancel Pro?
The workspace moves to Free at the end of the billing period, and published apps stay live. Unused monthly and rollover credits from the paid plan are frozen while you are on Free; purchased top-ups still work. Lovable may unpublish an app with no visits, no owner login and no custom domain for 12 months, and it emails you first.
Next guideReplit AI app builder →