Self-hosting

Export your code and database and run your Floot app on your own infrastructure.

You own 100% of your Floot app's code and data. If you want to host it yourself, you can export everything and deploy it wherever you like — code download is included on every paid plan.

When to self-host

You need to meet specific compliance or data residency requirements
You want full control over your infrastructure
You are migrating away from Floot
You need to run the app in an air-gapped environment

What you can export

Asset	How to export
Code	Project name dropdown → Get Code (included on paid plans)
Database	Right pane → Data → Floot database → cog icon → download `pg_dump`

How to self-host

1
Export your code
Open your project, click the project name dropdown, choose Get Code, and download the zip containing your full source. Code download comes with every paid plan — if you are on the free plan, upgrading unlocks it.
2
Export your database
In the right pane click Data, select Floot database, click the cog icon, and download the pg_dump file.
3
Set up your own database
Restore the pg_dump into a PostgreSQL database you control, then note its connection string. Managed options like Supabase, Neon, AWS RDS, or Railway all work.
4
Configure environment variables
The exported code includes an env.json file. For security it is not pre-populated — you supply the values.
JWT secrets — generate one with:
```
node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"
```
Database connection — fill in your own PostgreSQL connection string. Floot's database is not reachable from self-hosted environments.
External services — paste in the API keys for any third-party services your app uses.
5
Build and run
The export is a Node.js application:
```
npm install -g pnpm
pnpm install
pnpm vite build
pnpm tsx server.ts
```
Adjust freely to fit your own framework or deployment target.

Floot-managed services

Some built-in services are tied to Floot's infrastructure and will not work once you self-host. If your app uses any of them, migrate before or after exporting — you can ask Floot to do the migration for you while the project is still on Floot.

Service	What to do instead
Floot OAuth	Configure your own auth provider
Floot Storage	Migrate to an object storage provider like Cloudflare R2, S3, or Cloudinary
Floot AI	Use your own API key with the AI provider of your choice
Floot Realtime	Use a pub/sub service (Pusher, Ably, Redis pub/sub) or drop the feature
Floot Email	Point the app at your own provider — Resend, SendGrid, Postmark, SES
Scheduled & background jobs	Run them with your platform's scheduler (cron, EventBridge, a queue worker)

Things to consider

API keys: You will need to set up your own keys for every third-party service.
Updates: Self-hosted apps do not receive updates from Floot. Maintaining the code is on you.
Support: Floot support covers the Floot platform, not self-hosted deployments.