4 min readBy The VibeDeploy team

Lovable Custom Domain: Deploy Your Site in 5 Minutes

Move a Lovable project off its lovable.app subdomain and onto your own domain, step by step, with EU hosting and automatic SSL. Five minutes end-to-end.

Lovable's default lovable.app subdomain is fine while you're iterating. The moment you show the site to a customer, that subdomain starts to look unfinished. This guide covers the five-minute path to a custom domain on EU-hosted infrastructure. For the full picture of Lovable custom domain hosting, including SSL, free-plan limits and a feature comparison, see the dedicated tool page.

What you'll need

  • A Lovable project that builds successfully
  • A domain you own (or one you'll buy in the next 5 minutes)
  • A free VibeDeploy account

That's it. No CLI installation required. For faster redeploys, connect the VibeDeploy MCP server in Cursor or Claude.

Step 1: Export from Lovable

In your Lovable project, push to GitHub or download the project as a ZIP. Either path works.

If you use the GitHub option, you'll get a connected repo Lovable updates as you edit. That's useful later for auto-redeploys.

If you download the ZIP, you'll need to repeat this step every time you change the project in Lovable.

Step 2: Build locally (or skip and let Git do it)

If you're using the GitHub path, skip to Step 3. The CI build runs automatically.

If you downloaded the ZIP:

unzip my-lovable-project.zip
cd my-lovable-project
npm install
npm run build

You'll get a dist/ folder. That's what you upload.

Step 3: Upload to VibeDeploy

Sign in to VibeDeploy. Click New Site. Either:

  • Drag-and-drop the dist/ folder into the upload area, or
  • Connect the GitHub repo if you went that route. VibeDeploy detects Vite (Lovable's default) and runs npm run build automatically.

Either way, you get a *.vibedeploy.be URL within 30 seconds. Open it. The site should look identical to the Lovable preview.

Step 4: Add your custom domain

In the site settings, click Domains, then Add domain. Enter the domain (e.g. mysite.com).

VibeDeploy gives you DNS records to add at your registrar. Two flavors:

  • Apex (mysite.com): an A record pointing to VibeDeploy's edge IP.
  • Subdomain (www.mysite.com): a CNAME pointing to proxy.vibedeploy.be.

Add both if you want the apex and the www subdomain to work. Most registrars take 1 to 5 minutes to propagate.

Once DNS resolves, VibeDeploy issues a Let's Encrypt SSL certificate automatically. The site goes live on HTTPS.

Step 5: Set up automatic redeploys for future Lovable iterations

This is the step most people skip and then regret.

You have two clean ways to keep redeploying as you iterate in Lovable:

  • Connect your GitHub repo. Lovable can push to GitHub. Connect that repo to VibeDeploy and every push auto-redeploys, with no manual upload.
  • Let an AI agent deploy. Connect the VibeDeploy MCP server (https://mcp.vibedeploy.be/mcp) in Claude or Cursor, or export your deploy guide from the dashboard and paste it into ChatGPT or Gemini. Then you just say "redeploy" and the agent ships the latest build.

Why this matters: if you keep iterating in Lovable and pushing to GitHub, VibeDeploy auto-redeploys on every push, so your custom domain always shows the latest version without you re-typing deploy steps.

Verify

Open https://mysite.com in a fresh browser tab. You should see your Lovable site, served over HTTPS, on your custom domain.

Common things that go wrong:

  • DNS hasn't propagated. Wait a few more minutes. Use dig mysite.com to verify.
  • Mixed content warnings. Lovable sometimes generates http:// references for images or fonts. Search the source for http:// and replace with https://.
  • Custom domain on Lovable's side too. Lovable also lets you set a custom domain pointing at their hosting. Don't do both at once. Pick one (VibeDeploy in this case) and remove the Lovable side.

What you get

  • Custom domain (mysite.com instead of mysite.lovable.app)
  • HTTPS automatic, no manual cert management
  • EU hosting (Belgian data centre, GDPR-friendly)
  • Backup retention up to 30 days on paid plans
  • Auto-redeploy on every Lovable update if you used the GitHub path

What this doesn't do

  • Doesn't replace Lovable's AI editor. Keep iterating in Lovable.
  • Doesn't move your Supabase or external API. Those continue running where they were.
  • Doesn't migrate the project off Lovable. The source still lives in Lovable's editor; VibeDeploy just hosts the build output.

Cost

VibeDeploy's 14-day free trial covers 1 site with custom domain so you can try it at no charge. After the trial, the Maker plan is €15/month. No per-bandwidth charges.

For a deep comparison with other Lovable hosting options, see VibeDeploy vs Lovable hosting. For the broader pattern, see the main deploy guide.

From the VibeDeploy team

Ship your AI-built site in minutes

VibeDeploy hosts your AI-built websites in the EU with custom domains, automatic SSL, and a 14-day free trial that gets you online today.

Related reading

7 min readPillar

How to Deploy AI-Built Websites in 2026: 5 Tools, 5 Steps

Deploy sites from Lovable, Bolt.new, Cursor, v0, or Claude in five steps. Finish with a live 2026 website on EU hosting, HTTPS, and your own custom domain.

hostingdeploymentai
4 min read

Vibe Deploying: What It Means and How It Works

Vibe deploying is shipping a website by talking to an AI instead of running a build pipeline. What the term covers, how MCP makes it work, and how to try it free.

vibe-codingdeploymentmcp
5 min read

Launch a landing page with a working signup form

Validate an idea this week: let an AI build your landing page, host it on your own domain and collect signups through a form relay, no backend or mail service needed.

landing-pageformsvalidation
6 min read

/home/workdir/artifacts/index.html: How to Get Your File Out

Claude saved your site to /home/workdir/artifacts/index.html. That path lives in Claude's sandbox, not on your computer. Get the file out and put it on a live URL.

claudeartifactssandbox
6 min read

From Claude Code in your terminal to a live site

Claude Code writes a finished site straight into your project folder. Here is how to get it live: the MCP one-liner, the magic-file fallback, and the redeploy loop.

claudeclaude-codemcp
6 min read

AI-website online zetten: de zes valkuilen

Je AI-website online zetten lijkt de makkelijke laatste stap, maar juist hier gaat het vaak mis. Zes valkuilen die een AI-site tegenhouden, en hoe je ze vermijdt.

ai-websiteonline-zettenhosting
5 min read

The Lovable-to-production checklist

The pre-launch checklist for Lovable sites: export path, build output, forms, analytics, DNS, SSL, staging and rollback. Eight checks, one boring launch.

lovableproductionchecklist
6 min read

Claude Artifact Custom Domain: Download, Host, and Launch

Download or copy your Claude artifact code, host it outside Claude, and connect a custom domain with EU hosting and automatic Let's Encrypt SSL included.

claudeartifactscustom-domain
4 min read

What is MCP hosting? Deploying a site via MCP

MCP hosting lets an AI agent deploy your site to a live URL, no manual upload. How deploy-via-MCP works and how to connect it in Claude, Cursor or Windsurf.

mcphostingdeployment
5 min read

Localhost to Live URL: Turn Your Project into a Public Link

Turn a localhost project into a shareable live HTTPS URL. Compare a temporary tunnel with permanent EU hosting, then connect your own domain and HTTPS.

localhostdeploymenthosting
5 min read

Bolt.new Project Download: Export Your Project as a ZIP

Download your Bolt.new project as a ZIP, build it locally, and deploy it to a production URL with EU hosting, a custom domain, and automatic SSL included.

boltdeploymenthosting
6 min read

GDPR AI Hosting: What AI-Built Sites Need in the EU

What GDPR AI hosting really requires: why EU-resident infrastructure matters for AI-built sites, and how to set up a compliant deploy without sales calls.

gdprhostingeu