$ wc -l app/**/*.tsx | sort -n | tail -1Built with v0
v0 doesn't have the 404 problem. It has the other one.
v0 produces Next.js, which routes on the server. The failure that defines the other builders barely exists here — so this page is about what actually goes wrong instead.
Send the address and one sentence about what you are trying to change. With v0 the useful question is usually about the next change, not the last deploy.
What we measured on v0
Not the routing. The size of what you now own.
set output: 'export'. That is the only configuration where a Next.js app inherits single-page routing — so the 404 story does not apply to the other 95.
100 public v0 repositories, read 2026-08-03
have a single test. This is the lowest figure we measured anywhere.
100 public v0 repositories, read 2026-08-03
have a source file over 20 KB, with no data layer underneath it: repositories/ and domain/ appear zero times in the whole sample.
100 public v0 repositories, read 2026-08-03
Straight about what we know
What is true
Deployment is the least of it. Nobody has committed a key (0 of 100) and refreshing works. What you have instead is a codebase that will resist its first serious change: large files, no tests, and no separation between the interface and the data it reads.
What we won’t claim
Databases in v0 projects are not Supabase, so our migration and policy checks do not transfer. We have no measurement of how v0 apps handle data at all — and rather than guess by analogy with Lovable, we are saying that plainly.
Read the measurements and judge how much of it looks like your app.
What breaks first on v0
Not deployment. These are the things that surface on the second or third change, not on the first day.
- 01
“I want to move it off v0 and I don't know what I'm moving.”
- 02
“Every change breaks something somewhere else.”
- 03
“There are no tests, so I can't tell if a change is safe.”
- 04
“The whole page is one file and I've stopped editing it.”
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.