Deploy a Bolt.new App to Production Beyond the Preview

Deploying a Bolt.new app to production: leave the in-browser preview, pick hosting, fix the backend and env vars, add a domain and keep shipping safely.

Short answer

Bolt.new runs your app inside the browser during development, so production is the moment you find out what actually depends on a real server, real environment variables and a real database. Deploy through Bolt's hosting integration or export to GitHub and your own host, then add a domain, a production backend, monitoring and a release routine.

On this page
  1. Why the preview hides problems
  2. Pick your deployment path
  3. Get the backend right
  4. Environment variables, the silent failure
  5. Domain, HTTPS and email
  6. Add a staging step
  7. Monitoring and cost control
  8. When Bolt-built code needs engineering support
  9. From web app to app stores
  10. Two-week plan
  11. FAQ
  12. Tools from the jocapps ecosystem

Why the preview hides problems

Bolt.new builds and runs full-stack JavaScript apps in the browser using WebContainers. That is why it feels instant: the dev server, package installation and preview all happen in your tab. It also means the preview environment is unusual. It is single-user, short-lived, and some things that "work" there are really running in your browser session rather than on a server.

When you move to production, three categories of issues tend to appear:

  1. Server code that never really ran server-side. API routes, secrets and database calls that worked in the preview need an actual runtime with correct environment variables.
  2. Data that lived nowhere permanent. Local state, in-memory stores or a demo database are not a production data layer.
  3. Build differences. The production build is stricter than the dev server: type errors, missing environment variables at build time and import issues surface here.

Pick your deployment path

PathHow it worksChoose it when
Deploy from BoltUse Bolt's built-in hosting or its deployment integration (historically Netlify)Simple front-end or static-heavy apps, fast iteration
Export to GitHub, host yourselfDownload or push the project to a repo, connect a hostYou need control, staging, reviews or compliance
HybridKeep editing in Bolt, sync to GitHub, deploy from the repoTeams that want Bolt's speed with a proper pipeline

For anything customers depend on, we recommend getting the code into GitHub early. It gives you history, diffs to review after large prompts, and the freedom to change hosting later.

Get the backend right

Bolt projects commonly use Supabase for database and auth, sometimes Firebase or a custom Node server. Whichever it is:

  • Create a production project or instance separate from the one used in the Bolt preview.
  • Move schema creation into migrations so production can be rebuilt reproducibly.
  • If Supabase, enable row level security and test with two accounts; the anon key in the browser is public by design.
  • Move any third-party API key out of client code and behind a server function.
  • Confirm the hosting platform supports your server parts: serverless functions have timeouts and size limits that a long AI call or file processing job can exceed.

Environment variables, the silent failure

The most frequent "works in Bolt, blank page in production" cause is environment variables. Front-end frameworks only expose variables with a specific prefix (for example VITE_ in Vite projects) and inline them at build time. So:

  1. List every variable the app reads. Ask Bolt to produce the list, then search the code yourself.
  2. Separate public variables (safe in the browser) from secret ones (server only).
  3. Set them in the hosting provider for each environment.
  4. Trigger a fresh build after changing them, since build-time values do not update on their own.

Domain, HTTPS and email

Connect your domain at the host and let it issue certificates. Then update every place that knows the old URL: auth redirect URLs, OAuth app settings, CORS allowlists, webhook endpoints from payment providers and links in transactional emails. Missing one of these leads to errors that only appear for some users, which are the hardest to debug.

Add a staging step

Bolt encourages large, sweeping changes from a single prompt. That is a strength while building and a risk once users depend on the app. A staging site, which is simply a second deployment from a staging branch with its own backend, lets you check a big change before customers see it. Most hosts make this a few clicks.

Before promoting staging to production, click through sign-up, login, the main workflow and any payment flow, and glance at the GitHub diff for unexpected changes to authentication or database code.

Monitoring and cost control

  • Add front-end error tracking with source maps so production errors show real file names.
  • Set an uptime check and a simple status page if external users rely on the app.
  • Turn on usage alerts at your database and hosting providers; serverless bills grow with traffic and with bugs that cause retries.
  • If the app calls an AI API, log the number of calls and cost per day.

When Bolt-built code needs engineering support

Bolt gets you remarkably far, but production often surfaces work that is easier with experienced hands: untangling a backend that grew prompt by prompt, setting up proper environments, or making performance acceptable on mid-range phones. OnlineAppCreator takes over exactly this transition. Our AI Code Engineers export and review the project, set up hosting, staging, backups and monitoring, and maintain it under an SLA if you want, while you can keep prototyping new features in Bolt and hand them over through GitHub.

For organisations with procurement and security requirements, OnlineAppCreator can deploy into your own cloud account and provide the documentation reviewers expect.

From web app to app stores

Once the production web app is stable, mobile stores are a common next request. WebViewGold turns the hosted Bolt app into iOS and Android apps with push notifications and native features, so the production URL you just built becomes the single source for web and mobile. See publishing a Bolt app to the App Store for the store-specific steps, and scaling a vibe-coded app for what to expect as users grow. If you are still choosing a builder, compare Lovable, Base44 and Bolt.

Two-week plan

  • Days 1 to 2: push to GitHub, list environment variables, create the production backend.
  • Days 3 to 5: deploy staging, fix build errors, set up domain and redirects.
  • Days 6 to 8: security pass on database rules and API keys, monitoring.
  • Days 9 to 10: production deploy, soft launch, watch errors and costs.

FAQ

Why does my Bolt app work in the preview but not after deploying?

Usually missing or misnamed environment variables, server code that needs a real runtime, or stricter checks in the production build. Check the build log and the browser console first.

Do I have to use Bolt's own hosting?

No. You can export the project to GitHub and deploy it on any host that supports your framework. Many teams start with Bolt's deployment and move later.

Can I keep using Bolt after going to production?

Yes. Sync the project to GitHub, develop new features in Bolt, and deploy through staging so you can review changes before users see them.

Is a Bolt app fast enough for production?

Often yes, after a production build and basic optimisation such as image compression and code splitting. Measure on a real mid-range phone over mobile data before launch.

Tools from the jocapps ecosystem

Want this done right, and fast?

Talk to our AI Code Engineers and AI architects. In a free 30-minute call we look at your idea, prototype or roadmap and tell you honestly what it takes to ship it.

24/7 call support in English and German.

Free call

Free intro call

Tell us which task an AI agent should take responsibility for. We show how our platform, AI Code Engineers and operations plug into your stack.

  • 30 minutes, no obligation
  • Honest feasibility check
  • Concrete next step
Rather talk now? 24/7 call support in English and German+49 761 519 751 50