Put a Lovable or Bolt app online on your own EU host
Export a Lovable or Bolt.new app to GitHub and run it on blitz.cloud in the EU, including the Supabase backend question, checked 24 October 2026.
Export your Lovable or Bolt.new app's code to GitHub, connect that repository on blitz.cloud, and it goes online in the EU. Whether it needs a server (not just static files) depends on which stack it is; the next section helps you check.
Is your app static or does it need a server?
Lovable projects created from 13 May 2026 use TanStack Start and run server code: server-side rendering (SSR) and server functions. Check your package.json for @tanstack/react-start in dependencies. Projects from before that date, and most Bolt.new exports that haven't opted into a server framework, are a plain Vite/React single-page app that builds to static files.
If you find @tanstack/react-start, your app needs a server. If you don't, it is a static single-page app. Both cases work on blitz.cloud; the deployment steps differ slightly.
Export the code to GitHub
Lovable: in the project, use the GitHub integration to push to a repository. You can push to a private repository right away without sharing credentials.
Bolt.new: click the GitHub icon in the toolbar (or Export → GitHub) to push to a repository, or Export → Download to get a ZIP file you push yourself.
Once the code is on GitHub, you're ready to deploy.
Deploy it on blitz.cloud
Connect your GitHub account on blitz.cloud, pick the repository (private ones work), and blitz.cloud reads the project and builds from every push.
If your app is a server app (you found @tanstack/react-start): blitz.cloud reads the project, writes a Dockerfile if there is none, and every push goes online. Your app must listen on the port blitz.cloud gives it. Read it from process.env.PORT and fall back to 8080 if it is not set. This is the same pattern as the Node.js API guide. See deploy a GitHub project for the full walkthrough.
If your app is a static export: the same GitHub connection builds and deploys the static files. No server code runs; blitz.cloud serves them without an app container.
In both cases, connect your GitHub account on blitz.cloud, pick the repository (private ones are fine), and see deploy a GitHub project for the full steps.
The database: Supabase
Most Lovable and Bolt apps use Supabase as their backend. Over 60% of new Supabase databases are launched by AI app builders and coding agents, according to Sacra's research from May 2026.
Your app likely already talks to Supabase over the network, and that keeps working unmodified once your app runs on blitz.cloud. No code change needed. Your data still lives wherever that Supabase project runs — which is usually not the EU.
To move the data itself into the EU, you have options.
From Lovable: export via More → Database → Manage → Settings → "Export project data". Note that this export does not include storage files, Edge Function code or secrets. You move those separately by hand or through Supabase's own tools. Once you have the export, restore it into a PostgreSQL database on blitz.cloud the same way you would a Heroku or any other Postgres dump. See databases for the upload steps. DATABASE_URL is set for you automatically.
From Bolt: use whatever Supabase project you already connected. Export it with Supabase's own tools — pg_dump works the same way. Then restore it into blitz.cloud's PostgreSQL the same way as above.
Need the Supabase part in the EU too?
A managed Supabase in the EU on blitz.cloud is not yet built. Whether it's worth building depends on whether people ask for it. If you do want it, tell us what you need: email mara@blitzworks.io with a short note about your team size and which Supabase features you use. We read every request, and if enough people ask for the same thing, we build it.
See what's live for what is available today.
Checklist
- Code exported to GitHub (Lovable sync or Bolt push/ZIP).
- GitHub repository connected on blitz.cloud.
-
package.jsonchecked for@tanstack/react-startto know if it is a server app. - Port read from
process.env.PORTif it is a server app (or confirmed as static if not). - Supabase connection string still points at the same project (or moved, if you moved it).
- On Pro, domain repointed once the new app answers correctly.
Sources
- https://docs.lovable.dev/tips-tricks/deployment-hosting-ownership
- https://lovable.dev/blog/building-apps-using-tanstack-start
- https://lovable.dev/faq/backend/supabase
- https://docs.stackblitz.com/docs/features/export
- https://sacra.com/research/supabase-170m-year-growing-221-yoy/
Facts checked on 24 October 2026. Tell us at hallo@blitzworks.io if something here is out of date.
Read next
Move a Heroku app to the EU
Move a Heroku app's buildpacks, config vars, Postgres database and add-ons to blitz.cloud in the EU, with the exact commands, checked 24 October 2026.
blitz.cloud data location and GDPR - hosted in the EU
Where blitz.cloud stores your apps and data (data centres in the European Union), who operates it, which service providers are involved and how privacy is handled.
Deploy a GitHub project on blitz.cloud
Connect GitHub or paste a link to a public repository, and blitz.cloud builds the code and puts it online with HTTPS, with a new version on every push. How the build works, which port is used and what fails.
Put your app on your own domain.
Pro connects domains you own to any app, with HTTPS, for 7 EUR a month for your whole account. Try it free for 14 days: starting doesn't need payment details, and if you don't add them before it ends, nothing is charged.