People are shipping software like never before. Agents write code in minutes, and teams want to ship that code to real users today — not next quarter after a devops project. floo is the infrastructure layer for that velocity. CLI-first, config-as-code, with managed auth, dev/prod environments, and agent-native observability built in.Documentation Index
Fetch the complete documentation index at: https://getfloo.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Why teams choose floo
Managed auth, in one config line
Set
access_mode = "accounts" and floo handles sign-in end-to-end — email, Google, GitHub, domain allowlists. No auth infra to build, no WorkOS account to manage. This is how non-devs on your team can actually use the apps you ship.Dev and production, out of the box
Every app has a dev URL and a production URL.
git push goes to dev. Promote when it’s ready. No staging cluster to maintain.Observability for the whole team
Live logs, per-service analytics, alerts to Slack or email, and signed incident webhooks that route production errors straight to your agent or on-call.
Change control, when you need it
Every deploy is a release. Tag it, promote it, roll back to any previous version in one command.
Team access and SSO
Per-app grants, org roles, domain-based allowlists. Enterprise SSO via SAML/OIDC for larger teams.
Budget controls
Spend caps, per-app budgets, and hard stops so a runaway loop or a growth spike doesn’t turn into a surprise bill.
Common use cases
Internal tools
Ship a lookup tool, dashboard, or admin panel that your teammates sign into with their work email. No devops project, no access-control setup, no support ticket to provision access.
Sales demos with usage tracking
Give prospects a real, branded demo app. They sign in with their work email via managed auth — you see exactly who logged in, from which company, and when they came back.
The differentiator: managed auth
The single thing that unlocks everything above is floo managed auth. Toggle one config value and floo provisions a full OAuth flow — hosted sign-in page, JWT issuance, refresh tokens, domain allowlists, a dashboard that shows which users have signed in and when.git push gives you an app that anyone on your team (or your customers, or your prospects) can sign into — without you building auth.
This is what makes floo usable by non-devs. A salesperson can use the admin tool an engineer shipped this morning. A prospect can open your demo and see their own data. An analyst can use the dashboard an agent built for them — all signed in, all audited, all with no extra work from you.
Start with an internal tool
The fastest path to value for most teams.
Ship a sales demo
Turn a demo into a measurable signal of intent.