Built something with Bolt.new?

Bolt.new app nearly working? We finish it.

Most Bolt.new projects that land with us started as a demo that worked, grew into something a business wants to charge money for, and then ran into the parts the chat quietly skipped. We go through what it generated, keep what works, and rewrite the handful of pieces that cannot stay the way they are.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

bolt.log

still failing

What it is

Bolt at a glance

Bolt.new is an AI-driven development environment from StackBlitz, launched in 2024. A chat panel generates a React, Next.js or Astro app, installs any npm package it needs, and can ship the result to Netlify or Vercel without ever leaving the browser tab.

The trick behind it is WebContainers, which run a full Node.js toolchain inside the browser itself, so the preview you see is the real build. That makes it very good at turning a sentence into a running prototype in minutes. It is less good at being the engineer who later reads every file and asks whether it is safe to put in front of paying customers.

Type
AI-powered in-browser dev environment
First released
2024
License
Proprietary SaaS
Maintained by
StackBlitz, Inc.
Typically used for
Prototypes, landing pages, early SaaS MVPs, internal tools

The honest version

Bolt pros and cons

No technology is all upside. This is where Bolt earns its place and where it tends to cause trouble.

Where Bolt is strong

  • Build without local setupWebContainers run the whole Node toolchain inside the browser, so there is nothing to install on your laptop before the preview boots.
  • Prompt to prototype in minutesA sentence of description turns into a working page you can click through, which makes it ideal for pitching an idea or testing a layout.
  • Deploys without leaving the chatShipping to Netlify or Vercel happens from inside the Bolt.new tab, so a non-engineer can get a live URL in front of stakeholders quickly.
  • Open to the npm worldIt is not limited to a walled garden of components. Any npm package is fair game, and projects can be exported to StackBlitz or pushed to a GitHub repo when you want to own the code.

Where Bolt bites

  • Security is treated as optionalGenerated code tends to leave authentication, CORS rules and secret handling as something you were presumably going to add later.
  • Keys leak into the browserValues that belong on a server routinely end up bundled into client JavaScript, visible to anyone who opens the network tab.
  • Database and payments look like demosSupabase tables, Stripe checkout and similar integrations follow 'hello world' examples that do not survive real traffic, concurrent writes or refund flows.
  • Regeneration eats your fixesAsk it to rework a feature and the careful edits you made by hand last week can quietly disappear from the next version.
  • The chat forgets what it decidedContext windows fill up, and a convention set in the first prompt is often ignored by the twentieth, so the codebase drifts in several directions at once.
  • Deploy debugging falls on youWhen the Netlify build fails or an edge function times out, the chat is rarely the fastest way to work out why, and the logs are the ones you were trying to avoid reading.

Sound familiar?

Common Bolt problems we fix

The Bolt problems that bring people to us, and what you have once each one is fixed.

SUPABASE_SERVICE_ROLE_KEY in client bundle

Secrets ended up in the browser

API keys and service role credentials got wired into client code where any visitor can read them, usually because the chat treated environment variables as a single bucket.

Keys moved server-side and rotated

Supabase RLS: no policies on table 'orders'

The database is wide open

Row level security was never turned on, or was turned on with no policies, so one logged-in customer can read every other customer's rows.

Policies written and tested per table

Auth guard missing on /admin routes

Anyone can reach the admin pages

Login exists on the front door but the admin screens check nothing on the server, so pasting the URL is enough to get in.

Guards enforced on the server, not just the UI

Netlify deploy failed: build command missing

The deploy keeps failing

Build command, output directory or environment variables were set in the chat preview but never carried across to the hosting provider's own settings.

Pipeline that builds green on every push

App regenerated: manual edits lost

A regeneration wiped your fixes

Hand-written changes vanished because the chat rewrote whole files instead of patching them, and there was no real git history to fall back on.

Moved into a real repo with proper commits

CORS error calling /api/webhook from browser

Webhooks and third-party calls fail from the browser

Calls that should run on a server are being made from the client, so the other service refuses them or blocks the origin.

Server routes handle the outbound calls

404 on refresh

The site 404s on refresh

A single-page app shipped without the rewrite rule that sends every path back to index.html, so direct links and page reloads break.

Routing fixed at the hosting layer

Token limit reached on Bolt.new plan

The chat has run out of runway

The project has grown past what a prompt can usefully reason about in one go, and each small change now costs a full regeneration.

Handed off to engineers with a real editor

What we do

Bolt.new help, from rescue to ready-for-customers

Call us to finish one feature, or hand us the whole prototype.

Audit
A walk through what Bolt built, flagging the parts that leak keys, skip authentication or will not survive real traffic.
Harden
Server-side auth, proper secret handling, database policies and the webhooks moved off the client.
Deploy pipeline
A real git repository, preview environments and a build that passes on every push instead of only in the chat.
Finish the build
Billing that handles refunds, real user accounts, email, uploads and the quiet pieces the chat skipped.
Rework
Rewriting the handful of files that cannot stay as generated, without throwing away the parts that already work.
Managed Tech
Monitoring, backups, upgrades and engineers to call once the app is actually live.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Bolt alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Bolt questions

Something else? Call+1 737 727 7327

Can you help me finish an app I vibe-coded with Bolt.new?

Yes. That is one of the more common things we get asked to do. We start with what you already have, keep the parts that are sound, and rebuild only the pieces that would get you in trouble as soon as a real user touches them.

Is my Bolt.new app safe to put in front of real customers?

Usually not without a review first. The most common issues we find are secrets shipped in the client bundle, database tables with no row level security and admin routes that trust the browser. These are all fixable, but they are worth catching before launch rather than after.

Why do my Bolt.new deploys keep failing on Netlify?

Normally it is one of a short list: the build command or publish directory never got copied across, environment variables are only set inside the chat preview, or the generated SPA has no rewrite rule for refreshes. We read the real build log and fix the actual cause.

Can you move a Bolt.new app to a proper repo and CI/CD?

Yes. We export the project to GitHub, clean up the history, add preview deployments on every pull request, and make sure regenerations from the chat can no longer silently overwrite a week of work.

How do we add real users and billing to a Bolt.new project?

We wire in proper authentication, add server-side session checks, and connect Stripe with real webhook handling for success, failure and refund events. The database side gets row level security that reflects who owns what.

How much does Bolt.new help cost?

Estimates are free. Share the project URL or a repo and you get a price before any work starts.

Free estimate

Bolt.new project not quite there?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.