Do I own the code my AI builder generated?

On the major platforms (Lovable, Bolt, v0, Replit), yes - their terms grant you ownership of generated code. Owning it in practice means holding a copy outside the platform: sync or export the project to your own GitHub repository. Until you do, your product exists at the pleasure of one vendor's uptime, pricing and account decisions.

How do I export my app from Lovable?

Connect Lovable's GitHub integration (Settings -> GitHub -> connect and create repository). Lovable then two-way syncs code to a repo you own. From there you can run it locally (npm install, npm run dev), keep editing in Lovable, or deploy the repo independently. Note the Supabase database is separate - your Supabase project is already yours; keep its keys and take regular backups.

Where should I deploy my exported app?

For most exported React/Vite apps: Cloudflare Pages (generous free tier, commercial use allowed, no egress fees) or Azure Static Web Apps (free tier with custom domains). Next.js apps from v0 fit Vercel naturally, or Azure/Cloudflare with adapters. The key decision inputs are commercial-use terms and bandwidth pricing - see our hosting costs guide.

If I export, can I still use the AI builder afterwards?

Usually yes. Lovable's GitHub sync is two-way, so you can keep prompting in Lovable while owning the repo. Bolt and v0 are more one-directional - after export you continue with AI coding tools like Cursor or Claude Code against your own repository, which is the natural graduation path anyway.

Own your AI-built app: export it, then deploy it yourself

By Carl Mills - cloud & DevOps engineer • Published 9 July 2026 • Last updated 9 July 2026

TL;DR

You own the code your AI builder generated - but only on paper until a copy lives in your own GitHub repository. Lovable: connect the GitHub integration (two-way sync). Bolt: download/export or push to GitHub from the editor. v0: use the GitHub sync or download the project. Then your app can run anywhere - Cloudflare Pages or Azure Static Web Apps for most exports (both have free tiers that allow commercial use), Vercel for Next.js. Do this before you have paying customers, not after your builder changes its pricing.

Why bother? Your app currently has a landlord

Every one-click AI builder is also a hosting company, and your app lives in their building: their subdomain, their deploy pipeline, their pricing, their account-suspension button. That's a fine trade for a prototype. It's a bad place for a product with users, because platform risk is real and boring: pricing restructures, feature-gating, acquisitions, outages, or simply outgrowing the editor.

The fix costs an afternoon and is entirely non-destructive: get the code into a repository you control, prove it runs off-platform, and only then decide where it should live.

Exit routes, platform by platform

Platform	How you get the code	Two-way?	What stays behind
Lovable	GitHub integration: Settings → GitHub → create repo (auto-syncs)	Yes - keep prompting in Lovable	Nothing critical - Supabase is already a separate account you own
Bolt.new	Download project zip, or push to GitHub from the editor	Partially - re-import is manual	Netlify deploy settings if Bolt created them
v0	GitHub sync from the project menu, or download	Mostly one-way	Vercel project settings/env vars - copy them out
Replit	Git pane → connect GitHub → push	Yes	Replit DB/secrets - export data and re-home secrets

Platform UIs move - if a menu has shifted, search the platform's docs for "GitHub" or "export". The capability exists on all four as of July 2026.

The 5-step ownership drill

Export/sync to a private GitHub repo you own. Free, takes minutes.
Copy out every environment variable from the platform's settings into a password manager entry - these are the keys the code needs to run anywhere.
Prove it runs locally: npm install → npm run dev with a .env built from step 2 (never commit it). If it runs on your machine, no platform owns you.
Back up the data separately. The code export doesn't include your database. Supabase: dashboard backups or pg_dump; Replit DB and platform stores: use their export, then schedule it monthly.
Deploy a copy somewhere neutral (below) - even unlinked to your domain. A proven second home turns every future platform surprise into a shrug.

Where to deploy the exported app

Your export is...	Easiest independent home	Why
React/Vite SPA (typical Lovable, Bolt)	Cloudflare Pages or Azure Static Web Apps	Free tiers allow commercial use; connect the GitHub repo and both build on every push. Azure SWA adds free custom domains + SSL
Next.js (typical v0)	Vercel Pro, or Cloudflare/Azure with adapters	Vercel is native for Next.js; Cloudflare (OpenNext) escapes egress pricing at scale
Node server (some Replit/Bolt)	Railway, Fly.io, or Azure Container Apps	Real servers from ~$5/month; Container Apps scales to zero

Full cost comparison, free-tier traps and spend caps: see what hosting your AI-built app actually costs.

After the export: the graduation path

Owning the repo unlocks the grown-up toolchain without abandoning AI coding: point Cursor or Claude Code at the repository, add the git safety net so sessions can't destroy work, and run the platform security checklist for wherever you came from - Lovable, Bolt or v0 - before you point customers at the new home.

Frequently asked questions

Do I legally own the generated code?

On the major builders, yes - their terms assign generated code to you. Practical ownership is the part this guide fixes: a copy in your repo, keys in your vault, data in your backups.

Will exporting break my app?

Exporting is read-only - nothing changes on the platform. The risk is the opposite: apps that were never exported breaking when the platform changes something.

Can I keep using Lovable/v0 after exporting?

Lovable's sync is two-way, so yes, seamlessly. v0 and Bolt are effectively one-way - after export you'd continue with repo-based AI tools, which is the natural next step anyway.

What about my custom domain?

Domains are portable by design - you own them at the registrar. When you re-home the app, update the DNS records to point at the new host; both Cloudflare and Azure walk you through verification.

Keep going

Run your platform's security checklist: Lovable • Bolt • v0
Compare real hosting costs before picking the new home.
Want the export, hosting and CI/CD done with you in an afternoon? That's a fixed-scope engagement - book a scoping chat.