Host your Lovable app on your own hosting

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.

The website costs $5 a month on aidrop.it’s Starter plan, or $20 a month on Pro if you want your own domain. On Lovable, a custom domain needs its Pro plan, from $25 a month as of October 2026 (Lovable’s plans). Your backend stays on Lovable Cloud, under your Lovable account.

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 is the master key to your backend. It opens everything and ignores those access rules, so 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

• An aidrop.it account — start free: a 7-day trial, no card. To keep it running, Starter at $5/month is enough for the website alone; your own domain needs Pro at $20/month. See the pricing page.
• A Lovable project connected to GitHub, as Lovable’s GitHub sync guide explains. The sync works both ways and is available on all Lovable plans.
• 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

Replace the parts in angle brackets before you paste.

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. Row Level Security must stay on. If the server part needs a secret, ask me for it, store it with project_secret_set, list its name in required_secret_names and read it at run time. Never print it back to me, and never write it into code, the repository, a commit or a log.

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 > Redirect URLs) or in Supabase.

What your agent does to move the Lovable site

1. Reads your code and checks which kind of Lovable app it is. Apps made from 13 May 2026 on include a small server part; older ones are plain website files.
2. Writes a short build recipe that fits aidrop.it’s rules and saves it with your code.
3. Builds the app on aidrop.it and waits until it runs. A blank page or a failed build usually means the public backend values did not reach the build, so that is what it checks first.
4. 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 More, then Cloud, then Users, then Auth settings, expand Advanced, and add your new link (and later your domain) under Redirect URLs. With your own Supabase project, add them in its sign-in settings instead. Lovable’s sign-in settings guide shows the screen.

Connect your domain (optional, Pro plan). 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.

Once the site runs here, you can also add an AI chatbot to your website: a chat bubble that answers visitors from your own FAQ, with its AI key kept out of your Lovable code.

Check the moved site

• 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

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 13 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. Moving that backend is a separate job, which Lovable’s hosting outside Lovable guide covers. Keep your Lovable account: it still runs your backend.

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

Yes, if your database’s access rules are switched on. Supabase made the publishable key for browsers and says it is safe to show; the access rules decide what it can reach. The secret key skips every rule, so it must never be in website code. Your agent is told to keep it out.

Is hosting outside Lovable cheaper?

For the website alone, often yes: $5 a month here at an aidrop.it address, or $20 with your own domain, against Lovable’s Pro plan from $25 a month for a custom domain. But if you keep building in Lovable, you still pay for the Lovable plan you build on. The move is about owning where the site runs, not only the price.

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”.

Related

• Put a landing page online
• Move an app from Base44 or Replit
• Add an AI chatbot to your website
• Bring a repository you already have
• Quickstart
• All playbooks