The AI-powered web development platform that generates full-stack code instantly in your browser.
Last updated
Bolt.new, from StackBlitz, is the AI builder whose identity is a runtime rather than a model. Everything distinctive about it follows from one fact: the generated application runs inside your browser tab, in a real Node environment compiled to WebAssembly, with no server executing your code and nothing installed on your machine. Deciding whether Bolt suits you is mostly deciding whether you want that trade.
The practical experience is that you describe an application and then watch it run — not a preview image, not a mocked interaction, but the actual project executing with a package manager, a dev server, and a terminal you can type into. Errors appear as errors. The AI can see them and try again. Because nothing is provisioned, the gap between having an idea and watching it fail for a real reason is measured in seconds.
This makes Bolt unusually good at a specific thing that the polished app builders are bad at: telling you quickly that an approach does not work. A tool that only shows you a rendering will let you believe a plan is fine for much longer than a tool that runs it.
The constraint is the same as the feature. A browser-based Node runtime is not a Linux machine, and the things it cannot do are specific rather than vague. Anything that depends on a native binary compiled for a host platform is out of reach. Runtimes that are not JavaScript — a Python service, a Go binary, a Ruby backend — are not what this environment is for. There is no container to run a database in, which is why persistence is handled by connecting to an external service such as Supabase rather than by something inside the tab, and why deployment goes out to a hosting provider rather than staying where you built it.
Browser support is narrower than an ordinary web application's, since the technology depends on capabilities not every browser exposes the same way; check the current requirements before you plan a workshop around it. And because the whole project lives in a tab, the session is more fragile than a checkout on disk. Connecting the project to a repository early is the difference between a bad afternoon and a lost one.
None of this is a defect. It is the cost of not installing anything, and it is a reasonable price for a JavaScript project. It is a fatal price for a polyglot one.
Do not use Bolt if you cannot read the code it produces. This is the sharpest difference from Lovable, which is built for people who will never open the source and structures its whole experience around protecting them from it. Bolt assumes a developer is in the chair and hands you the project accordingly. When something goes wrong — and on anything non-trivial it will — Bolt's recovery path is that you understand what happened.
Do not use it for a project you expect to grow large. Token consumption is driven substantially by keeping the AI in sync with your files, so the cost of each message climbs with the size of the codebase rather than with the size of your request. A one-line change in a big project is not a cheap message. The economics favour small, fast, early work, which is also where the tool is most enjoyable.
Do not use it when the environment is the point. If your application depends on a specific runtime version, a native dependency, a local database, or infrastructure you have to configure, you will spend the session fighting the sandbox instead of benefiting from it — reach for a conventional setup and an editor-first tool like Cursor instead, or a cloud environment such as Replit that gives you a real machine. And if you want UI rather than an application, v0 is aimed at that narrower job. Our comparison of Bolt, v0, and Lovable lays the three out side by side, and Cursor vs Bolt.new covers the build-versus-maintain split.
A borrowed laptop, a locked-down work machine, a tablet, a machine that does not have the right Node version. The entire setup step disappears, which is most valuable exactly when setting up would have been the largest part of the task.
Beginners see generated code execute immediately and can break it on purpose to find out what happens. The feedback loop is what teaches; a builder that only shows a finished preview hides the part worth learning from.
Hackathons and one-day spikes, where hours spent on environment configuration are hours not spent on the idea. Bolt converts that overhead into build time, and the throwaway nature of the result means the token economics never get uncomfortable.
Does this library do what the README implies, does this API shape work, will this integration behave. Building a disposable app to find out is often faster than reading, and Bolt makes disposable genuinely cheap because nothing was set up to begin with.
A working, deployed application for a client or stakeholder inside a single session. Paid plans remove Bolt branding and support a custom domain, which is the difference between showing a product and showing a tool you used.
Bolt offers Free (1M tokens/month, 300K daily limit, no credit card, but Bolt branding and no custom domain), Pro ($25/mo or ~$22.50 annually, 10M+ tokens, no daily limit, token rollover for up to two months, custom domains, no branding), and Teams ($30/member/month). The crucial pricing mechanic: Bolt is token-based and most tokens are consumed syncing your project's files to the AI — so the larger your codebase, the more each message costs, independent of how small the edit is. Heavy users on bigger projects can exhaust even the Pro allotment, so budget by project size, not just message count.
It is StackBlitz's technology for running a Node environment inside the browser using WebAssembly, and it is the reason Bolt can execute your project rather than merely render it. Your code is not being run on a remote server that has to be provisioned for you; it runs locally in the tab, which is what makes starting instant and what makes the limits specific.
Anything outside the JavaScript world, broadly. Non-JS runtimes, native binaries compiled for a host platform, containerised services, and a locally running database are not what this environment provides. Persistence comes from connecting an external service, and production hosting happens on a provider outside the tab. If your stack needs any of those, the sandbox is a wall rather than a convenience.
Because much of the consumption is keeping the AI aware of your project's files rather than processing your sentence. That means cost scales with codebase size, not edit size, and a trivial change to a mature project can be an expensive message. Budget by how big the project will get, and expect the tool to feel cheapest in exactly the early phase where it is also most fun.
It comes down to who is sitting there. Bolt hands a developer a running project and expects them to steer, debug, and take over. Lovable is designed so that a non-developer never has to look at the code and has a guided path when things go wrong. If you can read a stack trace, Bolt gives you more control; if you cannot, it gives you a problem.
Full review coming soon.