by StackBlitz
Built it with Bolt.new?
A prompt-driven builder from StackBlitz that generates and runs full applications entirely inside the browser, using WebContainers to execute Node without a server.
What it generates
- Flexible framework choice — React, Next.js, Svelte, Vue and others
- Runs in-browser via WebContainers rather than on a remote machine
- Optional integrations for Supabase and similar backend services
- Deployment commonly through Netlify
What it’s good at
- Genuinely fast iteration, with no environment setup and no cold start.
- Less opinionated about framework than most builders, so you are not locked to one stack.
- Produces a normal project structure that an engineer can take over without unpicking anything unusual.
What Bolt.new leaves you to build
Mostly scope rather than shortcoming — these are the boundaries of what the product sets out to do.
A backend, in many cases
Bolt is strongest at the application itself. Unless you explicitly wire up a backend service, what you have is a frontend with data held in the browser, which looks complete and persists nothing.
Anything the browser runtime cannot do
Running Node inside a browser tab is an impressive trick with real edges. Native modules, some binaries, and certain system-level operations do not work there, and code that assumed they would needs revisiting once it runs on a real server.
Production deployment on infrastructure you chose
Getting from the in-browser preview to hosting you control, with environment variables, a build pipeline, and a custom domain, is separate work.
Token efficiency at size
As a project grows, each change consumes more of the model's context, and cost per change rises while reliability falls. This is a practical ceiling rather than a bug, and it is a common reason people look for help.
Signs you’ve outgrown it
- Data disappears when the page reloads, because there is no real persistence layer.
- Each change is costing noticeably more and succeeding less often than it did.
- You need a scheduled job, a webhook receiver, or anything that runs when nobody has the app open.
- The project needs to run somewhere other than a browser tab.
What a handoff involves
Bolt.new — questions
Why does my data vanish when I refresh?
Because it was never stored anywhere. State is being held in the browser, which is normal for a prototype and is exactly the boundary where a backend becomes necessary. It is a well-defined piece of work rather than a sign anything went wrong.
Why is Bolt getting more expensive and less reliable as I go?
Larger projects mean more context per request. Cost rises, and the model has more opportunity to make an inconsistent change. Restructuring into smaller, clearer modules helps directly, and is one of the things that makes AI tools work well on a codebase again.
Last reviewed 2026-07-20. Bolt.new ships changes frequently. If something here is out of date, tell us and we will correct it — we would rather be accurate than flattering.
Not sure what your Bolt.new app needs?
A fixed-price review tells you what's actually wrong, what it would cost to fix, and whether you need us at all.