Code, data, and exports

Do I own the code?

Completely — code, data, and IP. See Security and data.

How do I download or export my code?

There is no export tool on the connector, so your assistant cannot produce the download for you. It can read any file in the project, so it can copy specific code into your chat, but the runnable zip has to come from the browser.

Open your project on floot.com, click the project name in the top bar, and choose Get Code. The download includes instructions for running it, and comes with every paid plan. If you plan to host it yourself, read Self-hosting first.

Can I import an existing codebase into Floot?

Floot cannot run your existing codebase as-is — it rebuilds it. What you get is a Floot-native app that looks and behaves like the original, not a port, so third-party API keys and data migrations still have to be redone by hand.

There is no import tool on the connector — nothing takes a repository or an archive and turns it into a Floot project. Handing your assistant a zip does not import anything.

What works instead: if your assistant can already read your source — Claude Code, Codex, and Cursor all run on your machine — point it at the repository and ask it to rebuild the app in Floot page by page. It writes the pages, endpoints and schema with the same tools it would use on a new project. Give it the schema and one page at a time rather than the whole repo at once.

Can I export my database?

Yes, but it is a browser step — there is no connector tool that produces a database dump.

1. Open your project on floot.com and go to the Services tab, then Data.
2. Select your Floot database and open a table.
3. Click the cog icon in the table header and download the pg_dump.

If the download fails, contact support with your project URL and we can generate one for you.