Skip to main content
App rescue · Bolt.new

Your Bolt.new app works in the preview and breaks everywhere else

Bolt is very good at getting you to something that runs. It is not trying to get you to something that survives real users, real data and a real deploy. That gap is where almost every Bolt rescue starts.

What actually breaks

The four failures we see most in Bolt.new builds

These are specific to Bolt.new. A rescue starts by working out which of them you have.
01

Supabase row level security left off

The single most common and most serious one. Industry reporting puts roughly 70% of Lovable and Bolt apps on Supabase shipping with RLS disabled, which means any signed-in user can read, modify or delete any other user's records. It looks completely fine until someone looks.
02

Environment variables that only exist in the preview

Keys hardcoded during generation, or set in the Bolt environment and never carried into the deploy target. The build succeeds and the app fails on first real request.
03

Auth redirect loops after deploying to a custom domain

Callback URLs still pointing at the preview host, so sign-in bounces forever. Fixable in minutes once you know where to look, and maddening if you do not.
04

Regressions after a prompt-fix

You ask the model to fix one bug, it rewrites a file it should not have touched, and something unrelated breaks. This is the fix-and-break cycle, and it is why credit spend keeps rising while the app gets worse.

What we do

What a rescue includes

Scoped after the audit, so you see the plan and the price before anything is touched.
Full RLS policy audit on every table, with policies written and tested
Secrets moved out of the codebase and into the deploy environment
Auth callback and redirect URLs corrected for your real domain
A working deploy pipeline you can run yourself
Error handling and logging so the next failure is visible, not silent

The first look is free

A written audit within 24 hours

Send the live link or the repository. You get back what is salvageable, what is not, and what it would cost to reach production — yours to keep whether or not you hire us.

Book the free audit

Book the audit

Pick a time and tell us what broke

Twenty minutes, free, and you get the written findings within 24 hours whether or not you hire us.

Loading available times…

FAQ

Bolt.new rescue questions

Can you fix my Bolt app or do you have to rebuild it?+
Usually fix. Most Bolt apps have sound intent and unsafe execution — the data model is roughly right and the security, deployment and error handling are missing. Rebuilds are for cases where the core structure cannot support what you actually need. The audit tells you which one you are, honestly, before you spend anything.
Is my Supabase data actually exposed right now?+
Check whether row level security is enabled on your tables. If it is off, then yes — any authenticated user can query any row. This is the first thing we look at, and it is the fix we most often deliver within a day.
What does the free audit actually include?+
We look at the real thing — the live app or the repository, not a description of it — and send back a written assessment within 24 hours: what is salvageable, what is not, what it would cost to get to production, and what we would do first. It is yours to keep whether or not you hire us.
Do I own the code after you fix it?+
Yes. You own the repository, the infrastructure and every account it runs on, with documentation and a handover. That is true of a rescue exactly as it is of a build.

Other tools

We rescue builds from all of these

Send us a Bolt.new app and we will tell you what is wrong with it

No obligation, no deck. If it is not worth rescuing we will say so, and tell you what we would do instead.
Get the free audit