Bolt.new app to production
Take your Bolt.new app to production, ready for real users.
Bolt.new previews your app inside a browser tab, which is why building feels so fast. Taking a Bolt.new app to production means proving the published build behaves the same way. That takes data rules that hold, keys nobody can copy, backups you can restore, and code and accounts you control. We do that work, starting with the $299 Production Readiness Audit, and the fee is credited toward the build.
All prices are in US dollars.
- A studio founded in 2009, whose founder has built websites since 1999
- Fixed price and timeline before any build work
- Code ends up in your own repository
How a Bolt.new project is put together.
Bolt.new is an AI app builder from StackBlitz. It writes a JavaScript project, most often a React front end. While you build, the preview runs in your browser tab using WebContainers, a technology that runs Node.js inside the browser. The database, server functions and the published app run on Bolt's cloud.
Bolt Cloud adds a database, server functions, login, hosting on a bolt.host address and custom domains. Instead of Bolt Database, a project can use a Supabase project you connect yourself, an option on Bolt's Pro and Teams plans. Bolt can also publish through Netlify and syncs both ways with GitHub. Bolt changes quickly, so the audit records which of these pieces your project uses today and who controls each account.
Six things we check first in a Bolt app.
Bolt Database or your own Supabase
Bolt sets up the database, server functions and login for you, inside your Bolt account. Your own Supabase project gives you the dashboard, tools and account control directly. Either can run a production app.
The audit confirms which one you have and recommends whether the data should move into an account in your name. If you choose to move it, that migration is part of the quoted build.
Data rules and restores
Row-level security decides which signed-in user can see which rows, and we test each table from outside the app. Bolt's version history rolls back code but, per Bolt's own documentation, does not restore databases. So we set up automated backups and run a test restore before launch.
Secrets and build-time settings
Front-end variables in a Bolt app are baked into the files at build time. Change one on your host and nothing happens until the next build, and anything baked in can be read by any visitor.
Payment keys, AI model keys and database secret keys belong in server functions. Their values go in Bolt's Secrets settings, your host's settings or Supabase's, depending on your setup. We move them there and rotate any that already shipped.
Preview versus the published build
An app that runs perfectly in the browser preview can still fail once published: a package that needs native code, a missing environment value, a route that only worked in preview. The hosting score in the audit looks at how the app behaves outside the preview. The build fixes what breaks and adds error monitoring, so failures reach you instead of your users.
Login and email
Bolt Cloud handles sign-ups, logins and password resets, and Supabase projects use Supabase's login service. Either way, we test password reset, email confirmation and expired sessions on your live domain, check that reset links point there, and make sure confirmation and reset emails reach customers.
Code and hosting you control
Bolt's GitHub sync works both ways, so a repository in your GitHub account becomes the source of truth. If Bolt hosting suits your app and the account and domain are in your name, staying is fine.
Moving the front end alone to Netlify, Vercel or another host leaves a Bolt Database and server functions behind on Bolt, so the audit says whether to move both, one or neither. Public pages that need search traffic get rebuilt as static HTML or prerendered (built as HTML ahead of time).
The audit and build for Bolt projects.
The Production Readiness Audit scores seven areas, and for a Bolt app it ends with a recommendation on whether your database and hosting should stay on Bolt or move into your own accounts. Go ahead within 60 days of the report and the $299 is credited toward the build. A report delivered later than five business days after access is refunded in full. Our vibe-coded app to production page explains the audit and build in full.
Bolt.new to Production Quick Facts
Flamcom's audit for Bolt.new apps checks whether the published build behaves the same as the browser preview.
Bolt's version history restores code but not databases, so Flamcom sets up automated backups with a tested restore before a Bolt app launches.
Flamcom's $299 audit recommends whether a Bolt app's database and hosting stay on Bolt Cloud or move into accounts the founder owns.
- How Bolt runs
- Browser preview on StackBlitz WebContainers; database, functions and hosting on Bolt Cloud
- Backend
- Bolt Database or your own Supabase project (Pro and Teams plans)
- Known gap
- Bolt's version history does not restore databases
- First checks
- Row-level security, secrets baked into the build, behavior outside the preview
- Hosting
- Stay on Bolt or move to your own host, recommended per app in the audit
- Audit
- $299 fixed (US dollars), five business days from access, refunded if the report is late; credited toward a build ordered within 60 days of the report
- Build
- From $4,000; most small apps production ready within two to four weeks of starting the build
Bolt.new production questions
Is a Bolt.new app ready for production?
Not straight out of the builder, in most cases. Bolt gets the app working and published, but production needs tested data rules, secrets kept off the front end, backups you can restore, monitoring and accounts you control. Some apps need only a few fixes, others need parts rebuilt. The $299 audit tells you which, with a ranked fix list you keep either way.
Should I use Bolt Database or my own Supabase project?
Bolt Database is the easiest start, with nothing to set up. Your own Supabase project, available on Bolt's Pro and Teams plans, gives you direct access to the dashboard, backups and settings in an account in your name. For a business app holding customer data, we lean toward owning the account. The audit looks at your setup and recommends whether a move is worth it before launch.
How do I deploy a Bolt.new app outside Bolt?
Make sure the project syncs to a GitHub repository in your account, then deploy that repository to a host such as Netlify or Vercel. Set the front-end variables before the build, keep server secrets in the host or Supabase settings, and add a rewrite rule if the app routes in the browser. If the app uses Bolt Database or server functions, plan that backend move too.
Does Bolt's GitHub sync mean my code is backed up?
It means your code has a second home, which is a good start. Bolt commits changes to GitHub and pulls in edits made there, so the repository stays current. Check that the repository sits in your own GitHub account, not a freelancer's. Remember that the sync covers code only: your data lives in the database and needs its own backups.
How much does it cost to make a Bolt app production ready?
The Production Readiness Audit is $299, fixed, and credited toward a build ordered within 60 days of the report. Builds start from $4,000. A Bolt build costs more when the backend moves out of Bolt Database or when the app takes payments, and the written quote shows that before work starts. Our app audit and build price list sets out the published prices.
What access do you need to audit my Bolt app?
Collaborator access to your Bolt project, read access to the GitHub repository it syncs with, and read access to your Supabase project if it uses one instead of Bolt Database. The audit's five business days run from the moment that access is in place. You take our access away once the report is delivered, or at the end of the build if you hire us for it. If you ask, we sign your NDA before seeing code.
What if my Bolt app is broken right now?
Tick "My app is live and broken right now" when you contact us. Those requests are read first, and we aim to reply the same business day, without guaranteeing it. You get a fixed price for the emergency fix before we start, and we don't provide 24/7 or on-call cover. When the app is stable again, the $299 audit is the next step we recommend.
Send us your Bolt.new project.
Share the app link and tell us whether it is synced to GitHub and whether it uses Bolt Database or your own Supabase project. We reply within one business day (Monday to Friday) by email, confirming the audit scope and sending a payment link. Comparing builders? Read Lovable vs Bolt vs Replit for production, or see how we handle Lovable apps in production and Replit deployment.
Building something Bolt cannot? See custom development.
Your Production Readiness Audit includes:
- A scored report across seven areas, with your Bolt Database or Supabase backend reviewed alongside the code
- A fix list ranked by risk and effort, yours to keep
- A recommendation on whether your database and hosting should move into your own accounts
- A debrief call with the engineer who reviewed your Bolt app