Host your Lovable app on your own hosting

Move the website part of your Lovable app to hosting you control, with your own link and domain. Your AI agent does the moving; your data stays where it is.

This page moves the website part of an app you built in Lovable to aidrop.it. You paste one paragraph into your AI coding agent (Claude Code, Codex or Cursor). It takes your code from GitHub, builds it and gives you a working link. The build itself takes minutes. Your database and user sign-in stay on Lovable Cloud (or your own Supabase). Only the website moves.

What you will have at the end

Your Lovable app running at its own secure link, and on your own domain if you want one.
The same pages, logins and data as before, because the site still talks to the same backend.
A copy of the code you own, which any agent can change later.
A way to publish new versions: keep editing in Lovable, then ask your agent to rebuild.

Words you will meet

GitHub is a website that stores code. Lovable can copy your app’s code there and keep it up to date.
Backend is the hidden part of the app: database, user accounts, file storage. For most Lovable apps it is Lovable Cloud, which runs on Supabase.
Publishable key is the public key your site uses to talk to the backend. Browsers see it anyway. It is safe in the code because your database’s access rules decide what it can reach.
Secret key (Supabase calls it the service role key) opens everything and ignores those rules. It must never be in your website’s code.
Build means turning your code into a finished app the internet can open.
Domain is your own address, like myapp.com.

What you need

A Lovable project connected to GitHub, as Lovable’s GitHub guide explains. The sync works both ways.
An aidrop.it plan that runs apps (the free plan runs nothing). A website like this fits the smallest size. Plans are on aidrop.it.
Your agent connected to aidrop.it. See the quickstart.
Access to your domain’s settings, if you want your own address.

Say this to your agent

Move the website part of my Lovable app to aidrop.it. The code is
on GitHub: <owner/repository>. The backend (database, sign-in,
storage, edge functions) stays on Lovable Cloud / Supabase. Do not
move or change it.

Read aidrop.it's runtime rules before you write anything and
follow them. Build from my GitHub repository if aidrop.it can see
it; if it can't, give me the link to install aidrop.it's GitHub
app. Put the Service in a new aidrop.it Project called
"<app name>".

Work out which kind of Lovable app this is. An older React + Vite
app builds to plain files: serve them as a static site, and send
every unknown path to index.html so page links and refreshes work.
A newer TanStack Start app (Lovable, May 2026 on) has a server
part: build it with Nitro's node-server preset and run it as a
Node app. Its outgoing requests must go through aidrop.it's proxy:
use Node 22.21 or newer with NODE_USE_ENV_PROXY=1.

The build cannot see Project secrets. The public Supabase URL and
publishable key must be in the repository (Lovable keeps them in
.env). Keep them there. Never put a service role or other secret
key in frontend code. If the server part needs a secret, store it
as a Project secret and read it at run time.

When it runs, tell me the link, which kind of app it was, and
exactly which sign-in addresses I must add in Lovable
(Cloud > Users > Auth settings > Advanced) or in Supabase.

What your agent does

Reads your code and checks which kind of Lovable app it is. Apps made from mid-May 2026 on include a small server part; older ones are plain website files.
Writes a short build recipe that fits aidrop.it’s rules and saves it with your code.
Builds the app on aidrop.it and waits until it runs. If it fails, it reads the error, fixes it and builds again.
Gives you the link and the sign-in addresses to add in Lovable.

After it runs: two things only you can do

Allow sign-in from the new address. Lovable only lets users sign in from addresses it knows. In Lovable, open Cloud, then Users, then Auth settings, then Advanced, and add your new link (and later your domain). With your own Supabase project, add them in its sign-in settings instead. Lovable’s guide.

Connect your domain (optional). Say “connect myapp.com to this site”. Your agent tells you one record to add where you bought the domain, then switches the domain on. If the domain pointed to Lovable before, that record is replaced. Your Lovable copy keeps its lovable.app address.

Check that it works

Open the link. The home page loads.
Click through a few pages, then refresh one of them. It should not show “not found”.
Sign in with a test account. If it fails, check the sign-in addresses above.
Add or change something. It also appears in Lovable, because the data is shared.

When something goes wrong

What you see	What to tell your agent
A blank white page	“The page is blank. Check that the public Supabase values reached the build.”
“Not found” when you refresh a page	“Refreshing a page gives not found. Send unknown paths to the app.”
Sign-in fails or sends you back to lovable.app	Add the new link in Lovable’s sign-in settings, then try again.
A Lovable edit does not appear	“Rebuild the site from the latest code on GitHub.”
The build keeps failing	“Read the build log, fix the cause and tell me what it was.”

FAQ

Can I host a Lovable app somewhere other than Lovable?

Yes. Lovable says you own your code and can host it wherever you choose. Older Lovable apps are plain website files that any host can serve. Apps made from May 2026 on include a server part, so the host must run a small server. Your backend can stay on Lovable Cloud.

Does my database move with the website?

No. The database, user accounts, file storage and backend functions stay on Lovable Cloud, and the moved website keeps using them. Lovable supports moving that backend only to Supabase, managed or self-hosted. Keep your Lovable account: it still runs your backend.

Is it safe that the publishable key is in my code?

Yes, if your database has access rules turned on. Supabase made the publishable key for browsers and says it is safe to show. Your data is protected by those rules, called Row Level Security. The service role key skips every rule, so it must never be in website code.

Can I keep building in Lovable after moving?

Yes. Lovable keeps syncing your edits to GitHub. On aidrop.it a new version goes live when your agent rebuilds, not on its own. So the habit is: edit in Lovable, then tell your agent “rebuild my site”.