Bolt.new Guide: Vibe Coding Platform, Workflows, and Limits

Bolt puts an AI agent, editable code, a terminal, and a live preview in one browser workspace. That sounds simple until the project needs a database, a payment flow, a mobile release, or a life outside Bolt. The useful question is not whether Bolt can draw the first screen, but where its convenient path ends.

Product details and prices in this guide were checked against Bolt's official documentation and pricing pages on July 28, 2026. Treat the figures as a dated purchasing snapshot, because token allowances, agents, and included services can change.

What Bolt Builds

Bolt describes itself as a browser-based environment for websites, web apps, and mobile apps. Its workspace can create project files, install JavaScript packages, run development commands, and show the result. The code remains visible, so a user can inspect a file or edit it directly instead of relying only on chat.

The supported backend boundary matters. Bolt's browser-support documentation says the runtime supports JavaScript backends, not PHP or Python backends. A prompt can still produce a JavaScript application that calls a Python service hosted elsewhere, but Bolt is not the place where that Python service runs.

Bolt Cloud brings managed databases, hosting, and domains into the same product. Integrations add paths to GitHub, Stripe, Expo, and other services. Those connections shorten setup, but each introduces an account, permission set, billing owner, and recovery path that should be recorded before launch.

Project Need	Bolt Path	Check First
Marketing site	Web project and hosting	Forms, analytics, domain owner
Account-based app	JavaScript app and database	Roles, recovery, data export
Native mobile app	Expo project	Store accounts and review
Python service	External API only	Separate host and deployment

How the Workspace Fits Together

The prompt is only one control surface. Bolt also exposes the files, preview, and development environment created by the agent. A beginner does not need to understand every file, but should know which page is being changed, where errors appear, and which action restores a working state.

Bolt's agent documentation currently lists Standard and Max. Standard is available on Free, while Max requires a paid plan. Bolt says it handles underlying model selection, so a project should name the agent choice rather than claiming a fixed model.

Start by asking for one screen and one complete user action. Confirm that the preview matches the request, then inspect the changed files. Adding authentication, payments, external APIs, and a complex dashboard in the first prompt makes it harder to identify which layer failed.

When the preview looks correct, test the behavior that changes data. Refresh the page, sign out and back in, use an invalid value, and repeat the action from another account if roles are involved. A polished screen does not prove that data access or error handling is correct.

Planning Before Building

Plan Mode lets the agent examine a request and propose an implementation without making code changes. Bolt's documentation notes one exception: on a new project, the first Plan Mode request creates a basic structure before planning. That distinction matters if the repository must remain untouched during an initial review.

A useful plan names the screens, user roles, stored data, external services, and acceptance checks. It should also identify decisions that require a human owner, such as whether deleting an account removes records, who can issue refunds, or what happens when an integration is unavailable.

Non-coders should reject plans that hide important behavior behind phrases such as “set up authentication” or “add payments.” Ask which provider is used, where keys live, how failed payments behave, and how an administrator recovers access. The answer becomes a checklist for the build and later handoff.

After the plan is approved, request one bounded section at a time. Bolt's token guidance recommends focused prompts and clear context. Small changes are also easier to review, restore, and explain to the next person who inherits the project.

The Current Pricing Model

Bolt measures AI work in tokens. On July 28, 2026, Free included one million monthly tokens with a 300,000-token daily limit. Pro started at $25 per month with ten million monthly tokens and no daily limit.

Teams started at $30 per member per month, and Enterprise used custom pricing.

The pricing page says paid-plan unused tokens roll into the following month and remain valid for two months in total. Free tokens do not receive the same benefit. Bolt also advertises yearly savings of up to 28 percent, so the exact checkout total depends on plan and billing term.

Plan	Listed Monthly Price	Core Allowance
Free	$0	1M monthly, 300K daily tokens
Pro	From $25	10M monthly tokens
Teams	From $30 per member	Team controls and tokens
Enterprise	Custom	Custom limits and support

