How to host a Lovable app in Europe in 2026

Sync your Lovable project to GitHub, deploy that repository to a European platform such as Eurobase, and put the database in a Supabase project in an EU region. If you only need the data in Europe, Lovable itself can store the backend there, but your site is still delivered from locations worldwide. Scalingo and Sliplane suit you when you'd rather run the app as a plain Node.js server next to a database.

Ways to host a Lovable app in Europe at a glance

Platform	How the Lovable app runs	Company	Starts at	Main gap
Eurobase	TanStack Start and Vite on V8 isolates, built from Git	Warsaw, Poland	Free, then €10 a month + VAT	No managed Postgres or preview deployments
Lovable hosting	Lovable's own hosting, backend region set to Europe	Lovable Labs Incorporated, Delaware law	Free on a lovable.app address	Frontend served globally, region locked once chosen
Scalingo	Node.js server from the Nitro build	Strasbourg, France	€7.20 a month for 256 MB, excl. VAT	Its Postgres has no Supabase auth or storage
Sliplane	Container from GitHub or an image	Berlin, Germany	€9 per server, excl. VAT	Also sells regions in the US and Singapore
Supabase	Backend only: database, auth, storage, functions	Not stated	Not stated	Doesn't host the frontend

Prices are from each provider's own page, checked on 9 and 10 November 2026.

Two parts to move, separately

A Lovable app has a frontend and a backend, and Lovable's docs treat them as independent. You can move only the frontend and keep the built-in backend, or move both.

• The frontend is your code. Apps created from 13 May 2026 use TanStack Start, which renders pages on the server and needs a host that runs server code. Older apps are React and Vite and build to static files. Open package.json: if it lists @tanstack/react-start, you have the newer kind.
• The backend is a database, sign-in, file storage and edge functions. Lovable supports only managed or self-hosted Supabase as a destination. A plain Postgres database means writing your own replacements for auth, storage and functions.

The code reaches your repository through Git sync, which works with GitHub, GitLab or Bitbucket on every plan. A .zip download needs a paid plan, and neither includes database rows or uploaded files.

What to check before you move

• Where each part sits. Lovable's region setting covers backend data only. The published site is served from points around the world whatever region you choose.
• AI features and connectors. Calls to Lovable's AI gateway and app connectors keep going through Lovable, and keep using your workspace credits, until you replace them with your own provider accounts.
• Server variables. A TanStack Start app on the built-in backend needs VITE_SUPABASE_URL and VITE_SUPABASE_PUBLISHABLE_KEY at build time and SUPABASE_URL and SUPABASE_PUBLISHABLE_KEY on the server. Secrets saved in Lovable aren't in the repository, so add each one again.
• Sign-in redirects. Add the new address to your auth provider's allowed redirect URLs, or Google and GitHub sign-in fail after the move.
• What "Europe" means. Supabase's own regions page points out that its Europe group includes London and Zurich, which aren't EU member states. Pick Frankfurt, Stockholm, Ireland or Paris if the contract says EU.

1. Eurobase

Eurobase deploys the repository Lovable syncs to, from GitHub or GitLab, and runs it on European infrastructure run by Scaleway, a French provider. Apps on @tanstack/react-start 1.132.0 and Vite 6.1.0 or newer run on V8 isolates. If the Vite config uses the Nitro plugin, the build replaces it with the Cloudflare Vite plugin, so you don't pick a preset. An older Lovable app on Vite runs the same way, or as a static site. Lovable wraps its Vite config in @lovable.dev/vite-tanstack-config, so deploy once to the default address and try a server-rendered page and a server function before you switch the domain.

Lovable can keep editing the same repository through two-way sync while Eurobase serves the live app. When you edit outside Lovable with Claude Code, Codex or Cursor, that agent ships changes with the Eurobase MCP server or CLI.

• Best for: a Lovable app whose data already lives in a Supabase EU region, run at a fixed monthly price.
• Price: a Free plan with 2 projects, then Starter at €10 and Pro at €20 a month + VAT. Usage isn't billed today: work over a limit is refused, apps on V8 isolates and Functions stop until the monthly reset, and containers and static sites keep serving.
• What it lacks: managed Postgres, preview deployments and a sign-in service, so the backend stays with Supabase. A Worker reaches Supabase over HTTPS only, and the default @supabase/ssr cookie setup doesn't reach the server without the change in the cookies docs. ISO 27001 and SOC 2 certification is under way, not finished. GitHub and GitLab Inc. become US subprocessors when you connect them.

