Skip to main content
Deploy your app with managed Postgres and a custom domain. Customers use prod, which runs the versions you release. Dev and previews use invite-only sign-in while you review changes. For customer sign-up and sign-in, add User accounts. Requires the app’s source in a GitHub repository with a Dockerfile that serves on 0.0.0.0:$PORT. Dockerfiles has one to copy for Next.js, Rails, Django, FastAPI, and Express. The examples use Next.js on port 3000.

Set up your agent

For Claude Code, also run floo skills install --path .claude/skills/floo. Cursor, Codex, and other agents: Agent setup.

Agent prompt

Paste into your agent. Replace storefront with your app name.

floo.app.toml

floo.app.toml
[app] access_mode = "public" opens prod to anyone. The two [environments.<env>] overrides keep dev and previews invite-only. Dev and prod each get their own Postgres with separate credentials, injected as DATABASE_URL. The first prod release creates the domain.

Deploy to dev, then release to prod

Every push to the default branch deploys to dev at https://storefront.getfloo.app, signed in. When a version is ready for customers, replace owner/repo with your GitHub repository and release it:
Once the release’s commit is live in dev, floo deploys it to prod at https://storefront-prod.getfloo.app. A push never changes prod. For an app floo hosts, run floo promote --app storefront instead.

Point your domain at prod

The first prod release prints the DNS records for shop.example.com. Read them again at any time:
Publish the records at your DNS provider. floo activates the domain once they resolve. See Custom domains for apex domains and troubleshooting.

Verify

The curl returns your page with no redirect to sign-in. Opening the dev URL in a private window shows floo’s sign-in page.

Next steps

Custom domains

DNS records, activation, apex domains, and per-service domains.

Production environments

Releases, per-environment env vars, and the two URLs.

Releases and rollbacks

Put the previous version back when a release goes wrong.

Preview environments

Review each pull request on its own URL and database branch.