Bolt.new rescue
Bolt.new app stopped working? We'll stabilise and ship it.
If Bolt.new built your app and then it stopped working — after you added auth, when you tried to run it anywhere but the browser, or once the project got big enough that edits started landing half-finished — AI Cubed audits the project in two business days, gets it running in a real environment, and ships it to a host you own. Most Bolt rescues take two to four weeks.
AI Cubed
September 9, 2026
Bolt is unusually good at the first hour. It's also unusual in that it runs your app inside the browser, and a lot of what breaks later is the difference between that environment and a real one.
audit, including a local run
most Bolt rescues
not the browser sandbox
Sounds familiar?
- "It worked perfectly until I connected Supabase auth. Now sign-in loops forever."
- "I downloaded the project and it won't install or run on my laptop."
- "Bolt says it updated the file, but half the file is missing."
- "The deploy button worked once. Now the deployed version is weeks behind."
- "My .env is in the project. I think that means everyone who has the export has my keys."
- "Every change costs tokens and the app is getting worse, not better."
What breaks in Bolt.new apps specifically — and what we do
| What breaks | Why it happens with Bolt | What we do |
|---|---|---|
| Runs in Bolt, fails locally or on a host | WebContainers emulate Node in the browser. Some packages behave differently or aren't supported; the project was never run in a real Node environment. | Get it running from the repo on a real machine, pin Node and package versions, replace or shim packages that only worked in the sandbox. |
| Auth loops or fails after adding Supabase | Redirect and site URLs point at the WebContainer preview URL, which changes; email confirmation and OAuth callbacks were never configured for a stable domain. | Configure Supabase auth per environment with stable URLs, set OAuth callbacks, test magic link and password reset on the real domain. |
| Secrets in the project | Bolt keeps `.env` inside the project, so exports, shares and GitHub pushes carry the keys. | Rotate every key, move secrets to the host's environment settings, `.gitignore` the file, purge history if pushed. |
| Truncated or half-applied edits | Large projects exceed the model's output limits; files get cut off or only partly rewritten. | Diff against the last working state, repair truncated files, and move to a branch-and-review workflow so no edit lands unchecked. |
| Deploy drift | One-click deploy happened once; later changes were never redeployed, or were deployed without the right environment variables. | Repo-connected deploys to a host you control with environment variables per environment and preview URLs per branch. |
| Database schema only in Supabase | Tables created through the integration; no migrations in the repo. | Capture the real schema as versioned migrations; run them on deploy. |
| Performance and size | Everything in a few enormous files because that's how the sandbox grew it. | Split by responsibility, remove dead code, index the database, paginate lists. |
How we work on a Bolt project
- Audit — two business days. Export or GitHub access, plus Supabase access if used. We run the project in a real environment as part of the audit, because that's where most Bolt problems appear. You get a written report and a fixed quote.
- Stabilise — first week. Runs locally, secrets rotated and moved, auth configured properly, truncated files repaired.
- Complete — weeks two to four. Migrations, error handling, tests on the money paths, a real deploy pipeline, the features that never quite worked.
- Hand over — repo, hosting and domain in your name, with a runbook. Bolt can stay connected for new features if you want it.
Fix or rebuild a Bolt app?
| Signal | Fix | Rebuild |
|---|---|---|
| Runs outside Bolt after setup | Yes, with configuration | Depends on sandbox-only behaviour throughout |
| Framework | Vite/React, Next, Astro or similar — mainstream | Unusual or mixed frameworks |
| File integrity | A few truncated files | Widespread truncation; no last-known-good state |
| Data | Supabase with a recoverable schema | No stable schema; data model changed repeatedly |
How long and how pricing works
Audit in two business days; most Bolt rescues live in two to four weeks. Fixed-price audit, fixed quote for the rescue, no hourly meter. If the honest answer is a rebuild, you hear it on day two with a phased plan.
Frequently asked questions
Related
Start here
See where your operation is losing time.
Twenty minutes with an operator, not a salesperson. We'll name the one bottleneck costing you the most — and tell you whether it's worth fixing with software at all.
Book your free 20-minute consult→20 minutes · video call · no preparation needed