Token totals do not translate into a fixed number of features. Bolt warns that larger projects require more file syncing, so later prompts can cost more than early prompts. Model selection, context size, repeated debugging, and broad requests also affect consumption.

Keeping Token Use Under Control

A sensible budget test uses a representative feature, not a disposable landing page. Record the starting balance, plan the change, build it, fix one realistic error, and record the ending balance. That gives a project-specific reference without pretending that every future change will cost the same.

Use Plan Mode for questions about approach, and keep Build Mode for approved edits. Tell the agent which files or behavior must remain unchanged. If a request touches unrelated areas, restore the last working version and narrow the task rather than spending more tokens repairing a broad rewrite.

Version history is a cost control as well as a safety feature. Name working checkpoints after completed behavior, such as “account creation and password reset pass.” A meaningful label helps a non-coder choose the correct recovery point without guessing among visually similar snapshots.

Do not prepay for a large allowance solely because the first generation looks promising. Complete an export, test the external services, and estimate ordinary maintenance first. The recurring work after launch can include copy changes, dependency updates, billing failures, user support, and security fixes.

Code Ownership and GitHub

Bolt can connect a project to GitHub, create a repository, import an existing repository, and work with branches. Its documentation says Bolt automatically commits and pulls changes at intervals. The connected repository becomes the durable record that another developer can inspect without entering the original Bolt workspace.

Bolt does not merge branches inside the product. That work happens on GitHub, where conflicts and review comments must be resolved. A non-coder should ask a developer to review any conflict involving authentication, database schemas, payments, or access rules rather than choosing whichever block looks newer.

A project download is another exit path, but code is only part of a running service. Environment variables, databases, uploaded files, DNS records, payment products, email templates, and OAuth settings may remain in external systems. List each system, its owner, and its export or recovery procedure.

Prove portability before launch. Download or clone the repository onto a separate machine, follow written setup instructions, and run the main user flow. If that cannot be done without the original builder explaining undocumented steps, the handoff is incomplete.

Web Apps and Native Mobile Apps

A responsive web app can run in a phone browser, but that does not make it a native App Store or Google Play app. Bolt uses Expo for native iOS and Android projects. The first prompt must identify the project as a mobile app so the correct structure is created.

Bolt's Expo guide separates building from store submission. Submission requires a computer, Node.js, Git, an Expo account, platform developer accounts, signed builds, store metadata, screenshots, privacy disclosures, and review. Apple and Google can reject a build even when it works in a local preview.

For a non-coder, the safer route is to validate the main flow with Expo Go, then involve someone familiar with EAS builds and store requirements. Budget for developer-account fees, device testing, privacy documents, and review time. Do not promise a release date based only on the generated preview.

If the requirement is simply a phone-friendly booking form or dashboard, a responsive web app may avoid store overhead. If push notifications, device APIs, offline behavior, or store distribution are essential, write those requirements before generation and test them on physical devices.

Databases, Payments, and Hosting

Bolt Cloud can supply a database and hosting, while Bolt also documents external integrations. Convenience does not remove operational decisions. Define what data is collected, who can read it, how it is backed up, and how it is deleted before inviting users.

Authentication needs more than a sign-in screen. Test password reset, duplicate accounts, expired sessions, deleted users, and every role. For a client portal, create two test customers and confirm that neither can reach the other's records by changing a URL or request identifier.

Payment work needs a provider test environment and official test payment methods. Confirm success, failure, cancellation, refund, duplicate submission, and webhook retry behavior. Keep product IDs, prices, tax settings, and refund permissions under an account owned by the business, not by a temporary contractor.

Hosting also needs a rollback and domain plan. Record where DNS is managed, which account pays for hosting, and how a prior working deployment can be restored. A shareable preview URL is useful for review, but it is not an operations plan.

Collaboration and Review

