Bolt app deployment
Deploy an app built with Bolt to production.
Pull the complete Bolt project source into a repository, open it in an Adios workspace, and turn the generated prototype into a buildable, observable, approval-gated production release.
Source to production
- 01Bolt source
- 02Adios workspace
- 03Build + preview + logs
- 04Human production approval
Production stays separated from the agent's preparation work until you approve the release.
Source
Reviewable files and config
Preview
Healthy before production
Evidence
Build output and runtime logs
Control
Human approval gate
Deployable projects
Keep the generated app. Add the production contract.
Adios works from the project source and its normal framework commands. It does not require the app to be regenerated in a proprietary format.
- Bolt React, Vite, and Next.js applications
- Full-stack JavaScript and TypeScript projects
- API-connected web products
- Projects that need secrets, services, domains, and health checks
Bolt CLI source handoff
Pull the Bolt project into a durable codebase.
Use Bolt's CLI pull command to download the current project files to a local directory. Put that directory in source control, then open the repository in Adios so builds and fixes remain attached to the code you own.
bolt pull project/<project-id> --out ./app
cd app
git initExample agent prompt
Ask for a verified release, not only a deploy command.
Use this in the Adios AI workspace after pulling and saving the Bolt project source.
“Prepare this Bolt project for Adios. Inspect the framework, build scripts, ports, environment variables, and backend dependencies. Add a reviewable adios.yaml, run a clean production build, fix failures using the logs, and give me a working preview before asking for production approval.”
Reviewable configuration
The agent writes down how the app should run.
The exact manifest should match the repository. This example makes a conventional Node.js production build, port, and health endpoint explicit so the release can be reviewed and repeated.
Learn how adios.yaml worksname: vibe-app
region: de
build_cmd: npm ci && npm run build
start_cmd: npm start
runtime:
name: node@24
port: 3000
health_path: /api/healthSource-to-release workflow
Five checks between generated code and production.
- 01
Inspect the project source
Identify the framework, package manager, build output, start command, expected port, environment variables, and any stateful services before creating a release.
- 02
Make the runtime contract visible
Write or update adios.yaml so the build command, start command, runtime, port, health check, secrets, and managed resources can be reviewed beside the code.
- 03
Build and open a preview
Run the production build in an isolated workspace, start the application, and inspect a preview URL before treating the project as deployable.
- 04
Read logs and repair failures
Use build output, runtime logs, and the configured health path to diagnose failures. Apply the fix to source, then rebuild the same project rather than patching production by hand.
- 05
Review and approve production
Check the final source diff, configuration, preview, and health result. A person approves the production deployment after the agent has prepared a healthy release.
When the build fails
Give the agent evidence it can act on.
Generated Bolt projects can depend on development-only defaults or browser-held configuration. A clean Adios build exposes those assumptions, while workspace logs give the agent concrete evidence for a source-level fix and verified rebuild.
build · failed
↓ inspect output
source + adios.yaml · updated
↓ rebuild and health check
preview · healthy
↓ human review
production · ready for approval
Framework deployment
Match the generated project to its runtime.
Deploy Next.js
Server-rendered routes, route handlers, static output, and persistent Node.js apps.
Open runtime guideDeploy React
Vite and other React frontends served as static or Node-backed applications.
Open runtime guideDeploy Node.js
APIs, background workers, and full-stack JavaScript services with explicit start commands.
Open runtime guideDeploy Postgres
Managed relational data for apps that need durable state and a private connection string.
Open runtime guideFAQ
Deploying Bolt apps with Adios.
How do I move a Bolt project to Adios?
Pull the project source with Bolt CLI, save it in a Git repository, and open that source in an Adios workspace. Adios then builds and runs the project from the files you control.
Does deploying with Adios remove my Bolt project?
No. Pulling the source gives you another copy of the project. Keep the repository as the durable deployment source and decide how future Bolt changes should be merged into it.
Does Adios deploy only Next.js apps?
No. Adios supports explicit build and start commands for common frontend, full-stack, API, worker, and data-backed projects. The detected framework changes the runtime contract; the source-to-preview-to-production workflow stays consistent.
Can the AI agent deploy to production without approval?
No. The agent can prepare source, configuration, builds, previews, and diagnostics, but the production transition is approval-gated so a person can review the release first.
What happens when the production build fails?
The build output and runtime logs remain available to the workspace. The agent can use that evidence to update the source or configuration and run a new build before asking for production approval.
Vibe coding tools
Deploy from another AI coding workflow.
From source to healthy release
Let Bolt prepare the deploy. Keep production approval yours.
Start with the source you already have, verify it in an Adios preview, and promote only the release you reviewed.
Start free trial