Deploy Lovable

Deploy Lovable sites with VibeDeploy

Name: VibeDeploy
Brand: VibeDeploy

Lovable builds full-stack React and Tailwind apps from prompts. VibeDeploy gives them a real production URL with custom domains, automatic SSL, and EU hosting.

Deploy your Lovable site See pricing

Why VibeDeploy for Lovable

Lovable provides a lovable.app address and supports custom domains on paid plans. Its frontend is delivered globally, while Lovable Cloud offers a Europe region for backend data. VibeDeploy is an independent hosting option for the exported frontend, served from Belgium.

shield_lock

EU-resident hosting

Your exported frontend is served from Belgian infrastructure. Supabase, Lovable Cloud and other external services keep their own hosting regions and data-processing arrangements.

language

Custom domain on every plan

Bring your own domain on any plan, the 14-day trial included. A Let's Encrypt certificate is issued and renewed for you at no extra cost.

bolt

Built for AI iteration

Re-deploy as fast as you regenerate: every push from Lovable to GitHub rebuilds the site, an AI connected over MCP can publish for you, or you upload a build. Built for the prompt-and-ship loop.

How to deploy a Lovable site

1
Sync your Lovable project to GitHub
In Lovable, open Project settings > Git > GitHub and click Connect. Lovable creates a private repository and keeps it in two-way sync. Git sync is included on every Lovable plan, Free too, and it is the route we recommend. Download codebase needs a paid Lovable plan and gives you the project source, not a finished build.
2
Start your VibeDeploy trial
Create an account at vibedeploy.be. The 14-day trial needs no credit card and covers one site with your own domain, automatic SSL and a restore point before every deploy, hosted in Belgium. Solo costs €4 a month after the trial.
3
Connect the repo, or upload a build
In the dashboard, create a site from GitHub and pick the repository: VibeDeploy runs npm run build and redeploys on every push. Uploading works too, but upload the built dist folder (after npm install and npm run build), not the raw project ZIP, which the deploy guard rejects as an unbuilt project. Projects on TanStack Start, Lovable's default for new projects since 13 May 2026, render on a server instead and run as a container app; see the questions below.
4
Add your custom domain
Open Web Addresses in the dashboard, add the domain under "Use your own domain" and create the records it lists: a CNAME for a subdomain, an ALIAS or A record for the bare domain, and a TXT record that proves ownership. Click Verify, and the Let's Encrypt certificate follows automatically.
5
Keep iterating in Lovable
Every change Lovable pushes to GitHub rebuilds and redeploys the site, so editing in Lovable stays your release process. Changes made outside the repository are replaced by the next build, so keep the repository as the source.

Guides for Lovable

Lovable hosting at a glance

How Lovable's default hosting and a generic alternative compare to VibeDeploy.

Feature	Lovable default / generic alt	VibeDeploy
Custom domain	Pro plan and up	Every plan, the trial included
Hosting region	Global frontend; Europe available for Cloud backend	Exported frontend in Belgium
Restore an earlier version	Code version history; very old versions cannot be restored	One click in the dashboard, 3 to 30 days by plan
Server-rendered (TanStack Start) apps	Hosted by Lovable	Container next to the site (deploy_app)
Try before you pay	Free plan on a lovable.app address	14-day trial with your own domain, no card
GDPR DPA included	Business and Enterprise; US contracting entity	Every paid plan; EU operator

Common questions about deploying Lovable

Does Lovable's Free plan include a custom domain?expand_more

No. Lovable's plan comparison lists custom domains on Pro, Business and Enterprise; on the Free plan the site stays on its lovable.app address. The workaround is to host the code elsewhere: sync the project to GitHub, which works on the Free plan, deploy it on VibeDeploy and attach your domain there with automatic SSL. Lovable remains your editor, the domain and the hosting are yours.

My Lovable custom domain is not working. What should I check?expand_more

Start with the DNS records. Leftover A, AAAA or CNAME records from a previous host keep an old site showing, and a stray AAAA record can also block the certificate, because Let's Encrypt validates over IPv6 first. If Cloudflare runs your DNS, set the records to DNS only (grey cloud): a proxied record answers with Cloudflare's addresses. Lovable ties Cloudflare errors 1001 and 1003 to that proxy, and Cloudflare's error 1000 means a proxied record points at a Cloudflare address. CAA records must allow the certificate authority, and Lovable's docs allow up to 72 hours for propagation. A domain that should point at VibeDeploy must not also point at Lovable.

Can I keep using Lovable while hosting elsewhere?expand_more

Yes, that is the usual setup. Keep Git sync on and every change Lovable pushes to the repository redeploys your site on VibeDeploy. Lovable's Publish button keeps publishing to the lovable.app address only, so unpublish that copy once your domain works if you want one public version. A Lovable Cloud backend keeps running at Lovable and keeps using your workspace's Cloud credits.

How do I export the code from Lovable?expand_more

Connect the project to GitHub under Project settings > Git > GitHub: Lovable creates a repository and keeps it in two-way sync on every plan, Free included, and every later edit arrives as a push that can redeploy. Paid plans can also use Download codebase for a one-off ZIP. Either way you get source code, which VibeDeploy builds from the repository or accepts as a built dist folder.

How do I get an SSL certificate for my Lovable site?expand_more

You don't manage the certificate yourself. Once your custom domain verifies in VibeDeploy, a Let's Encrypt certificate is requested, installed and renewed automatically. There is nothing to buy and nothing to renew by hand. If your domain has CAA records, one of them must allow letsencrypt.org.

Can I use a domain I bought through Lovable?expand_more

Yes. A domain bought through Lovable stays registered there and uses Lovable's nameservers, so you edit its records in Lovable. Disconnect it from the Lovable project first, which removes the records Lovable created. Then, in Lovable, open Workspace settings > Workspace domains > Configure > DNS records and add the records your VibeDeploy dashboard lists; Lovable offers no ALIAS type, so use the A record for the bare domain. Only workspace admins and owners can change them.

Does VibeDeploy run server-side code from Lovable?expand_more

It depends on the stack. A project on Lovable's older React + Vite stack builds to static files that VibeDeploy serves as they are, and its calls to Supabase or Lovable Cloud keep going from the browser to that backend. A project on TanStack Start, Lovable's default for new projects since 13 May 2026, renders pages on a server: your AI can run that Node.js server as a container next to the site with the MCP tool deploy_app, isolated with gVisor, within up to 6 services, 2 CPU and 2 GiB of memory per site. Container data is not yet included in snapshots.

Will deploys break when Lovable updates the project?expand_more

No. Every deploy is kept as a version, with a restore point taken before it, so a bad regeneration is undone with one click in the dashboard. The restore window is 3 days on the trial, Solo and Maker, 7 days on Studio and 30 days on Business. Database changes are not part of that restore: they stay with Supabase or Lovable Cloud. One exception: an upgrade to TanStack Start in Lovable is pushed like any other change, and a static build of a TanStack Start project is not a working site. Run the upgrade on a new branch in Lovable (VibeDeploy only builds the branch you picked) and have your AI start the container with deploy_app before you merge it.

How is this different from hosting on Vercel?expand_more

VibeDeploy runs on its own cluster in Belgium under EU jurisdiction, so the exported frontend stays in the EU, served from that single region rather than a global edge network. Each plan has one flat price with its sites, storage and bandwidth listed, and there is no overage billing.