Home / Compare builders / SPOE vs v0 / How to export from v0How to export your code from v0, and keep it runningv0 pushes your project's code to a new private GitHub repository on every plan, Free included, and sends later changes as pull requests. A chat's code also downloads as a ZIP from the project menu or through v0's API. The data stays with the database provider you added, such as Neon or Supabase, and environment variables and domains stay in the linked Vercel project.From v0's own docs, read 2026-10-22. Every step links to the page it is from.Push to GitHub (every plan)

Open the Project menu (...) → Settings → GitHub, and select Connect. (source)

Under Git Scope, select the GitHub account or organization that will own the repository, and enter a repository name. (source)

Select Create Repository. v0 creates a private repository and pushes the project's current code to it. (source)

Later changes land on a v0 working branch. To bring them to your base branch, create or open the pull request and merge it; Publish does this too, then deploys to Vercel. (source)

Keep the repository: once connected, it is the source of truth for the code, and deleting it may make the code unrecoverable. (source)

Download a ZIP

From the project menu, use Download ZIP. v0's changelog names it; no docs page gives the exact clicks. (source)

For one file: open the Code tab, select the file in the file tree, then Download file at the right of its header. (source)

Through the API

Create an API key in v0's settings. (source)

Call GET https://api.v0.dev/v2/chats/{chatId}/files/download with the header Authorization: Bearer and your API key. It downloads the chat's source files as a ZIP archive. (source)

Or with API v1: GET /v1/chats/{chatId}/versions/{versionId}/download, with format=zip or tarball. includeDefaultFiles=true adds package.json and the config files. Its curl example saves the archive with -o version-files.zip. (source)

What comes out

A Next.js project in React, TypeScript, Tailwind CSS and shadcn/ui. (source)

The back end is in the same codebase, as Next.js server actions and API routes. (source)

Since 8 June 2026, a new app that needs a database and sign-in is scaffolded with Neon, Drizzle and Better Auth. (source)

Through API v1 you get only the generated source files, unless you ask for includeDefaultFiles=true. (source)

No Built with v0 badge in published apps or generated repositories, since 14 August 2026. (source)

Vercel says it does not own the code v0 generates. (source)

What stays behind, and needs replacing

A v0 account is a Vercel account. (source)

Environment variables live in the connected Vercel project and are managed there. (source)

Databases are separate hosted services, such as Neon, Supabase, Upstash and Vercel Blob: adding one opens an account with that provider, managed through the Vercel Marketplace. (source)

AI features in the apps v0 builds use Vercel AI Gateway by default. (source)

Services reached through Vercel Connect, in beta, use short-lived tokens that Connect issues and refreshes at runtime: they never appear in your code, environment variables or chat. (source)

Custom domains come from the Vercel project and team. (source)

Not on v0's pages

Whether environment variable values or a .env file come with the ZIP or the repository.

A way to export the rows in your database through v0: they sit with the provider.

Which plans can use Download ZIP or the API.

Docker files, or how to host an exported app away from Vercel.

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 v0. SPOE does not import a v0 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 v0 export either way: it is yours.

SPOE vs v0 · Lovable vs v0 · Bolt vs v0Export guides for Lovable · Bolt · Base44 · 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.