Home / Compare builders / SPOE vs Bolt / How to export from BoltHow to export your code from Bolt, and keep it runningBolt downloads any project as a ZIP of its files at any time: click the project title, then Download, and run it with npm install && npm run dev. GitHub sync is two-way, with Bolt committing each working change for you. Your database rows come out separately, table by table as CSV or JSON, and Bolt's pages do not say whether a downloaded app keeps working on Bolt's database after you leave.From Bolt's own docs, read 2026-10-22. Every step links to the page it is from.Download a ZIP

To run it on your computer, install Node.js first. (source)

In Bolt, open the project, click its title in the top left, then click Download. (source)

Unzip the file, open a terminal in the project folder and run npm install && npm run dev. (source)

Connect GitHub

You need an individual GitHub account, and to be the project's owner. (source)

In a project, click the GitHub icon in the top right, then Log in to GitHub, then Authorize. (source)

Click Install the GitHub App, choose All repositories or Only select repositories, then click Install & Authorize. (source)

Back in the project, click the GitHub icon, enter a name for the new repository, click Create repository, then Start building. From then on, Bolt commits for you. (source)

Your data

For Bolt Database rows: in the project, click the database icon at the top center, then a table. (source)

Select the rows (the header checkbox selects them all), click Export or Copy, and pick CSV or JSON. Do the same for each table. (source)

To move the whole database (Pro or Teams, as the Supabase organization's owner): connect Bolt to your Supabase account, click the database icon, then the Advanced tab, then Claim, and finish the steps in Supabase. (source)

What comes out

A ZIP of the project, to work on outside Bolt in your own code editor. (source)

JavaScript only: a Node.js back end, and any JavaScript framework that runs in the browser on the front end. (source)

GitHub keeps a copy outside Bolt with the full history of changes. (source)

Database rows come out from the Tables screen as CSV or JSON, apart from the code. (source)

On Pro or Teams, a claimed database shows up as a project in your own Supabase account. (source)

Bolt says the code is yours to use for any legal purpose, commercial use included. (source)

What stays behind, and needs replacing

Bolt Cloud is the back end and hosting built into Bolt. (source)

Bolt Database includes sign-in, server functions, secrets, user management and file storage. (source)

Bolt runs the database servers and the hosting for you. (source)

Moving the whole database into your own account means claiming it into Supabase, which needs Pro or Teams. (source)

Bolt's pages disagree on that: its database overview says there is no supported way to migrate an existing Bolt database to Supabase. (source)

File storage: Bolt shows the buckets but cannot yet show or manage the files inside them. (source)

Netlify, Bolt's other hosting option, cannot host a database or a traditional back end, Bolt says, and for those it says to stay on Bolt hosting. (source)

In an unpublished project, Bolt may pause the database after six days or more of low use. (source)

Deleting a project deletes its Bolt database too. (source)

If StackBlitz, which runs Bolt, ends an account other than for cause, there are 30 days to export; keeping your own backups is up to you. (source)

Not on Bolt's pages

What the ZIP or the repository holds beyond the project files: the database schema, sign-in settings, server functions or secrets.

Whether a downloaded app that uses Bolt Database keeps working after you leave, after a plan lapses or after the project is deleted.

Which plans include GitHub sync.

Docker or docker compose files for an exported project.

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

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