When is Bolt a useful place to start?
Try Bolt when you want to go from a written idea to a web app you can actually open, without setting up a programming workspace on your computer. It can also work with an existing JavaScript project, which is useful if you’ve already started building.
An example: you run a community workshop and want people to reserve one of 12 seats. You can ask for a signup page, try it in the browser, and decide later whether you need accounts or waitlist emails. If you already have a site whose behind-the-scenes code runs in Python or PHP, Bolt doesn’t run that part. Find out how the existing site works before you try to move it.
Can you tell if Bolt built a real signup or just the page?
Ask Bolt to reserve a seat and show a confirmation only after it’s saved. Start with 12 seats and use pretend names. Reload the page, then open it in another browser window: the count should still show 11 seats.
If the number jumps back to 12, ask where the reservation is being saved and whether another visitor can see the updated count. Once it works, try two people claiming the last seat. That reveals a different problem than an empty form does.
Use Chrome or Edge on a computer if you want to edit the code. Safari on a Mac can show Code view in read-only mode. You can chat, preview and publish from a phone; the mobile interface doesn’t include Code view, visual editing or the database tools.
Can Bolt remember reservations and give organizers private access?
Bolt Database can keep records, sign people in and store uploaded files. You can use those features without signing up for another database provider, but you still need to tell Bolt who gets access to what.
For the workshop, attendees might only need to reserve and cancel their own seats. The organizer needs to see the whole list. If Bolt adds an organizer page, try opening its exact address as a regular attendee. The app should refuse to return the list, even if the link was shared by accident.
What does Bolt publish, and what can take the site offline?
Publish when the app is ready to go online. Bolt provides a bolt.host address; attaching your own address requires a paid plan. Edits made afterward need another publish before visitors receive them.
Open that address outside the editor and check what visitors see. Test a signup there only if you’ve confirmed it uses test records and can’t send real messages. Otherwise, try the signup on an isolated copy. Bolt says that reaching its hosting limit can take the site offline until the allowance resets or an eligible account raises it. A balance for AI edits doesn’t tell you whether you still have room for visitors.
What changes Bolt’s bill as a project grows?
Start by checking building tokens and hosting usage separately. Tokens measure pieces of text and code Bolt processes. Asking it to fix one sentence in a big project can use more than you expect if it reads many files to do it.
Check the usage after a few real edits. If a project will sit unused for a while, also check expiry and active-subscription requirements before counting on rolled-over paid tokens.
The figures are from Bolt’s listed plans. Check the current plan for your account before paying.
| Cost | What it covers | What to check |
|---|---|---|
| Build tokens | Bolt reading files and generating changes. | Free: up to 300,000 tokens a day within 1 million per month. Pro starts at US$25/month for 10 million tokens per month with no daily cap. |
| Live hosting | Keeping the published app available to visitors. | Usage limits, what happens at the limit and whether you can raise it. |
| Separate services | Anything Bolt doesn’t provide under your plan. | Domain renewal and any outside mail, payments or storage bill. |
On a small screen, scroll the table sideways to read every column.
What would a Bolt restore leave untouched?
Bolt’s version history can bring back project code. It doesn’t restore the current Bolt or connected Supabase database. If an edit deleted reservations, restoring yesterday’s code can leave the same empty list.
Before changing anything that can remove records, find out how you’d recover them. Keep a copy of the code that works with those records. Bolt’s database security checks can help find issues with database rules, but also try the actions a visitor shouldn’t be able to take, such as opening the attendee list.
Can you take the whole app with you if you leave Bolt?
You can download the project files from a desktop browser or keep the code on GitHub, a service that tracks project files and their changes. For a working move, you also need to transfer or reconnect saved records, sign-in, uploaded files and private settings.
Bolt documents a way for the owner of a Supabase group account to claim an existing Bolt Database from a Pro or Teams project. Claiming into Supabase Free turns off checks for passwords known to have leaked; keeping that protection requires Supabase Pro or higher. Bolt’s general database and Supabase pages don’t fully agree on migration guidance, so confirm the Claim option for your project. Connecting a fresh database won’t copy your records.
Do you need a phone app or a website that works on phones?
Use a normal web project if people just need to open the signup from a link on their phone. If you need people to install it from an app store, start with Bolt’s Expo route. Expo is a toolkit for building mobile apps.
Tell Bolt which you need at the beginning. An app-store version adds device testing and store submission. A successful browser preview doesn’t check either of those steps.
Where can you learn the next steps?
- Check your app before inviting usersWork through access, failed actions and recovery checks before a release.