Can you host and own the code an AI app builder writes?

Ownership and portability are different questions

Ownership is a legal statement about who holds rights to the generated output. Portability is a practical question about whether you can get the code out and run it somewhere else. A tool can be generous about the first and restrictive about the second, and the second is the one that will actually affect your Tuesday.

Ask both, separately, and get the answers from documentation rather than a sales conversation.

What each tool documents

v0 states in its FAQ that "Vercel doesn't own the code generated based on your queries and prompts", and code can be exported and deployed elsewhere. It also notes that output may be similar to other users' output — a caveat worth reading if you assume generated code is unique to you.

Lovable says the creator owns the code, and documents zip download from the code editor or project settings, plus transfer to GitHub or GitLab with two-way sync.

Base44 gates the exit. Its documentation states that "GitHub 2 way sync requires the Builder plan or higher", and that once connected, "GitHub sync is permanent. You can't disconnect or transfer the project back to Base44." A CLI eject command clones an app into a local project.

Replit is a development environment, so the code is present in your workspace throughout; its Agent documentation does not address export terms specifically.

sup3rapp has not published its export terms yet. That is a real gap and it is stated on every comparison page rather than hidden — we will publish it on the facts page before we publish anything else about it.

What "exportable" is worth in practice

Getting a zip is not the same as being able to run the thing.

Generated applications usually depend on a managed backend, an auth provider, environment variables, and a database that belongs to the platform. Exporting the frontend code while the data layer stays behind is a partial exit — you have the code and none of the reasons it worked.

The useful question is: if this company disappeared next month, what would I have? A repository you can npm install and run against your own database is one answer. A folder of components that expect a proprietary backend is a different one.

What to check before you commit

• Does the tool state, in writing, that you own the generated output?
• Can you export on the plan you are actually on, or only on a higher one?
• Is the export a one-time snapshot, a two-way sync, or a one-way door?
• Does the export include the backend and schema, or only the frontend?
• If you export, what happens to the hosted version and the data in it?

None of that requires a lawyer. It requires reading the docs page for ten minutes before you spend a month building. If a tool makes those answers hard to find, that is itself an answer.

What to do the day you export

Do it once, early, before you need to. Export the code into a fresh directory, install dependencies, and try to run it against a database you control. You will find out in an afternoon whether the export is a working application or a pile of files, and that is a much better day to find out than the day you have to leave.

Write down what was missing. Usually it is environment variables, a schema, or a service the app assumes exists. That list is your real exit plan, and it is worth keeping current.

Then keep exporting on a schedule. An export you performed once and never repeated is a snapshot of an app you no longer have.