$ curl -I yourapp.com/pricingYour app works in the preview.
On your own domain, it doesn’t.
Built with Lovable, Replit, v0, Bolt, Base44?
You built something that works. Something between the app you designed and the person opening it is broken. You asked the AI, it explained the concept, and the app is still broken.
Send us the address and what you see when you open it. We look first, then quote.
Four ways this shows up
Four descriptions of the same underlying thing. If one of them is your week, you are in the right place.
Refreshing any page gives 404
The home page loads. Every other page is fine until someone reloads it, or opens a link you sent them. Then it's gone.
Nothing in the app changed. Only where it's being served from.
same app, same page, two addresses
The build says success. Half the app quietly does nothing.
It compiled, it deployed, it said success. Then a form submits into silence, or a button does nothing at all.
No error in the build. Nothing in the server log either, because it isn't failing on the server.
$ npm run build
vite v5.4.2 building for production...
transforming (1482) src/main.tsx
✓ 1482 modules transformed.dist/index.html 0.68 kB
dist/assets/index-C4tZ9v.css 28.14 kB
dist/assets/index-Bq7xKp.js 512.77 kB
✓ built in 46.05s
✓ deployed to productionAnyone can read my database
Everything the browser needs is handed to the browser, and some of that is fine by design.
The question is what sits at the other end of it, and whether anything is stopping a stranger from using it.
The console says Unexpected token '<' and the code looks fine
It is fine. What arrived was not the file the browser asked for.
Until that is fixed the page will not start, however correct the code is.
How it goes
We look before we quote. Never the other way round.
You send it
The address of a page that breaks, and one sentence about what happens when you open it.
We reproduce it
We open it ourselves and make the failure happen, then send the scope and one fixed price.
We fix it, you check it
On your domain, on your phone. You keep the code and a written list of what changed.
What it costs
Not a price list. Enough to know whether this is worth a message, which is the only thing a range is good for.
What we don’t do
Worth reading before you write to us. It is a short list and we keep to it.
$ curl -sI yourapp.com/pricing | head -1Send us the app
You don’t need to send us any code to start, and a private repository is not a problem. The address of the page that breaks is enough, and the first look is free.
Prefer to read more first? The measurements are the fastest way to judge whether we know what we are talking about.