Get started
Either paste this into your agent or install it yourself.Why floo
Agents can write the app. The hard part is making what they wrote into software a real person can actually use. Without floo, your agent stitches together a hosting provider, an auth service, Postgres, Redis, object storage, a cron scheduler, a worker runtime, a domains layer, and an observability tool. A separate dashboard for each. A separate bill for each. A separate API your agent has to learn, each with its own edge cases. With floo, all of it lives in one config. One CLI. One dashboard. One rollback. One bill. One platform to rule them all. The apps your team builds on floo match the SaaS they’re replacing. Real sign-in. Background jobs. Scheduled tasks. Custom domains. Live logs. A rollback button. Not a scrappy internal clone. A real product. One config covers Postgres, Redis, storage, cron, workers, custom domains, rollbacks, and live logs.See a real floo.app.toml
See a real floo.app.toml
What you can ship
Public products
SaaS, APIs, consumer apps on a custom domain. Live logs and analytics built in, so you see what real users are doing, not guess.
Internal tools
Your team signs in with work email and your app knows every user. Build tools personalized to each teammate.
Private betas and demos
Track per-company sign-ins and usage. See which prospects came back for a second look, close more deals.
Start building
Ship my first app
Three commands and your app is live.
floo init, floo apps github connect, git push. Every push after that deploys automatically.Understand the model
The four pillars that make floo safe for agents to operate. Config in the repo, deploys from GitHub, CLI as the surface.
Learn the CLI
Every command, flag, and error code, with copy-paste examples your agent can parse and script against.