What is probably broken
The app runs fine in Bolt.new but crashes on a real server with missing modules, build failures, or a process that will not stay alive.
The app runs fine in Bolt.new but crashes on a real server with missing modules, build failures, or a process that will not stay alive.
The same Bolt.new app running on your own server, with a working build, stable process, and live URL on your domain.
STEP 01
Bolt.new handles install, build, and start automatically. You need to replicate those settings.
STEP 02
Install dependencies and run the build with production env vars present.
STEP 03
A VPS needs a process manager. The app will not stay running on its own.
Quick check
If you cannot tick all five, we can fix it. Send us the repo and we handle the rest.
Free checklist
Get the exact 5-step checklist we run before every deploy. No fluff, just the things that actually break.
Done-for-you deploy
Fixed price per repo. 24h delivery or full refund. No hourly billing.
Related guides
Environment variables that worked in Bolt.new preview stop working after export. Public vs private, build-time vs runtime, and wrong values are the common traps.
Read guideSupabase connection failures after moving a Bolt.new app off preview. Wrong URLs, missing keys, and network config are the usual causes.
Read guideBolt.new API routes fail after export. Fix server config, runtime settings, endpoint paths, and env vars. Get your Bolt.new backend working in production.
Read guide