What is probably broken
The frontend loads but every API call returns 500 or 404 because the server cannot route or execute the API functions.
The frontend loads but every API call returns 500 or 404 because the server cannot route or execute the API functions.
API routes working correctly on the production server with proper routing and environment.
STEP 01
Bolt.new may use different API patterns depending on the app stack.
STEP 02
The server needs the right runtime to execute API routes.
STEP 03
Verify each API route responds correctly before going live.
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
Bolt.new apps often fail when moved from preview to a real server. Missing build config, env vars, or wrong start command are the usual causes.
Read guideEnvironment 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 guide