$ curl -I yourapp.com/pricingBuilt with Lovable
It works in the preview. On your own domain it doesn't.
Lovable builds a Vite single-page app. The preview serves it correctly; a plain host does not, and nothing in the project tells it how.
Send the address of a page that 404s. We will tell you whether it is the rewrite rule, the asset path, or both — and which of the three you can do yourself in ten minutes.
What we measured on Lovable
Keys in the repository, and routing that stops at the front door.
contain no rewrite rule at all — nothing that answers a request for an inner route.
100 public Lovable repositories, read 2026-08-03
have a committed .env. Every one of them already had a .gitignore.
100 public Lovable repositories, read 2026-08-03
switch off type checking somewhere with `any` — a second pass over a wider sample than the rest of this page.
158 public Lovable repositories, read 2026-08-03
Straight about what we know
What is true
This is the builder we have measured most: 100 repositories for structure, 158 for the contents of the code. Both passes are reproducible from published scripts, and the article says which numbers we threw away.
What we won’t claim
We cannot see your database from your code. Three quarters of these projects have no migrations at all, which means the schema was clicked together in a panel and left no trace in the repository. Whether your tables are protected is a question about your live app, and we do not test that without being asked.
Read the measurements and judge how much of it looks like your app.
What breaks first on Lovable
In the order people run into them. The first two are configuration and the last two are not.
- 01
“Refreshing any page but the home page gives 404.”
- 02
“Someone told me my API key is visible in the page source.”
- 03
“It works on the Lovable domain and breaks on mine.”
- 04
“The console says Unexpected token '<' and the code looks fine.”
Every job runs the same way: we look from outside first, work on our own machine, and the result goes onto your infrastructure with you watching. How we work sets out what access is needed at each stage and what we never do.