Vibecode to production · Bolt.new

Your Bolt app only
works in the preview.

Bolt builds something that runs in a browser tab remarkably fast. The problem starts with the step after: a real database, users logging in at the same time, payments and an environment that stays up when the tab is closed.

Vibecode naar productie
0:00 / 0:00

In half a minute I show what almost always sits below the waterline in a project like this: everyone can reach all the data, payments that only work in the demo, and an environment that does not run outside the tool.

Recognise it? Send your link. The first opinion costs you nothing.

Sound familiar

Where Bolt projects run aground.

01

Everything runs in the browser

The WebContainer Bolt builds in is not a server. The moment you need something that has to run in the background, like sending email or processing a webhook, it stops.

02

The database is a toy

Test data in local storage or a stray Supabase without permissions. Put real customer data in it and everyone can reach everything.

03

Every prompt rewrites too much

One change and the model touches files that were already fine. Without version control with meaningful commits, nobody knows what broke.

04

Deploying does not work

It works locally, not on Vercel or Netlify. Usually environment variables, build steps or server-side code that never existed are missing.

05

No tests, no safety net

You no longer dare change anything because you only discover afterwards what fell off.

06

The subscription is the infrastructure

If the tool or the subscription stops, your product stops. There is no repository that runs independently of the platform.

How it works

From preview to something allowed to go live.

01

Export and assessment

You send the export or the repository. I look at what is usable: screens, flow and data model. That opinion costs you nothing.

02

A foundation underneath

Supabase with row-level security, real migrations, environment variables and server-side code for everything that does not belong in the browser.

03

Finish what is missing

Logins with roles, payments through Stripe or Mollie, email that arrives, and error handling for when an external service goes down.

04

A deploy that stays up

Your own domain, monitoring and a repository in your name where every change can be traced.

What you end up with
  • An application that runs independently of Bolt
  • Database with permissions per user
  • Payments and email that actually work
  • Repository and hosting in your name
  • 30 days of support after delivery

The first opinion costs you nothing: send me the repository or a link and I will tell you honestly whether building on beats starting over.

Frequently asked questions
Can you take over my Bolt project without starting again?
Usually yes. Bolt generates ordinary React or Next.js, and that is the stack I work in daily. What is often missing is the server side and the data model; I build that underneath instead of throwing the lot away.
What does finishing it cost?
A finishing track usually takes four to six weeks and gets one fixed number. If it is small and manageable, it is less. If you do not know what is needed, you start with Discovery, which comes off the build price.
How long does that take?
Usually four to six weeks, depending on how much is usable and how many integrations come with it.
Can I carry on in Bolt afterwards?
For prototypes, fine. For the production environment, no: that then sits in your repository, with tests and migrations an AI tool would walk straight through.
Let's build

Tell me what you
want to build.

A half-hour call. You get an honest answer about what it costs, how long it takes and whether building it is smart at all.

Free · no obligation

Have your current site or tool scanned

You do not have to want to buy anything yet. Send what you have and I will tell you honestly what I would keep, what I would replace and whether that is worth the investment. Including when the answer is that you are better off doing nothing.

The scan is a first impression, not a security audit.

WhatsApp
0:00 / 0:00
  1. 01Send a link to your site, your tool or your repository
  2. 02I look at speed, structure, data and security
  3. 03Usually within two working days you hear what I would replace and what that costs
Vibecode naar productie
0:00 / 0:00
Take your Bolt.new app to production · Webframer