Home / Compare builders / SPOE vs Lovable / How to export from LovableHow to export your code from Lovable, and keep it runningOn a paid plan, Lovable saves the whole project as a ZIP from its code editor; on every plan, Free included, it syncs the code to a new private GitHub repository. Your database comes out separately, through a database export, and stored files are downloaded by hand. The code keeps calling Lovable's backend, AI and connectors until you move the backend to your own Supabase project and replace the rest.From Lovable's own docs, read 2026-10-22. Every step links to the page it is from.Download a ZIP (paid plans)

Open the code editor with the Code tab in the project toolbar. (source)

Click Download codebase at the bottom of the file panel to save the whole project as a .zip. The Download codebase section in Project settings → Git does the same. (source)

Sync to GitHub (every plan)

As a workspace owner or admin, open Workspace settings → Git → GitHub → Add connection (or the same under Project settings), then click Add account. (source)

In the GitHub window, choose the account or organization, pick All repositories or Only select repositories, then click Install & Authorize. (source)

In Project settings → Git → GitHub, click Connect next to the connection. Lovable creates a new private repository and starts two-way sync. (source)

Clone the repository with the HTTPS, SSH or GitHub CLI address shown in Project settings → Git → GitHub. (source)

Check its README and package.json for what to install and the commands that start the app. (source)

Your data, as a separate export (every plan)

If the backend is paused (idle, out of credits or at a credit limit), wake it first. (source)

Go to More → Database → Manage → Settings and click Export data under Export project data. In the Database card, click Export, then Start export. (source)

When Lovable emails you, download the export, a compressed PostgreSQL archive for pg_restore, from More → Storage, and download your stored files from there too. (source)

Run it somewhere else

A TanStack Start app, whose package.json lists @tanstack/react-start under its dependencies: set VITE_SUPABASE_URL and VITE_SUPABASE_PUBLISHABLE_KEY, build with NITRO_PRESET=node-server npm run build, then start node .output/server/index.mjs with SUPABASE_URL, SUPABASE_PUBLISHABLE_KEY and your secrets set. (source)

An older React and Vite app: run npm ci, then npm run build with the same two VITE_ variables set, and serve dist/ with a fallback to index.html. (source)

To leave Lovable's backend: create a Supabase project, apply the migration files in order, restore the export with pg_restore, set up the sign-in providers again, copy the storage files, set the secrets, deploy the Edge Functions with npx supabase functions deploy, test, then point .env and supabase/config.toml at the new project. (source)

Before you switch, find and replace the app connector calls, the AI calls and the built-in backend URL. Then move your custom domain and unpublish the app on Lovable. (source)

What comes out

The ZIP and GitHub both carry the app's source, with its configuration files and the database migration files stored in the project. (source)

New apps made from 13 May 2026 (22 June 2026 in Enterprise workspaces) use TanStack Start, which renders pages on the server; older ones use React and Vite unless upgraded. Lovable offers no choice of framework or database. (source)

With the built-in backend, the repository also holds the backend code: Edge Functions in supabase/functions/ and migrations in drizzle/migrations/ and supabase/migrations/. (source)

The database export holds the whole database, structure and data, including your users' accounts and their password hashes. A single table also downloads as CSV. (source)

The database export is on every plan, Lovable's changelog said when it launched on 3 July 2026. (source)

Lovable's guide gives example Dockerfiles to adapt, and Lovable writes Docker and Docker Compose files when asked, but says it cannot run or test Docker builds: you verify them yourself. (source)

What stays behind, and needs replacing

The records in your database and the files in storage: neither the ZIP nor GitHub includes them. (source)

A copy run on your own machine still reads and writes the live backend, so records you change there change real data. (source)

Secrets are write-only in Lovable: a saved value can never be viewed again, only replaced or deleted. For a key you no longer have, Lovable says to generate a new one at the service that issued it. (source)

AI features run through Lovable's AI gateway on your credits, and app connector connections are not exported: each is replaced with your own provider account or integration. (source)

Sign-in providers are set up again: managed OAuth and automatic token refresh only work on Lovable's built-in backend. (source)

The backend can move to managed or self-hosted Supabase only. Plain PostgreSQL or another provider means building the missing pieces yourself, and Lovable does not support it. (source)

Out of credits, the built-in backend pauses, and the data cannot be reached or exported until it runs again. (source)

A database export is limited to 15 GB of database and a 5 GB file, one every 24 hours. (source)

Your lovable.app address stays with Lovable and keeps serving the version you last published there. (source)

Not on Lovable's pages

Whether the ZIP download includes the .env file.

How SPOE differs

The whole project. A SPOE export is the whole project: the code, the Docker files that start it and, for a full-stack app, its database migrations, with a signed provenance manifest and the verifier inside. It starts with docker compose up, with nothing of SPOE inside, so there is nothing of ours to replace.

Signed and recorded. Every export is signed by SPOE: an Ed25519-signed provenance manifest, with a record of it on APIR's hash-chained log. spoe.ai/verify checks every file and that spoe.ai signed it, in your browser, so anyone can prove the code is exactly what was exported.

Yours for good. Your first payment of any size unlocks export permanently, whether or not you ever pay again. Locked or not, the code is always visible and copyable in the editor.

Coming from Lovable. SPOE does not import a Lovable project. If the app is live and you can show the site is yours, with a DNS record, a file on it or a tag in its pages, Bring your site copies the page at that address, with its styles and pictures, into a SPOE project to keep building; the data and the logic behind it are not copied. Otherwise, describe the app to SPOE and it is built as a Next.js, Fastify and Postgres project you hold. Keep your Lovable export either way: it is yours.

SPOE vs Lovable · Lovable vs Bolt · Lovable vs v0 · Lovable vs Replit · Base44 vs LovableExport guides for Bolt · Base44 · v0 · ReplitHow it works · Features · Models · Pricing · Docs · Blog · Handle checker · App ideas · Arcade · Compare builders · Verify an export · Developer API · Start freeThis page needs JavaScript to run the app itself. Everything above is a plain description of it.