I take Bolt.new projects from "works in the preview" to actually live. If your app runs perfectly in the editor but breaks the moment real users touch the deployed URL, that's the exact problem I fix.

Bolt is genuinely great at getting you a working app fast. But the editor runs your code inside a browser sandbox, not on a real server. The deployed version is a different machine with different environment variables, a different connection to your database, and no memory of anything the sandbox knew. That gap is where launches die, and it's almost never the code's fault.

Clean export, real repo, real deploy pipeline

Environment variables, secrets, and Supabase wired up correctly in production

Custom domain, build config, and CI/CD so deploys stop being one-way surprises

Load, error handling, and launch readiness

Your Bolt code is genuinely portable (standard Vite, React, Next.js) which means it doesn't need a rewrite. It needs someone who knows what production actually requires. I do the boring, unglamorous infrastructure work that turns a prototype into something you can charge money for.

Your project out of Bolt and into a proper Git repo that passes the only test that matters: a fresh clone builds with one npm install and zero connection back to Bolt. Sensible branching, a readable history, and a .gitignore that isn't leaking anything.

Every environment variable that existed only in the editor moved into the host. Build commands and output config set correctly. Continuous deploys from your repo, so pushing a change doesn't spin up a brand-new random URL and orphan the custom domain you already set up. Preview deploys for testing before anything hits users.

Your Supabase project claimed and owned by you, not floating in a half-connected state. Row Level Security reviewed so users can't read each other's data. Edge functions configured correctly (including the JWT setting that silently rejects every webhook you send it). Auth redirects and callback URLs fixed for your real domain instead of the sandbox one.

Real error handling instead of a happy path, loading and failure states in the UI, seed and test data cleaned out of your production database before a paying customer sees it, and error monitoring so you find out about the 500 before your users tell you.

Custom domain and SSL live, analytics in, a documented runbook for how to deploy and roll back, and the whole thing written down so you or a future developer can maintain it. And critically: you can keep iterating in Bolt afterward without breaking what I set up.

Most deployments ship in 2 to 4 days. Faster if your app's already exported.

Projects, stacks, and outcomes on my site. Live builds you can open and read on Bolt.

Website: pmcosta.dev