Home / Compare builders / SPOE vs Base44 / How to export from Base44How to export your code from Base44, and keep it runningOn the Builder plan or higher, Base44 exports the code as a ZIP from the editor's More actions menu, or syncs it both ways with a new GitHub repository. Your data comes out separately, one CSV per table, and your app users as a CSV too. Base44's own docs say the exported code still relies on Base44 to run: there is no self-hosting, and running fully outside it means replacing its backend with your own.From Base44's own docs, read 2026-10-22. Every step links to the page it is from.Download a ZIP (Builder plan or higher)

On a computer, with edit access: open the app editor, click the More actions icon at the top right and select Export project as ZIP. (source)

Click Download ZIP. (source)

To run it locally: npm install, then npm run dev. It still talks to the Base44 backend. (source)

Your data, a table at a time

In the app editor, click Dashboard, then Data, and select a table. (source)

Click the More actions icon, then Export. The table downloads as a CSV; do the same for each one. (source)

For your app's users: click Dashboard, then App Users, then the More actions icon at the top of the page, and select Export to CSV. (source)

Sync to GitHub (Builder plan or higher, app owner)

In the app editor, click Dashboard, then the GitHub icon at the top right, then Connect to GitHub, then Connect GitHub. (source)

Click Authorize Base44 Builder, choose the GitHub account or organization and the repositories it can reach, then click Install. (source)

Create a repository for the app: choose its owner, enter a name and click Create Repository. (source)

To work on a clone: npm install, install the CLI with npm install -g base44@latest, then run base44 login and base44 link. base44 dev runs a local backend with the app; base44 dev --remote uses the live backend, and its writes go to production data. (source)

Eject a copy with the CLI

Run npm install -g base44@latest, then base44 eject, and pick the app and a destination folder. (source)

Build the copy with base44 build, so its new Base44 app ID goes into the bundle. (source)

What comes out

A standard React project built with Vite, set up the same way as the code in the Code view and in a connected GitHub repository. (source)

Your frontend code, your backend functions and your data structure: each table's fields and permissions. (source)

Backend functions are TypeScript running on Deno. (source)

package.json includes @base44/sdk, and vite.config.js a Base44 plugin. (source)

Your data comes out on its own, one CSV per table. (source)

Its Terms say you own the code and apps the platform generates, subject to Base44's own earlier IP. (source)

What stays behind, and needs replacing

The exported code still relies on Base44 to run: Base44 calls the ZIP a copy of your code, not a way to move your app off Base44. (source)

Base44's pages disagree on that: its pricing page says "Nothing is locked to the platform." (source)

The code uses the Base44 SDK to reach your app's backend on Base44 for data, logins, backend functions and integrations, wherever it runs, and it works on the live app's data. (source)

Your data, secrets, app users and version history are not in the ZIP. Secrets and app users stay in Base44. (source)

There is no self-hosting: the database, login system and integrations cannot run on your own servers. To run fully outside Base44, you replace them with your own backend and change the code that uses them. (source)

The database is Base44's own NoSQL store. (source)

With GitHub sync, the tables are managed in Base44 and are not in the repository. (source)

An ejected copy gets a new backend on Base44 with an empty database: the schemas are copied, the data is not. (source)

App users are not copied into a clone and cannot be imported into one. (source)

Cancel a paid plan and the workspace drops to the free plan at the end of the billing period: at most 5 apps stay published, and you may lose features only paid plans have. (source)

Base44's Terms let it delete all your data and generated code at any time after your subscription ends, or for any other lawful reason. (source)

Not on Base44's pages

Whether the ZIP includes sign-in settings, agents or connector configurations.

What the App Users CSV holds, and whether anything in it lets your users sign in somewhere else, such as password hashes.

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

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