Lovable built it. Now give it an address.

From Lovable to your own URL

A Lovable export is a Vite + React app that builds with npm run build into dist/ — which happens to be slew's defaults. Turn on Lovable's GitHub sync, then:

$ slew git connect you/your-app --output dist
$ slew domains add app.yourdomain.com
Live at https://app.yourdomain.com

From then on it's push-to-deploy. The GitHub sync is two-way, so you can keep prompting in Lovable and every change lands as a commit and goes live — or hand the repo to a developer and let them take over, without the app moving again.

Built for what Lovable generates

Lovable apps route client-side with React Router, and that's the part most static hosts make you configure. On slew, deep links serve your app shell out of the box while missing assets still return real 404s — no rewrite rules, no config file. VITE_* environment variables are set once with build scope and compiled in on every deploy, the way Vite expects.

Keep Supabase, move the frontend

Lovable backends run on Supabase, not on Lovable — so moving the frontend changes nothing server-side. Set your Supabase URL and publishable key as build-time env vars, add the new domain to Supabase's auth redirect allow-list, and logins work from the first deploy.

The production half

Once it's yours, it gets the platform's normal feature set: a custom domain on EU DNS and CDN, an expiring preview URL on every pull request, instant rollback to any earlier deploy, and cookieless analytics measured at the edge — visitor numbers without adding a script or a consent banner to the app Lovable wrote.

Frequently asked

Can I keep editing in Lovable after moving the hosting?

Yes. Lovable's GitHub sync keeps working both ways — edits in Lovable become commits, commits deploy on slew. Hosting elsewhere doesn't disconnect the builder.

Does client-side routing work, or do visitors get 404s on deep links?

It works with zero config. Extensionless paths fall back to your app shell, so /dashboard/settings loads the app; paths with file extensions never fall back, so a missing asset is a real 404 instead of index.html served as CSS.

What happens to my Supabase backend?

Nothing — it stays on Supabase. Set VITE_SUPABASE_URL and the publishable key as build-scope env vars, and add your new domain to the auth redirect allow-list in Supabase so logins return to the right origin.

What does it cost?

A Lovable app fits the free plan (3 projects, 50 GB traffic). Paid plans are flat euros — €9, €24, €99 — with no build-minute meter and no per-seat fees.

Where does my app physically live?

Storage and servers at Hetzner in Germany, CDN and DNS at Bunny in Slovenia, company incorporated in the EU. No US parent, no CLOUD Act exposure.