Self-hosting

You own 100% of your Floot app's code and data. If you want to host your app on your own infrastructure, you can export everything and deploy it yourself.

When to self-host

• You need to meet specific compliance or data residency requirements

• You want full control over your infrastructure

• You're migrating away from Floot

• You want to run the app in an air-gapped environment

What you can export

Asset	How to export
Code	Project name dropdown → Get Code
Database	Right pane → Data → Floot database → cog icon → download pg_dump

How to self-host

1. Export your code

1. Open your project

2. Click the project name dropdown in the top-right

3. Select Get Code

4. Download the zip file containing your full source code

2. Export your database

1. In the right pane, click Data

2. Select Floot database

3. Click the cog icon

4. Download the pg_dump file

3. Set up your database

1. Upload your pg_dump file to your own PostgreSQL database

2. Note the connection string for the next step

You can use a managed Postgres service like Supabase, Neon, AWS RDS, or Railway.

4. Configure environment variables

The exported code includes an env.json file. For security reasons, this file is not pre-populated — you'll need to generate or retrieve the values yourself.

JWT secrets:

Generate a value with:

node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"

Paste the generated value into the appropriate field in env.json.

Database connection:

Fill in the connection string for your own PostgreSQL database as you can't use Floot's database in self-hosted environments.

External services:

Retrieve your API keys for any third-party services and fill in the corresponding values.

Floot-managed services

Some built-in Floot services are tied to Floot's infrastructure and will not work in self-hosted environments. If your app uses any of them, you'll need to migrate to an alternative — either ask Floot to help migrate before you export, or migrate it yourself after downloading the codebase.

Service	What to do instead
Floot OAuth	Configure your own auth provider
Floot Storage	Migrate to an object storage provider like Cloudflare R2 or Cloudinary
Floot AI	Use your own API key with the AI provider of your choice
Floot Realtime	Use a pub/sub service (e.g. Pusher, Ably, Redis pub/sub) or remove the feature

5. Build and run

The exported code is a Node.js application. Build and start the service with:

npm install -g pnpm
pnpm install
pnpm vite build
pnpm tsx server.ts

You're free to adjust this to work with other frameworks or deployment targets.

Hosting options

You can deploy to any hosting provider that supports Node.js:

Things to consider

• API keys — You'll need to set up your own API keys for any third-party services

• Floot-managed services — Floot OAuth, Floot Storage, Floot AI, and Floot Realtime do not work in self-hosted environments. Migrate to alternatives (auth provider, R2/Cloudinary, your own AI API key, a pub/sub service) before or after exporting

• Updates — Self-hosted apps won't receive updates from Floot; you'll need to maintain the code yourself

• Support — Floot support covers the Floot platform, not self-hosted deployments

Questions?

• Live chat — Click the support button on floot.com

• Discord — discord.gg/sUFNJ3FW8G

• Email — [e-mail]