Bolt.new pricing: building and running a business app

Bolt.new pricing includes Free, Pro, Teams, and a quoted Enterprise option. Bolt’s official price sheet, checked October 12, 2026, displays Pro from $25 per month and Teams from $30 per member per month with monthly billing. Higher token packages change the bill, so record the selected allowance alongside the price.

If you are turning a prototype into an employee app, budget for development, production use, and maintenance. Permute publishes this breakdown and sells connected business data and custom software with implementation support. A comparison with managed delivery needs the same data sources, users, and completed workflow on both sides.

Starting prices and included allowances

These are the public starting packages, not a quote for a particular app. Annual billing and larger allowances have their own terms. Confirm the billing cycle before comparing a displayed monthly equivalent with a month-to-month subscription.

Bolt lists hosting on Free and Pro, with custom domains on Pro. Its Enterprise offering lists SSO and audit logs. Select a plan from the controls and development workflow you require, then estimate usage; a small app can still need an organizational control that changes the purchase.

A token allowance does not promise a number of features

Bolt’s token documentation explains that the builder processes project files as well as your request. A larger project can consume more tokens per message. You cannot turn a short prompt or a count of screens into a dependable build-cost estimate.

Measure a representative change in your project: add a field, update its validation, and check the resulting screen and stored record. Record the consumption and the human review work separately. Repeat for an integration change, because changing a label does not represent the work required to connect an accounting source.

The token documentation describes paid monthly allocations rolling over for one additional month while the paid subscription remains active. Annual payment still supplies monthly allocations. Treat rollover as temporary capacity rather than a permanent reserve for future development.

Size the development team before buying its allowance

Bolt’s team billing documentation describes tokens assigned to individual members rather than a pooled team allowance. Model the people who will use the builder and their expected activity. An occasional reviewer and a person making daily changes may need different amounts of capacity.

For a synthetic example, three members at the published $30 starting rate cost 3 × $30 = $90 per month before any higher package or other service. This is a subscription calculation, not an estimate of how much software three people can deliver. Employees who use the finished app are a separate population to assess under the chosen runtime and authentication services.

Assign ownership of the project, billing account, and production credentials to the business. Document how another maintainer will take over if the original builder leaves. Access to an editor is only part of that handoff; the next person also needs the source connections, approved rules, and release procedure.

Check hosting limits against the deployed app

Bolt’s hosting documentation describes built-in hosting and separate paths for projects hosted on Netlify. Identify which path your app uses before applying a hosting allowance or estimating a migration. The existing deployment may have its own service agreement and bill.

Review the current Bolt Cloud hosting plans against your measured traffic and storage needs. Count the requests generated by a complete user session, including refreshes and background activity. A page view is not a reliable substitute for every billable or limited operation in the application.

List separately billed services in the architecture: an external database, email provider, or model API may have its own commercial terms. Ask the builder to identify which account pays each charge and what happens at its limit. A user should see a failed submission as an unresolved action, with a path to retry or seek help.

Budget the business rules and access review

An inventory exception app can show a shortage only after someone defines available stock, open demand, and the reporting cutoff. Match item identifiers and units across the ERP and spreadsheet first. Otherwise, a technically successful refresh can produce a number the planner cannot reconcile.

Include permission review in the implementation estimate. Test a warehouse employee’s request for another location’s restricted records and repeat after access is revoked. The enterprise app development process connects these checks to release and support responsibilities.

Compare the complete estimate with another route using the same acceptance criteria. The AI app builder comparison separates development approaches and their owners; it cannot replace a scoped estimate for your particular records and workflow.

Permute: budget the delivered workflow

Permute sells connected business data and custom applications with engineering delivery. We connect approved sources, match records, and implement the definitions your business owner approves. The same prepared data can support an app and a management report, with source evidence behind their calculations.

For an inventory planner, that can mean reviewing an exception and tracing it to the stock and order records used in the calculation. Current access controls limit what the user and application can query. Our engineers or your developers can build the interface under a defined delivery scope.

Ask for custom software delivery priced around sources, calculations, acceptance checks, and support. Compare it with the builder plan plus the people and services needed to meet the same requirements. Include recurring maintenance in both budgets.

Confirm the runtime and supported actions

Permute hosting is in early access for externally compiled static frontends. Source editing, builds, and a general server runtime are outside that hosting scope. A generated application that needs server code requires a compatible deployment plan; exporting code alone does not settle that question.

Confirm every required external write operation and its approval path before including it in delivery. Your team still owns business definitions and exceptions requiring judgment. Source connectivity and a working screen do not establish support for an arbitrary change to an ERP record.

Price Bolt from the members, token package, and controls needed to build your application. Add the hosting and service requirements of the deployed workload. Attach an implementation and maintenance estimate with named owners. A useful budget describes a finished, supportable workflow and the conditions that would change its cost.

Questions about budgeting for Bolt