Take Lovable output live on EU infrastructure
Lovable is a fast way to build; it should not dictate where you host. VibeDeploy runs the export on EU infrastructure with your own domain, git-triggered redeploys and snapshots, so the project outlives any single tool subscription.
Why VibeDeploy for Lovable
Lovable combines editing and hosting, with custom domains on paid plans. Its published frontend is delivered globally; a Europe Cloud region applies to backend data. Export to VibeDeploy when you want to manage frontend hosting independently in Belgium, while keeping Lovable for editing.
Under EU jurisdiction
Serving happens from EU data centres with a DPA on every paid plan. For European clients and GDPR-sensitive projects, the data path is short and inspectable.
Your domain, decoupled from the builder
Attach any domain with automatic SSL on every plan. If you ever stop paying for Lovable, the frontend keeps running, because the hosting was never Lovable's.
Redeploys match your iteration speed
Push from Lovable to GitHub and every commit redeploys, or let an MCP-connected agent publish updates. Each deploy leaves a restore point, so a regeneration you dislike is undone in the dashboard with one click, inside your plan's restore window.
The Lovable to production workflow
- 1
Get the project out of Lovable
Lovable's Git sync, part of every Lovable plan including Free, puts the project in a private GitHub repository of yours and keeps both sides current. Paid Lovable plans add a codebase download, but that ZIP holds source files, so it still has to be built before anything can be served.
- 2
Open a VibeDeploy trial
An account at vibedeploy.eu starts a 14-day trial covering one site; no credit card is asked for. Your own domain, automatic SSL and hosting in Belgium are part of the trial, and Solo costs €4 per month once it ends.
- 3
Publish the export
Create a site from GitHub in the dashboard and select the repository: each push from Lovable triggers a fresh build and deploy. For manual releases, build locally with npm install and npm run build and drop in the dist folder; a raw project ZIP is refused as unbuilt. TanStack Start projects, Lovable's default since 13 May 2026, are the exception: their server has to run, which on VibeDeploy means a container your AI starts.
- 4
Move it onto your own domain
Enter the domain in the "Use your own domain" section of the Web Addresses page and copy the listed records into your DNS: a CNAME, or an ALIAS or A record for a bare domain, routes the traffic, and a TXT record proves ownership. After verification the Let's Encrypt certificate is issued for you.
- 5
Keep the Lovable loop running
With the GitHub connection in place, regenerating in Lovable and letting it push is the whole release process. A hotfix published another way is overwritten by the next build from the repository, so commit it there as well.
Further reading on Lovable
Lovable hosting at a glance
How Lovable's default hosting and a generic alternative compare to VibeDeploy.
| Feature | Lovable default / generic alt | VibeDeploy |
|---|---|---|
| Own domain | Paid Lovable plans (Pro and up) | Every plan, the trial too |
| Where the site is served | Global delivery; backend region selectable in Lovable Cloud | Belgium, single region |
| Going back to an earlier release | Editor history; the oldest versions are preview-only | Dashboard restore, 3 to 30 days depending on plan |
| Data processing agreement | Business and Enterprise, US contracting entity | Every paid plan, EU operator |
| TanStack Start server | Runs on Lovable hosting | Container next to the site |
Common questions about deploying Lovable
Is a custom domain possible while I stay on Lovable's Free plan?expand_more
Not through Lovable: its plan table reserves custom domains for Pro, Business and Enterprise, and Free projects keep their lovable.app address. Git sync, however, works on Free, so you can deploy the synced repository on VibeDeploy and attach your own domain there with a certificate that renews itself, while Lovable stays your editor at no cost.
Why is my domain still not live?expand_more
Look for records that point elsewhere. An old A, AAAA or CNAME entry from a previous host keeps the old site visible, and an AAAA entry can derail certificate issuance too, since Let's Encrypt connects over IPv6 first. Cloudflare-managed zones need the records set to DNS only (grey cloud), because a proxied record returns Cloudflare's addresses. CAA entries have to permit the certificate authority, and Lovable's documentation allows up to 72 hours for propagation.
Can Lovable stay my editor once the site is hosted in the EU?expand_more
It can, and that is the point of the split. Lovable pushes each change to the synced repository and VibeDeploy rebuilds from it. Publishing inside Lovable only updates its lovable.app copy, which you may want to unpublish so a single version stays public. A Lovable Cloud backend remains hosted by Lovable, in the region picked when Cloud was enabled, and is billed through your workspace credits.
Will server-side code from a Lovable project run on VibeDeploy?expand_more
That depends on the template. React + Vite projects, Lovable's older stack, compile to static files that VibeDeploy serves directly; their Supabase or Lovable Cloud calls go from the visitor's browser and keep working. TanStack Start projects render on a server, which VibeDeploy runs as a gVisor-isolated container beside the site once your AI deploys it with deploy_app (per site: up to 6 services, 2 CPU, 2 GiB). Snapshots do not cover container data yet.
What happens to my deploy when Lovable regenerates the project?expand_more
Normally nothing breaks: each deploy becomes a separate version, preceded by a restore point. If a regeneration goes wrong, bring back the previous version from the dashboard in one click, within 3 days on the trial, Solo and Maker, 7 on Studio or 30 on Business. Your database is not part of that restore. The case to plan for is Lovable's switch to TanStack Start: the sync carries it into the repository like any edit, but the result no longer runs from static files. Have Lovable make the switch on a fresh branch, since only the connected branch gets deployed, and merge it once the container is running.
Where does this sit relative to hosting on Vercel?expand_more
VibeDeploy is operated from Belgium under EU law and serves from one region there, not from a global edge. Pricing is a flat amount per plan, without overage billing for bandwidth.
Does a domain bought through Lovable work here?expand_more
Yes. Lovable stays its registrar and DNS host, so the records are edited in Lovable. Disconnect the domain from its Lovable project, which clears the records Lovable created, then, in Lovable under Workspace domains, Configure, DNS records, enter the records your VibeDeploy dashboard shows; only workspace admins and owners can do that. Lovable's record types do not include ALIAS, so point the bare domain with the A record.
Who handles the SSL certificate for the custom domain?expand_more
The platform does, end to end. A verified domain gets a Let's Encrypt certificate that installs and renews itself, with no purchase and no manual renewal. If the zone carries CAA records, allow letsencrypt.org.
What does exporting a Lovable project actually involve?expand_more
Turning on Git sync, available on any Lovable plan, or downloading the codebase on a paid plan. Both give you source code rather than a ready site: VibeDeploy builds a React + Vite project from the repository and runs a TanStack Start project as a container.
Is there EU hosting for Lovable sites?expand_more
Yes. Lovable Cloud offers a Europe region for backend data, but published frontends are delivered globally. VibeDeploy serves your exported frontend from Belgium with a DPA on paid plans. Any external backend or API retains its own region and terms; exporting the frontend does not migrate those services.
More tool workflows
Hosting comparisons
Put your Lovable work into production
14-day free trial, no credit card. Your own domain and snapshots included. Runs on EU infrastructure.