Our verdict · App builder
The pick for people who iterate in long sessions and want to see and edit the code as they go: a big monthly token allowance that rolls over, hosting on every plan, and real two-way GitHub sync. Its built-in database is convenient but can't currently be moved to Supabase later, so choose the database provider at the start.
Pick it if
- Long, iterative build sessions in the browser
- Builders who want to watch and tweak the code
- Projects that should live in GitHub from day one
Skip it if
- You need branch merges or a review flow inside the tool
- You may want to move the database later but haven't chosen Supabase at the start
- You want published database limits before you commit
Bolt, from StackBlitz, runs a full development environment in the browser and builds apps from a chat, with hosting and a database included. It differs from Lovable in two ways that matter to how you work: it meters in tokens rather than per-message credits, and its GitHub sync goes both ways. This review compares Bolt's published plans and help-center documentation against our six criteria; we haven't run a benchmark, and where Bolt's documentation is silent we say so.
Scores
- Speed to a first version5/5
Description to running, hosted app in one session, in the browser, with no local setup.
- Depth before the wall3/5
Good while the project fits in the agent's context; token use grows with project size, and branch merging happens outside Bolt.
- Backend and data3/5
A database, auth and storage appear when needed, but limits sit in account settings rather than on the pricing page.
- Ownership and exit3/5
Real two-way GitHub sync, but an existing Bolt Database can't be moved to Supabase, and full database export isn't documented.
- Pricing predictability3/5
Published token allowances with rollover; what a token buys depends on the size of your project.
- Team and production readiness3/5
Teams adds SSO and central billing; SOC 2 and audit logs are Enterprise only.
Overall 3.3/5, the plain average of six criteria. Scored by Mahmoud Halat from published specs and docs, checked Nov 1, 2026. How we score.
Pricing: what a token budget means
| Plan | Price (USD) | What you get |
|---|---|---|
| Free | $0 | 1M tokens a month, 300K a day, hosting, unlimited databases, Bolt branding |
| Pro | $25/mo | 10M tokens, no daily limit, rollover, custom domains, choice of database provider, 1M web requests a month |
| Teams | $30/member/mo | From 10M tokens per member, centralized billing, SSO, private NPM registries |
| Enterprise | Custom | Consumption pricing, SOC 2 Type II, audit logs, dedicated infrastructure |
- Billed in
- Tokens (bigger projects use more per message)
- Free tier
- 1M tokens a month, 300K daily limit, hosting with Bolt branding
Source: bolt.new/pricing, Bolt Database docs, GitHub integration docs. Prices checked Nov 1, 2026, before tax. The page offers yearly billing ("save up to 28%") without listing annual prices. Prices exclude tax.
Bolt sells tokens: the units of text the model reads and writes. Pro's 10M tokens a month is a large number, but a token budget behaves differently from a message count. Every message carries project context, so the same request costs more in a large project than in a small one. Two consequences:
- The allowance stretches furthest early. A new project burns tokens slowly; a mature one with many files burns them faster for the same size of change.
- Rollover helps people who work in bursts. Unused Pro tokens carry over, so a quiet month funds a busy one. Free has no rollover and a 300K daily cap, which is enough to evaluate Bolt, not to build with it.
The pricing page offers yearly billing ("save up to 28%") but doesn't list the annual figures, so check the toggle on the live page before you budget.
What it builds well
Bolt suits people who like to see what's happening. You watch the code change as the agent works, you can open files and edit them, and the result is hosted on every plan, with custom domains from Pro. It's also one of the few builders with a documented route to mobile: Bolt's help center lists Expo for mobile apps. For long, iterative sessions where you keep refining the same project, the token model and rollover fit better than a per-message meter.
Where it struggles
Bolt's help center is candid about a few limits. Branches can be created and switched inside Bolt, but "Bolt currently doesn't support merging branches in-app", so merges happen in GitHub. Database limits aren't on the pricing page; they sit in your account's Cloud settings. Team features are thin below Enterprise: Teams adds SSO and centralized billing, while SOC 2 Type II and audit logs are Enterprise only.
Bolt Cloud and the database
Bolt Cloud is the built-in hosting, domains and database layer. Bolt Database is created automatically when a project needs one (you can ask it not to), with auth (email and Google sign-in, password reset) and file storage buckets. The help center describes it as separate from Supabase, which you can choose instead.
The important detail is timing. On Pro and Teams you can select Supabase when you start a new project, and advanced settings let you connect Supabase or claim the database into your own Supabase account. But "existing Bolt databases can't currently be migrated to Supabase." If there's any chance the app becomes a product with its own infrastructure, make the database choice before the first prompt.
One more operational note: unpublished projects may have their database paused after six or more days of low use. Published projects aren't paused.
Lock-in and leaving
The code side is the best of the browser builders. Bolt's GitHub integration commits your changes automatically and "checks GitHub every 30 seconds for any updates made outside Bolt", pulling them in, so you can work in Bolt and in a local editor on the same repository. You can also import an existing repository as a new Bolt project. The catch is the conflict rule: if Bolt and GitHub change at nearly the same moment, Bolt keeps its own changes and overwrites the GitHub version. Don't have a teammate push to the same branch while Bolt is mid-task.
The data side is weaker. The Tables page exports row data, but a full database export isn't documented, and the Bolt Database to Supabase path doesn't exist yet.
Key facts
- Made by
- StackBlitz
- Builds
- Web apps in a full in-browser dev environment; mobile apps through Expo
- Backend
- Bolt Database created automatically when a project needs one; Supabase selectable at project start on Pro and Teams
- Code export
- Two-way GitHub sync: Bolt commits automatically and pulls outside edits every 30 seconds; import existing repos
- Lock-in
- Existing Bolt databases can't currently be migrated to Supabase; table rows export, full database export isn't documented
Alternatives
- LovableMore polished first versions and a managed backend with more features
- v0If your stack is Next.js on Vercel
- Replit AgentWhen you need a real IDE and more languages
Head-to-head: Lovable vs Bolt · Bolt vs v0
Questions people ask
How much does Bolt cost?
Free gives 1M tokens a month with a 300K daily limit. Pro is $25 a month for 10M tokens with rollover and custom domains, and Teams is $30 per member a month. Enterprise is priced by consumption. Prices before tax, checked November 1, 2026 on bolt.new/pricing.
Why does Bolt use more tokens as my project grows?
A token is a unit of text the model reads or writes. Each message to Bolt includes context from your project, so a larger codebase means more tokens per message even for a small change. Keeping projects focused and splitting large apps helps the allowance last.
Can I move a Bolt database to Supabase later?
Not currently. Bolt's help center says existing Bolt databases can't be migrated to Supabase. On Pro and Teams you can pick Supabase when you start a new project, so decide before you build if you think you'll want your own Supabase account.
Does Bolt sync with GitHub?
Yes, both ways. Bolt commits your changes automatically and checks GitHub every 30 seconds for changes made elsewhere. If both sides change at nearly the same moment, Bolt keeps its own version. You can create and switch branches in Bolt, but merges happen in GitHub.