Teardown: How Bolt.new Works Under the Hood
Bolt.new generates full-stack apps in the browser. We dug into its architecture, WebContainer runtime, and where it hits limits.
Bolt.new from StackBlitz is one of the more technically impressive AI products we've seen. It runs a full Node.js environment in the browser using WebContainers. That alone is worth understanding.
The WebContainer layer
The key innovation isn't the AI — it's the runtime. WebContainers let Bolt run npm, Node.js, and a dev server entirely in the browser. No remote server, no SSH tunnel, no cloud VM. Everything executes client-side.
The AI layer
On top of the runtime, Bolt uses an LLM to generate project files, install dependencies, and fix errors. The AI sees the full file system and terminal output, creating a tight feedback loop.
What works well
For greenfield projects, the experience is remarkable. You describe what you want, and a working app appears in your browser in under a minute. The AI can read error output and self-correct, which handles most common issues.
Where it breaks
Complex dependency trees sometimes fail in the WebContainer environment. Native Node modules don't work. And once you need to customize beyond what the AI scaffolded, you're editing code in a browser IDE that's functional but not as capable as a local editor.
The real value
Bolt is best understood as a rapid prototyping environment, not a development platform. Use it to test ideas, generate starting points, then export to a proper development setup.