---
title: "Lovable review: pricing, features and what to test before paying"
description: "Is Lovable worth $25 a month? Verified prices, the real cost of credits, strengths, security traps and a 7-step test plan to run before you pay."
url: "https://vibe-code.blog/en/lovable-review"
lang: "en"
author: "Thierry Gustin"
published: "2026-09-05"
updated: "2026-11-21"
---

# Lovable review: pricing, features and what to test before paying

> **Key takeaways** — Lovable is the simplest app builder for turning an idea into a web app with user accounts, a database and hosting, with nothing to install. The free plan gives 5 credits a day and Pro costs $25 a month for 100 credits plus 5 a day. Its weak spots are credits that drain fast on bigger projects and database security rules you need to check yourself.

Lovable is a browser-based app builder: you describe your app in a chat, and Lovable writes the code, creates the database, handles user sign-in and publishes the result. Our Lovable review in one sentence: it is the simplest way to go from an idea to a working web app, as long as you watch your credits and check database security yourself. Below you will find verified prices, what credits really buy and a plan to test it before you pay.

Everything here comes from the official documentation, the pricing page and published reports. To see where Lovable sits among the alternatives, keep our [comparison of the best vibe coding tools](https://vibe-code.blog/en/best-vibe-coding-tools) handy.

## What exactly is Lovable?

Lovable is a platform that generates, hosts and updates web applications from plain-language conversations. Nothing to install: it all happens on lovable.dev.

In practice, a Lovable project includes:

- **A chat** with two documented modes: Plan mode, for thinking through the steps, and Build mode, which changes the code.
- **A live preview** of the app, which you can publish to a lovable.app address or to your own domain on a paid plan.
- **Lovable Cloud**, the built-in back end: database, file storage, authentication, realtime and functions. The docs say it runs on Supabase's open-source foundation, with no separate Supabase account needed.
- **Git sync** with GitHub or GitLab, available on every plan.

On the technical side, the docs say new apps created since 13 May 2026 use TanStack Start, which runs server code, while older apps use React with Vite. You do not need to know what that means to get started, but it matters the day a developer takes over your project.

## How much does Lovable cost?

Lovable has a free plan, Pro at $25/month, Business at $50/month and custom-priced Enterprise. Prices checked on 21 November 2026 on [Lovable's official pricing page](https://lovable.dev/pricing), in US dollars before tax.

| Plan | Monthly price | Credits | What you get |
| --- | --- | --- | --- |
| Free | $0 | 5 a day, 30 max a month | Unlimited collaborators, Lovable Cloud, lovable.app addresses |
| Pro | $25 | 100 a month + 5 a day | Custom domain, no Lovable badge, credit rollover, top-ups |
| Business | $50 | 100 a month + 5 a day | Team workspace, SSO, security center, priority support |
| Enterprise | Custom | Volume-based | SCIM, audit logs, SLA, EU inference |

Before you subscribe:

- **Yearly billing** gives you the equivalent of two months free, according to the pricing page.
- **Students** can get up to 50% off Pro.
- **Pro and Business tiers** range from 100 to 10,000 credits a month, per the docs: the $25 price is the entry tier.
- **Rollover**: unused monthly credits carry over while your subscription stays active, and expire two months after they were issued on a monthly plan.
- **Top-ups** are billed separately and stay valid for 12 months.

## How many messages do 100 credits buy?

A Lovable credit does not buy a fixed number of messages: the cost depends on the mode and on how complex the request is. The docs give these examples, flagged as illustrative:

| Request | Mode | Stated cost |
| --- | --- | --- |
| A planning message | Plan | 1 credit (plus any research) |
| "Make the button gray" | Build | 0.50 credits |
| "Remove the footer" | Build | 0.90 credits |
| "Add authentication" | Build | 1.20 credits |
| "Build a landing page with images" | Build | 2.00 credits |

Using those examples as a range, Pro's 100 credits cover roughly 50 to 200 build requests, plus 5 credits a day. That is comfortable for a prototype and tight for a project you work on every evening.

Two useful details from the docs:

1. **A request you stop midway** is only charged for the work already done, and nothing if no change was made.
2. **Lovable Cloud and AI features inside your app** also use credits. Each plan includes a monthly allowance of 20 credits for Cloud and 4 for AI; beyond that, your general balance pays.

> **The looping-bug trap** — When the AI cannot fix a bug, every new attempt costs credits. After two failures, stop, switch to Plan mode and ask for a root-cause analysis before any change. The full method is in our guide on debugging when the AI goes in circles.

## What Lovable does well

Lovable shines at getting from an idea to an online app with real users. Here are its strengths, with the reasoning.

- **A back end with zero setup**: database, user accounts and storage are created from the chat. That is the step where most beginners give up on other tools.
- **Plan mode**: at 1 credit per message, it lets you validate an approach before touching code. It is the best credit saver there is.
- **Portability**: the docs say it plainly, "You own what you create." Git sync is included on every plan, and downloading the code as a zip file is available on paid plans.
- **Collaboration**: unlimited collaborators, even on the free plan.
- **Cost guardrails**: in beta, Lovable pauses to check in with you when a single message reaches 20 credits.

## Lovable's limits and traps

Lovable has three weaknesses to know about before you build a real product on it.

### Database security is still your job

In 2025, a flaw caused by insufficient Row Level Security (RLS) rules in Lovable-generated apps was tracked as CVE-2025-48757, with a severity score of 9.3 out of 10. Lovable disputes the classification, arguing that protecting application data is the customer's responsibility. The lesson: an app that works can still let anyone read everyone else's data.

Lovable offers automated security checks, but the Lovable Cloud docs themselves describe them as "Not a full audit." Read our piece on [the Supabase RLS mistake that exposes your users' data](https://vibe-code.blog/en/supabase-rls-security) and work through the [pre-launch security checklist](https://vibe-code.blog/en/vibe-coding-security).

### The back end is hard to move

The Lovable Cloud docs state there is no one-click migration: moving to your own Supabase project means exporting the database, restoring it, moving files and reconfiguring authentication and secrets. The data region cannot be changed once the back end is enabled, so pick it carefully if your users are in Europe or the UK.

### Credits are hard to predict

Because cost depends on complexity, a monthly budget is hard to estimate, and a growing project uses more per request. Our breakdown of [what a vibe-coded app really costs](https://vibe-code.blog/en/vibe-coding-cost) helps you plan ahead.

## How to test Lovable in 7 steps before paying

Here is a plan you can run on the free tier, across two or three days of daily credits.

1. **Write a 10-line mini spec**: users, three features, data to store. Our method for [writing a PRD your AI builder understands](https://vibe-code.blog/en/prd-for-ai-builders) helps.
2. **Switch to Plan mode** and paste the prompt below.
3. **Approve or fix the plan** before moving to Build mode.
4. **Test sign-in** with two different accounts.
5. **Check data isolation**: logged in as account B, try to view items created by account A. You should see nothing.
6. **Connect GitHub** and check that the code lands in your repository.
7. **Write down the credits used** at each step, shown in each response's details. Multiply to estimate your real budget.

```text
I want to build a web app for [type of app] for [users].
Version 1 only:
1. Email sign-up and login.
2. [Main feature].
3. [Second feature].
Data: [list].
Security rule: each user can only see and edit their own data. Enable row level security on every table.
Do not write any code yet: give me a numbered step-by-step plan, the list of tables and the access rules for each table.
```

For more on writing requests, read [the 5-step prompting method](https://vibe-code.blog/en/vibe-coding-prompts).

## Who is Lovable for?

Lovable suits non-technical people who want a web app with users, and suits projects with heavy server logic or fine-grained control less well.

- **Yes, if** you want to validate a SaaS idea (see [building a SaaS with vibe coding](https://vibe-code.blog/en/build-saas-vibe-coding)), show a prototype to a client or build an internal tool with login.
- **Consider Bolt** if you mostly want fast prototypes or a mobile app test: see our [Bolt.new review](https://vibe-code.blog/en/bolt-new-review).
- **Consider Replit** if your project needs scripts, scheduled jobs or a real server: see our [Replit Agent review](https://vibe-code.blog/en/replit-agent-review).
- **Consider a coding agent** once the project gets big: our Lovable vs Cursor comparison explains when to switch.

If you are still torn between the three app builders, our [Lovable vs Bolt vs Replit](https://vibe-code.blog/en/lovable-vs-bolt-vs-replit) head-to-head decides by project type. The simplest move is to open an account on [Lovable](https://lovable.dev/) and run the plan above tonight.

## Frequently asked questions

## Frequently asked questions

### Is Lovable free?

Lovable has a free plan with 5 credits a day, capped at 30 a month, plus Lovable Cloud and unlimited collaborators. That is enough to try the tool and build a small prototype. For a custom domain, removing the Lovable badge or getting 100 monthly credits, you need the Pro plan, at $25 a month as of 21 November 2026.

### How much does one Lovable message cost?

It depends on the mode and the complexity. In Plan mode, a message costs 1 credit plus any research. In Build mode, the docs give examples from 0.50 credits to change a button color up to 2 credits for a landing page with images. The credits used are shown for each response in the interface.

### Can you get the code out of a Lovable app?

Yes. Sync with GitHub or GitLab is available on every plan, including free, and downloading a zip archive is limited to paid plans. The database and stored files are exported separately. Lovable's documentation states that you own what you create and can host your app wherever you like.

### Is Lovable safe for personal data?

Lovable provides authentication and automated security checks, but the docs state those checks are not a full audit. An RLS flaw was tracked in 2025 as CVE-2025-48757. Before welcoming real users, check that every table restricts access to its owner's data and test with two accounts.

### Does Lovable use Supabase?

The built-in back end, Lovable Cloud, runs on Supabase's open-source foundation, but you do not need a Supabase account. You can also connect your own Supabase project if you want to manage it yourself. Moving from Lovable Cloud to your own Supabase is a manual migration: export the database and files, then reconfigure authentication.

## Sources

- [Lovable Pricing — Lovable](https://lovable.dev/pricing)
- [Credits and usage — Lovable Documentation](https://docs.lovable.dev/introduction/plans-and-credits)
- [Built-in backend — Lovable Documentation](https://docs.lovable.dev/features/cloud)
- [Deployment, hosting, and ownership options with Lovable — Lovable Documentation](https://docs.lovable.dev/tips-tricks/deployment-hosting-ownership)
- [Connect to Supabase — Lovable Documentation](https://docs.lovable.dev/integrations/supabase)
- [CVE-2025-48757 — Tenable](https://www.tenable.com/cve/CVE-2025-48757)

— Thierry Gustin, Formateur en intelligence artificielle (GustinAI) · November 21, 2026
