Do You Own Your Code on Floot? Getting Your App, Database and Files Out (2026)
Short answer: yes. On Floot you own your app's code, its data and its intellectual property, on every plan. You can export the database on any plan, download the full project on a paid plan, and run the app somewhere else.
The longer answer matters more, because "you own your code" is easy to say and easy to misread. This post lists exactly what you can take out of Floot, what it costs, what does not come with it, and what a move to your own hosting involves. If you are choosing an AI app builder and lock-in worries you, this is the page to read before you start.
What you own
Floot's Security and data page states it plainly: the code, the app's data and the IP are yours. Floot claims no rights to what you build.
Two things are also yours that are easy to forget:
- Your conversations. If you build through Claude or ChatGPT, your build history lives in your own Claude or ChatGPT account, not inside Floot.
- Your domain. A custom domain you connect stays at your own registrar. Pointing it somewhere else is a DNS change you make yourself.
What you can export, and on which plan
| What | How | Plan |
|---|---|---|
| Database | Services → Data → open a table → cog icon → Export → Download Database. A standard Postgres dump (.sql.gz) | Every plan, including Free |
| Database structure only | Same dialog, tick Structure only: tables, indexes, constraints and functions, without rows | Every plan |
| Full project code | Project name menu → Get Code → Download as ZIP | Paid plans (Pro is $25 a month) |
| Code kept in sync with a folder on your computer | Get Code → Folder Sync, in Chrome or Edge | Paid plans |
| Uploaded files and images | Listed under Services → Storage; no bulk download. Your AI assistant can copy them to your own storage | Every plan |
A few details worth knowing:
- The database export is a plain
pg_dumpwithout owners or grants, so it restores into any PostgreSQL database: Supabase, Neon, AWS RDS, Railway or your own server. It runs in the background however large the database is, and the download link works for 24 hours. You can run up to five exports per database a day. - The code is ordinary TypeScript and React, built with Vite, with a Node.js server. The zip includes a
server.tsand a README for running it outside Floot. - Exports happen in your browser, not through your AI assistant. Your assistant can read any file and query the database for you, but the download itself is a button on floot.com.
- Export the database while your hosting balance is positive. If it runs out, the database cannot be exported until it is paid, even before your apps are taken down.
There is no GitHub sync
This is the honest difference from some other builders. Lovable, for example, syncs a project with a GitHub repository in both directions. Floot does not connect to GitHub.
What you can do instead, on a paid plan, is keep a folder on your computer in sync with the project (Get Code → Folder Sync) and commit that folder to Git yourself. Floot shows what would change in each direction and nothing moves until you approve it. Or download the zip and push it wherever you like.
If a live two-way GitHub sync is a must for you, weigh that. If what you need is a copy of your code and data you can always take with you, Floot gives you that.
What does not travel with the export
The exported code is your source, not a complete copy of the running app. Plan for these:
- Floot's built-in services. Sign-in, file storage, email, scheduled jobs, push notifications, realtime updates and Floot AI are provided by Floot's platform. Code that uses them imports from
@floot/..., and those imports will not resolve outside Floot, so the project will not build until you replace them. The self-hosting guide lists each one and what to use instead (your own auth provider, S3 or Cloudflare R2, Resend or SES, a cron or queue, and so on). The easiest way is to ask your AI assistant to swap them while the project is still on Floot, then export. - Your API keys. The export lists the environment variables your app expects but leaves the secret values empty. You fill them in.
- Uploaded files. Images and files in Floot's storage are not in the zip. Copy them to your own storage and update the paths.
- Pre-rendering. The exported server renders pages in the browser. If you need server-side rendering on your own host, you build it.
How backups work while you stay
On paid plans, Floot keeps a 7-day backup of the built-in database. Going back to an earlier point is done by Floot support: send the project link and the date and time you want. Checkpoints in the editor restore your code, never your data, so download an export before a risky change to your data.
Moving a live app off Floot
If people are using the app while you move it, do it in this order so no data is written to the old database after you copy it:
- Get the exported code building and running on your own host first, against a test database.
- Stop new writes: remove any custom domain from the Floot project, then unpublish the app. The project, its database and its files stay intact.
- Export the database and restore it on your side. The export is one snapshot, so it is consistent.
- Point your domain's DNS at the new host.
Your users will notice two things: everyone signs in again, because you generate a new sign-in secret, and anyone who connected a Google or Microsoft account through Floot's built-in integration connects it again.
FAQ
Do I own the code I build on Floot's free plan?
Yes. Ownership does not depend on the plan. What the free plan does not include is downloading the full project; exporting the database is available on every plan.
Can I export my Floot app to GitHub?
Not directly, because Floot does not sync with GitHub. On a paid plan, keep a folder on your computer in sync with the project and commit it, or download the zip and push it to any repository.
Can I host a Floot app myself?
Yes. Export the code and the database, replace the built-in Floot services your app uses, fill in your API keys and run it on any Node.js host. The self-hosting guide walks through each step.
Is my database backed up?
On paid plans, yes: a 7-day backup that Floot support can restore from. On any plan, you can download your own export whenever you want a copy.
What happens to my app if I stop paying?
Publishing a web app is free on every plan, so moving to the free plan does not unpublish your app by itself. Hosting is metered separately: if a busy app uses up its hosting balance, it is taken down until the balance is paid. Paid extras stop too: a custom domain needs a paid plan, and so does downloading the code. Download your code and a database export before you downgrade if you want a copy.