Start with the TanStack Start guide and Eurobase + Supabase.

2. Lovable hosting with a European backend

If moving is more than you need, stay on Lovable and choose Europe when you turn the backend on. That choice can't be changed later. On Business and Enterprise workspaces, an admin can make Europe the default for new projects. Enterprise plans can also keep AI model requests on EU endpoints with a setting called EU inference, and can ask for country regions such as Germany. Lovable says it holds SOC 2 Type 2 and ISO 27001.

• Best for: apps you're still changing every day in the Lovable editor.
• Price: publishing to lovable.app is free on all plans and a live site doesn't use credits on its own. Backend activity and AI features use Run credits. Custom domains need a paid plan.
• What it lacks: a frontend kept in Europe, and a way to move an existing project's backend to another region. On the Free plan, TanStack Start apps are capped at 1,000 server requests per project per 10 seconds.

3. Scalingo

Scalingo treats any repository with package.json at its root as Node.js. Lovable's guide gives the recipe for a plain Node.js host: build with NITRO_PRESET=node-server, then start node .output/server/index.mjs, which reads the PORT variable. On Scalingo that start command goes in a Procfile or the start script of package.json.

• Best for: teams that want the app and a managed database with one French company.
• Price: containers from €7.20 a month for 256 MB, €8.64 in its SecNumCloud region, both excl. VAT, with a 30-day free trial. Its smallest Postgres is €7.20 a month excl. VAT for 512 MB and 10 GB.
• What it lacks: a direct home for the Lovable backend. Scalingo's Postgres is plain PostgreSQL, so auth, storage and edge functions would need new code.

4. Sliplane

Sliplane runs containers built from a GitHub repository or pulled from a registry. It detects the framework or builds from a Dockerfile, and Lovable's guide describes a two-stage Dockerfile that ends by running the Nitro server on Node.js 22.

• Best for: a Lovable app plus a self-hosted Supabase or other containers on a single bill.
• Price: €9 per server, excl. VAT.
• What it lacks: a Europe-only region list. Servers can also run in the US and Singapore, so confirm the location before you create one.

5. Supabase for the backend

Supabase is where Lovable sends you when the backend leaves. Its EU regions are Frankfurt, Stockholm, Ireland and Paris. Lovable's database export is a compressed PostgreSQL archive that includes the auth schema, so users keep their passwords after pg_restore, though signed-in users must sign in again.

• Best for: the backend half of every option above except staying on Lovable.
• What it lacks: frontend hosting. Storage files, edge function code, secrets, scheduled jobs and sign-in providers all move by hand.

For other places to run the backend, see European Supabase alternatives.

Moving a Lovable app, step by step

1. Connect Git sync and check that the latest version is in the repository.
2. Create a Supabase project in an EU region, restore the Lovable export with pg_restore, and upload the storage files.
3. Deploy edge functions from supabase/functions/ with the Supabase CLI, set their secrets and recreate scheduled jobs.
4. Deploy the repository to the new host and test sign-in, uploads and one server function on its default address.
5. Replace remaining AI and connector calls, then move your domain and keep the Lovable project until traffic has settled.

Frequently asked questions

Can I keep editing in Lovable after hosting elsewhere?

Yes. Git sync works both ways, so Lovable keeps changing the repository and your host deploys every push to the branch you choose.

Do I need a paid Lovable plan to leave?

No. Git sync is on every plan. Only the .zip download and custom domains on Lovable's own hosting need a paid plan.

Can I put a Lovable app on a static host?

Only an older React and Vite app. A TanStack Start app renders on the server, so a host that serves files alone won't run its pages, server functions or API routes.

Is Lovable a European company?

Lovable's terms are with Lovable Labs Incorporated and are governed by Delaware law. Read EU region vs EU company if a contract asks for an EU provider.

For the same question about Bolt and v0 apps, see hosting for AI-built apps. For more TanStack Start hosts, see TanStack Start hosting in Europe.

Sources

• Lovable deployment and ownership options, Deploying and hosting outside Lovable, How Lovable hosts your app, Lovable built-in backend, Lovable EU inference, Lovable custom domains, Lovable pricing and Lovable terms
• Supabase regions
• Scalingo pricing and Scalingo Node.js docs
• Sliplane pricing
• Eurobase TanStack Start guide, Eurobase Workers, Eurobase + Supabase, Eurobase cookies, Eurobase plans, Eurobase pricing and Eurobase subprocessors