Bolt review: fast prototypes and web apps from a conversation
Quick from idea to hosted prototype, with code synced to GitHub. Token costs and a database that cannot yet be migrated make it a weaker base for a long-lived company system.
Contents
| Type | AI app builder |
|---|---|
| Pricing | Published |
| Website | bolt.new |
Bolt builds apps, websites, slides and prototypes by chat, and can start from a Figma file, a GitHub repository or a template1.
Best for: Fast prototypes and front-end-heavy web apps, often starting from a Figma design or an existing GitHub repository.
Not the right fit for: Long-lived internal systems whose data may later need to move, or teams that need SSO and audit logs below Enterprise.
What Bolt builds
Each Bolt project can have a built-in database, created automatically, with authentication by email or Google and file storage; hosting supports custom domains2. Code can sync two ways with GitHub, which Bolt checks every 30 seconds; only the project owner can manage the connection, and disconnecting it is permanent3.
Bolt describes its own engine in strong terms: it routes each task to a suitable model, tests and refactors automatically, and, by its own account, makes 98% fewer errors1. Those are vendor claims; we found no named customer results to check them against.
How tokens work
Bolt bills AI work in tokens, and its help centre explains that most token use comes from reading, understanding and syncing the project's files. Larger projects therefore cost more per message. Unused monthly tokens stay valid for two months4. For a company system that grows over years, that means the cost of each change rises with the system.
The database has a second constraint. Supabase can be chosen at the start of a project on Pro and Teams, but there is currently no supported way to migrate an existing Bolt database to Supabase2.
Strengths and limits
Strengths
- Quick from idea to a working, hosted prototype, with custom domains on Pro.
- Two-way GitHub sync keeps a copy of the code outside Bolt.
- Can start from a Figma file, a GitHub repository or a template.
Limits
- Token use grows with the size of the project, so mature apps cost more per change.
- There is currently no supported way to migrate an existing Bolt database to Supabase.
- SSO, audit logs and data-retention policies are Enterprise features.
- Databases of unpublished projects may pause after six or more days of low use.
Choose another option if: The app will hold the company’s operating records for years. Retool, Softr or OpenLazarus are built for that lifespan.
Pricing
Published: Pro $25 a month billed monthly (from 10M tokens); Teams $30 per member a month. Enterprise on request.
Questions to ask before building on Bolt
- Should this project use Supabase from the start, given that the built-in database cannot be migrated later?
- How many tokens does a typical change use once the project is large?
- Do we need Enterprise for SSO and audit logs?
- Who owns the GitHub connection, and what happens if that person leaves?
See how Bolt compares with the other builders in the main ranking.
Sources
- Bolt AI builder: websites, apps and prototypes. Bolt. Accessed 8 Nov 2026.
- Add and manage a built-in database in your Bolt project. Bolt Help Center. Accessed 8 Nov 2026.
- GitHub integration. Bolt Help Center. Accessed 8 Nov 2026.
- Tokens. Bolt Help Center. Accessed 8 Nov 2026.
- Plans & pricing. Bolt. Accessed 8 Nov 2026.