What Bolt is and delivers
Bolt, available at bolt.new, is StackBlitz’s AI application builder. It combines conversation, code, execution and publishing to create websites and web applications; mobile projects use Expo. Its output is an editable project with additional services when persistence or authentication is needed.
Assess its usefulness by following a complete task: entering information, obtaining a result and correcting an error. Distinguish user experience from the implementation supporting it. A visually convincing search still needs to handle empty filters, withdrawn resources and files that cannot be downloaded.
Reference documentation: Intro to Bolt.
History: from StackBlitz to Bolt Cloud
Eric Simons and Albert Pai are StackBlitz’s cofounders. Their April 2022 announcement documented a $7.9 million funding round. WebContainers, introduced in May 2021, enabled Node.js environments to run in the browser. Bolt arrived in October 2024, applying that infrastructure to AI-assisted development.
Bolt Cloud was announced on 14 August 2025, initially with hosting and domains; other capabilities were then in beta. The Bolt v2 announcement on 2 October 2025 dated its release to the previous day. This is an evolution from generating applications toward an environment that also organizes their operation.
Reference documentation: StackBlitz origins and seed round · StackBlitz execution environments · Bolt v2 introduction · Bolt Cloud announcement.
Technology, open source and compatibility
WebContainers provides a Node.js environment with a terminal. Bolt targets JavaScript technologies and does not support PHP or Python backends within that environment. The original public bolt.new repository has an MIT license and demonstrates combining an agent with execution tools; it does not necessarily describe every feature of today’s commercial service.
Choosing Bolt for a new interface does not mean any existing system can be imported unchanged. Before moving a project, identify its language, build commands, dependencies and external services. An API connection can retain a specialized system outside Bolt without attempting to rewrite it entirely.
Reference documentation: StackBlitz execution environments · Supported technologies · Open-source Bolt repository.
Standard, Max and Forge
The current selector distinguishes Standard, for everyday tasks, and Max, available on paid plans for more complex work. Bolt chooses the underlying models. Forge uses open models and has separate conditions. Its Pro promotion ran from 14 September to 14 October 2026; it should not be treated as permanent. Lite retains distinct conditions.
Compare agents with the same bounded correction: retain filters when a page reloads without changing its design or links. Compare the result, introduced changes and usage. Additional reasoning is useful when it improves a verifiable project criterion; it does not replace a clear specification.
Reference documentation: Agent selection · Forge documentation · Forge announcement.
Planning before changes
Plan Mode supports discussing a project and proposing an approach without modifying its existing code. It can consult context and web sources. Starting from the homepage creates a base structure before presenting the plan, unlike discussing an established project. Implementing the proposal switches to Build Mode.
For a learning resource, the plan should separate content, navigation and behavior. Request a list of screens and states: home, search, entry, empty results and unavailable link. Defining these states reduces implicit decisions left to the agent and allows each step to be reviewed with people familiar with actual use.
Reference documentation: Plan Mode.
Imported design and visual editing
The Figma integration imports a frame, not an entire project. It uses Anima; the Teams design-system workflow has a specific screenshot-based route. In Bolt, visual changes accumulate in the preview: saving the batch updates code and uses tokens. Seeing a change on screen does not mean it has been saved.
Also review states a static mockup does not show: long copy, keyboard focus, a missing image and a form error. In a poster library, a card should retain its title and language even if its thumbnail fails; the image should not be the only way to understand the resource.
Reference documentation: Visual edits · Figma integration.
Bolt Cloud and data administration
Bolt Cloud combines hosting, domains and a database. Its environment supports users, files, functions and secrets. Claiming a Bolt database for management through Supabase differs from connecting another database; advanced options are limited to certain roles.
In an application with persistent information, the schema should separate a resource’s stable identifier, translations and editorial status. Changing its title then need not break every link. This structure is a design proposal, not a configuration Bolt guarantees by default. Specify and test it before loading actual content.
Reference documentation: Intro to Bolt · Advanced database settings.
Mobile applications with Expo
State the intention to build a mobile application at the start. Expo Go previews it on a phone through a QR code. Building and distributing through Expo Application Services is a separate step involving tools and the relevant app-store developer accounts.
A mobile test should include physical actions and usage conditions, not only screen dimensions. For a materials catalogue, check PDF opening, returning from another application and language retention. If offline operation is required, design and test that requirement explicitly: a preview loading with good coverage does not demonstrate offline availability.
Reference documentation: Expo mobile apps.
Browsers and device differences
Bolt supports desktop Chromium and Safari. Safari provides read-only code, no terminal and a remote preview. Mobile lacks Code view, visual editing and database management.
Reviewing on a phone and maintaining an application from a phone are therefore different tasks. The former device may be right for testing the audience’s experience; a computer is needed for certain corrections. When documenting an issue, record the browser and editing surface so another person can reproduce it.
Reference documentation: Supported technologies.
Auditing and permission verification
Bolt distinguishes a database review available on all plans from a project audit on paid plans. The latter reviews code and data, proposes or applies fixes and may leave outstanding actions. The dedicated audit button has different usage treatment from requesting an audit in chat.
Review corrections just as you would a new feature. One proposed test uses two fictional accounts: each should see only its own records and neither should retrieve another’s information by changing an identifier. Also check sign-out, error messages and shared links. Record the result as evidence for those specific cases.
Reference documentation: Project security.
Git, export and recovery
GitHub supports code synchronization and branches. A project ZIP can also be downloaded from desktop. Restoring an earlier version does not restore Bolt or Supabase databases. Documentation permits commercial use of created code under the applicable terms.
A recoverable copy needs testing, not merely storage. An exercise can restore code into a test project, connect fictional data with the expected structure and exercise search. If recovered code expects a column that no longer exists, the interface may fail despite successful history restoration. Keep a service inventory alongside recovery instructions.
Reference documentation: GitHub for version control · Project recovery · Commercial ownership.
Publishing, plans and usage
Built-in hosting provides a bolt.host address and custom-domain options depending on plan. Hosting limits differ from token usage: reaching a limit can stop the site displaying publicly. Tokens measure context processing and generation, so a larger project may consume more per message.
A budget should cover building, review and operation. A practical comparison completes a representative change, measures usage and checks which services continue consuming resources afterward. Hosting matters particularly for a campaign with many visitors; reducing agent instructions does not necessarily reduce website traffic.
Connectors and interactive presentations
MCP connectors let the agent use tools from other services. Documentation says all available tools initially enable and their settings apply across projects. Bolt Slides adds web presentations: it exports static PDF and JSON containing presentation data.
For a prevention session, a slide could contain an interactive example using fictional data. The PDF is useful reference material but does not retain that interaction. For connectors, a library that only needs to consult resources does not necessarily need permission to delete or publish them: enabled actions should match the intended work.
Reference documentation: MCP integration · Bolt Slides.
Privacy and model training
The revised policy permits eligible content to be used for training and dataset licensing from October 2026, with opt-out controls. Accounts located in the EEA, UK and Switzerland are excluded; organizational agreements may establish different conditions. Forge requires specific consent where those uses apply.
Review the actual account and content being submitted. A test project can work with synthetic records and public documentation; personal information is unnecessary to demonstrate navigation. Training configuration and permission for an application to access a service are independent decisions.
Reference documentation: Privacy policy · Forge documentation.
Practical applications in OSH
It can explore safety communication resources, such as a materials finder or an interactive guidance page. Its occupational safety value lies in testing the user experience before investing in development, using reviewed content and without assuming that a prototype can assess hazards or authorize work simply because it appears complete.
Besides the catalogue, a proposed use is an interactive page directing people to public resources by topic or language. Another is demonstrating a visual library before deciding its final structure. These experiences should return reviewed materials, without generating new preventive instructions or presenting automatic selection as a professional assessment of a workplace situation.
Worked example and result checks
For example, a team could demonstrate a poster catalog with filters for language and topic. Testing would establish whether people can find the correct resource before introducing internal documents, real accounts or information requiring controlled access.
For the poster catalogue, prepare sample titles, topics, languages, authorised images and links to the correct files. Define how filters combine and what appears when nothing matches. Request an initial version without user registration to check whether the resource organisation makes sense first.
Try a combination with results, an empty combination and a long title. Check keyboard navigation, mobile readability and whether each thumbnail opens a poster in the same language. Change one resource and verify that its previous link does not remain in another view. If GitHub is connected, confirm that the expected revision has synchronised. Before actual publication, open the final address as a reader and repeat the cases: preview behaviour does not prove hosting behaviour. Record any differences so they are resolved before relying on the catalogue as a regular entry point.
Limitations and conditions of use
Rapid application generation does not demonstrate accessibility, security or maintainability. Review navigation, permissions, dependencies and failure cases; preventive content requires its own validation and should not be assumed correct merely because the interface works.
Bolt help distinguishes connecting another database from transferring administration of the existing one. Replacing a connection can cause data loss or leave the project pointing to different information. Migration therefore requires reviewing code, data and access together. Code version control also does not replace a backup and recovery strategy for stored records.
Reference documentation: Intro to Bolt · Advanced database settings.
When to choose it and how to complement it
Bolt fits browser-based iteration on a functional web experience when the project suits its supported technologies. Figma can help settle visual organisation before generating code. Lovable provides another workflow to compare using the same search and permission tests.
Consider ease of correcting errors, access to code, operating costs and service ownership. If a small catalogue works as a simple page, avoid adding accounts and a database without a concrete need: each component introduces operational and review work. Include that continuing work when comparing the initial convenience of different builders.
Frequently asked questions
Does GitHub synchronisation prove the website is current?
No. Synchronisation retains changes in the repository. Verify publication at the final address, checking the version and behaviour the audience will see.
Does adding a database always improve a prototype?
No. It is useful when persistence, editing or access requirements justify it. A static dataset may answer the initial design question when testing filters over a small collection.
Can a catalogue replace a work instruction?
No. It helps people find resources. Suitability for the role, current status and understanding of instructions need their own process even when search works correctly.
