$ curl -I yourapp.com/pricingBuilt with Bolt
It works in the preview. On your own domain it doesn't.
Bolt builds a Vite single-page app, so the delivery failures are mechanically identical to Lovable's and the repair is the same work.
Send the address of the page that breaks. We have no Bolt sample, so we will tell you what we find rather than what we expect.
Straight about what we know
What is true
A Vite app is built once and then served as static files. Whoever generated it, the browser routing, the build-time environment variables and the missing rewrite rule behave the same way, and so does fixing them.
What we won’t claim
We have no Bolt sample and will not print a percentage. We tried: the obvious structural marker, .bolt/config.json, appeared in 0 of 30 candidates, and GitHub's code search does not index files beginning with a dot at all. The one README phrase that does match returns 255 repositories — almost all of them hackathon entries, which is a sample of contest winners, not of users.
Read the measurements and judge how much of it looks like your app.
What breaks first on Bolt
The same four as any Vite single-page app, because that is what Bolt produces.
- 01
“Refreshing any page but the home page gives 404.”
- 02
“The build says success. Half the app quietly does nothing.”
- 03
“It works on the Bolt preview and breaks on my domain.”
- 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.