Lovable review: the fastest polished app, and a backend you can't unplug

Lovable turns a description into a running web app with a database, sign-in and hosting, and in November 2026 it's still the builder most likely to produce a first version you'd show a customer. This review compares Lovable's published plans and documentation against the same six criteria we use for every builder and coding agent. Mahmoud has built with Lovable and won its Shipped season 1 Grand Prize, so the speed and polish judgements come partly from use; the pricing and lock-in facts come from Lovable's and Supabase's own docs, linked below.

Scores

Pricing and credits, checked November 2026

Lovable charges per message, in credits, and the cost of a message depends on what it asks for. Its own examples put a small style change at 0.5 credits, adding sign-up and login at 1.2, and a landing page with generated images at 1.7. That makes Pro's 100 credits worth somewhere between 60 and 200 messages of that size, plus the 5 daily build credits Pro adds with no monthly cap.

Three details change the real cost:

• Credits roll over, but not forever. Unused monthly credits carry into the next cycle and expire two months after they were issued on monthly billing. The daily credits and the monthly Cloud, AI and connector grants don't roll over.
• The backend has its own meter. Every plan gets 20 Cloud credits and 4 AI credits a month. Beyond those, Cloud and AI usage draws on the same general credits you build with, so hosting traffic and AI features compete with your prompts for the monthly allowance. An app with real traffic or AI features costs more than its build credits suggest.
• Pro and Business scale by tier, not by seat. Both plans go from 100 to 10,000 credits a month. Business costs twice Pro at every tier; what the extra buys is SSO, role-based access, a security center, a DPA and training opt-out by default.

The Free plan changed shape in a way that matters for launches: free projects publish to invited people only, up to 10 per project. You can build and test on Free, but a public URL needs Pro.

What it builds well

Lovable is at its best on the visible part of software. A description becomes screens that look designed, with auth, a database and a hosted URL, in one sitting. Since May 13, 2026 new apps are built on TanStack Start, which runs server code, so a Lovable app is no longer only a static React front end talking to a database.

That makes it a strong fit for three jobs: an MVP to put in front of users this week, an internal tool where a polished UI helps adoption, and a working prototype to settle an argument about what to build. On Pro you can also edit the code directly, which helps when a change is quicker to make by hand than to describe.

Where it struggles

The weak spot is the one every prompt-to-app tool shares. As the app grows, each fix is another prompt into a codebase you didn't write, and the tenth fix to the same screen costs more credits than the first build did. Apps heavy in business rules, multi-step permissions, payments or integrations that must not fail quietly are where we'd expect the credit bill to climb while the app stops improving. When you see that pattern, move the repository into a coding agent such as Claude Code or Cursor and add tests before features.

Lovable Cloud: the backend question

Lovable Cloud is the built-in backend: database, auth, storage and edge functions, provisioned for you. Supabase's documentation describes it as an underlying Supabase instance that Lovable manages. That's convenient and it's why Lovable is so fast, but it comes with limits worth knowing before you start:

• The project isn't in your own Supabase account, so there's no Supabase dashboard, SQL editor, direct database URL or service key.
• Once Cloud is enabled on a project, it "cannot be disconnected or switched" to an external Supabase connection.
• The alternative is to connect a Supabase project you own from the start, which keeps the backend in your account.

If the app might become a real business, decide this on day one. For a prototype, Cloud is the right default.

Lock-in and leaving

Leaving Lovable has two halves, and they're very different.

The code leaves easily. Git sync to GitHub, GitLab or Bitbucket is on every plan, including Free, and paid plans can download a .zip. Older Vite apps deploy to any static host; TanStack Start apps need a host that runs server code.

The backend leaves by hand. Lovable's self-hosting guide says moving the PostgreSQL database alone doesn't move auth, storage, realtime or edge functions; each needs its own migration, and only managed or self-hosted Supabase is supported as a destination. Git carries the schema but not the data, so you export the database and storage files separately. Supabase's own help page confirms there's no automated transfer. None of this makes Lovable a trap, but it's a migration project, not a button.

Key facts

Alternatives

If you're still deciding whether the idea should be an app at all, run it through the decision tool first: plenty of weekend Lovable projects would have been a skill and a connector.