We built export because you should be able to leave

Every AI app builder can produce a prototype. The question that matters a month later is what you can do with it once you want to stop paying the tool, or once you hire an engineer who wants a repository, not a chat history.

What "export" means here

Two things, both shipped:

• Download as ZIP. The workspace collects the project's source files and hands you an archive. For a cloud project it collects them from your server.
• Push to GitHub. With your own personal access token, the Builder creates or updates a repository and pushes the project. From then on it is ordinary Git.

There is no proprietary runtime in the export. The browser workspace builds Vite + React + TypeScript; full-stack cloud projects add a Node server and use a normal PostgreSQL database. The self-host guide is short because there is nothing special to do.

Why this shapes everything else

Once leaving is easy, the product has to earn its place every month. That is a good constraint to build under. It is why cloud projects get a dedicated server with PostgreSQL installed on it rather than a slice of a shared database, and why the cloud page documents what runs where instead of asking you to trust a diagram.