Move your Bolt app to a server you own.
Bolt turned your prompt into a product. We move that product onto your own VPS so it no longer depends on tokens, a built-in host or anyone else's account.
- Fixed price, quoted before any work starts
- Your live app keeps running until the switch
- Every login and password handed over to you
What gets moved, and where it ends up
| Part | Today | After the move |
|---|---|---|
| Code | Bolt project | Your GitHub repository |
| Database | Bolt database | Postgres on your server |
| Hosting | Bolt hosting | Your VPS |
| Address | yourapp.bolt.host | yourapp.com with SSL |
| Cost | Monthly tokens | Flat server fee from $6 |
Why people move off Bolt
Bolt is a good place to build. These are the reasons owners give for not staying once the app is real.
- Tokens disappear on fixes
- Large projects use more tokens for every change. Many builders spend most of their allowance repairing things rather than adding them.
- The app runs where it was built
- Bolt publishes your project to its own hosting. That is fine for a demo and limiting for a product that needs background jobs, custom server settings or a specific region.
- Your database lives in the builder
- When the database is created inside Bolt, backups and direct access depend on the platform. Your data should be in an account you control.
What a Bolt app is made of
A Bolt project is usually a React app built with Vite, or a Next.js app, written in TypeScript. Data lives in a Bolt database or in Supabase, both of which are Postgres underneath. These are standard tools and run well on a VPS.
On your server it runs on Linux with Postgres, a web server that handles SSL, nightly backups and automatic deploys from GitHub.
What we do in a Bolt migration
- Export the project to a GitHub repository under your account
- Build the app and serve it from your VPS, with a Node process if it needs one
- Export the database and restore it to Postgres on your server or to a Supabase project you own
- Move user accounts, uploaded files and server functions
- Move environment variables and API keys
- Point your domain at the new server and issue the SSL certificate
Four steps from Bolt to your own server.
Most apps are moved in under a week. You do not need to be technical for any of it.
Free audit
Share your project. We check what it depends on and what the move involves.
1 business dayFixed quote
You get a written plan and one price. It does not change once agreed.
Same dayTrial move
We rebuild the app on your new server and you test it at a private address.
2 to 4 daysSwitch and handover
We point your domain to the new server and hand you every login, with a written guide.
About 1 hour, no downtime
One fixed price. Paid once.
A migration is a one-time job, so we charge for it once. After that you pay only your server provider. If the trial move does not work, you pay nothing.
See full pricingApp migration, from
$240One-time fee. Server from $6 to $24 a month.
- Server setup, SSL and domain
- Database, users and files moved
- Nightly backups and auto-deploy from GitHub
- 30 days of support after handover
Bolt migration questions
Can I export my code from Bolt?
Yes. Bolt lets you download the project or push it to GitHub. We start from that export and make it run on your server.
My Bolt app uses Supabase. Does that move too?
It can. We either move the data to Postgres on your VPS or transfer it to a Supabase project in your own account, so you hold the keys either way.
Will the app look or behave differently?
No. It is the same code and the same data, served from a different machine. You test the trial copy before anything goes live.
Can I keep building with Bolt after the move?
Yes, through GitHub. Changes you push to the repository deploy to your server automatically, whichever tool wrote them.