Bolt's collaboration documentation says collaborators share one project chat and only one prompt can be processed at a time. The project owner retains control over GitHub and certain integrations. That makes ownership more important than simply inviting everyone to the workspace.

Assign one person to accept changes and one person to test them. A reviewer should compare the requested behavior with the changed files, then run the affected flow. Visual approval alone misses broken validation, inaccessible controls, and data rules that only fail under a second account.

Keep decisions outside the chat as well. A short repository document can record the user roles, external services, environment variables, deployment route, and known limits. Chat history is useful context, but it is a poor substitute for a handoff that can be checked line by line.

For sensitive projects, require a qualified review before launch. Bolt's agent can produce code quickly, but the business still owns privacy, security, accessibility, and legal obligations. Generated output should enter the same review process as code written by a person.

Hard Cases for Non-Coders

Some failures require domain judgment rather than a better prompt. Access-control errors, corrupted records, payment disputes, dependency vulnerabilities, and store rejections can have consequences outside the editor. Set a threshold for escalation before users depend on the app.

Ask for help when a fix involves database migration, authentication policy, cryptographic keys, webhook signatures, or conflicting Git branches. Preserve a working backup and explain the intended outcome. Repeatedly asking the agent to “try again” can hide the original cause and consume the evidence a developer needs.

Use test data that contains no personal or confidential information. Separate development and production credentials. When the app is ready for real accounts, confirm that logs, analytics, error reports, and backups follow the same privacy rules as the visible application.

Finally, decide who maintains the service. A generated app still needs dependency updates, incident response, billing monitoring, and user support. If nobody owns those jobs, keep the project as a prototype or choose a managed system with an explicit support arrangement.

A Safe First Project

A reading list is a useful first exercise because it has visible state changes without payments or sensitive data. Ask for a responsive page where a user can add a title, mark it as read, filter the list, and remove an entry. Keep accounts and cloud storage out of the first pass.

1. Use Plan Mode to list the four actions, the page structure, and the acceptance checks.
2. Build the static interface and verify keyboard access at phone and desktop widths.
3. Add local persistence, then refresh and confirm that entries remain.
4. Enter empty, very long, and repeated titles to test validation.
5. Create a named working checkpoint before requesting visual changes.
6. Connect GitHub, clone the repository elsewhere, and follow the setup instructions.

Success means every action works, errors are understandable, and a second person can run the project from the repository. The platform guide provides alternatives if Bolt's runtime, budget, or ownership model does not match the next project.

The Verdict

Bolt is the better fit when a JavaScript web or Expo mobile project needs an integrated browser workspace, visible code, and a practical GitHub exit. Choose another route when the backend must use a different language, nobody can own production operations, or the project cannot absorb token variability and the specialist review required for sensitive features.

FAQ

What can Bolt build?

Bolt builds JavaScript-based websites, web apps, and Expo mobile apps in a browser workspace. Bolt Cloud can supply hosting, databases, domains, and other managed services, while integrations cover services such as GitHub and Stripe. A project that needs a non-JavaScript backend is outside Bolt's documented runtime support.

How much does Bolt cost?

Bolt's pricing page listed Free at $0 with one million monthly tokens and a 300,000-token daily limit on July 28, 2026. Pro started at $25 per month with ten million monthly tokens and no daily limit. Teams started at $30 per member per month, while Enterprise used custom pricing.

Can I move a Bolt project elsewhere?

Yes. Bolt documents both GitHub integration and project-file downloads. Moving the files does not automatically move domains, secrets, databases, user records, or third-party accounts, so test the exported project outside Bolt and write down every external dependency before treating the handoff as complete.

Can Bolt build an App Store app?

Bolt can create native iOS and Android projects with Expo, but generation is only the first stage. Store submission requires a computer, local tooling, an Expo account, Apple or Google developer accounts, signed builds, store listings, privacy information, testing, and review by the relevant store.