the cloud for agentic software
the way agents ship production software.
describe what you want. your coding agent builds it. push to main and floo handles the rest. your app is live, stays live, and updates every time you make a change.
02 · built for agents
a cloud built for agentic software.
agents write config, not commands. every infra change is a git commit. you review, you merge, you ship. your agent can't go rogue because it was never given the controls.
agent prompt
“add a worker that processes the uploads queue. point it at managed postgres. concurrency 4.”
agents write config, not commands
your agent edits floo.app.toml. it cannot run a command that deletes your database or spins up a $10k cluster. files only.
every change is a git commit
review before it ships. revert if it breaks. git log is your full infrastructure history, not a dashboard you have to screenshot.
the repo is the truth
no dashboard-only state. no out-of-band changes. whatever is in the repo is what runs. always.
03 · secure
internal tools. private by default.
your team builds it, floo keeps it private. a real URL, behind login, connected to your real data. no auth code. no IT ticket.
a real URL, for your whole team
every app gets a URL the moment it deploys. your teammates open it and they're in.
private by default
require login for every app in your org. you control who's in. one policy, everywhere.
connect to real data
your app talks to your CRM, your database, your APIs. nobody outside your org can see any of it.
your app
ops dashboard
who has access
everyone in your org. remove anyone at any time.
- SRsarah r.ops
- MKmarcus k.finance
- PDpriya d.admin
- JLjames l.ops
api keys
programmatic and agent access included. mint a key, pass it in a header. free, built in.
02 · built
what teams build on floo.
real software running on floo. we are starting with the tools we use ourselves, because proof is better than placeholder cards.
03 · platform
every primitive a real app needs.
declare services in floo.app.toml, push to the default branch, and they're provisioned on the next deploy. runtime state like secrets and domains lives behind the cli.
applications
your frontend and backend. the full stack users actually load.
[services.web]workers
background jobs off the request path. queue consumers, llm calls, emails.
[services.worker]cron jobs
scheduled work on a reliable clock. nightly reports, cache warmers, syncs.
[cron.nightly]postgres
the database every real app builds on. users, orders, anything that has to persist.
[postgres]redis
cache, queues, rate limits, sessions. the glue between your services.
[redis]authentication
sign-in, sessions, and jwts. hosted oauth so you don't wire it up yourself.
[auth]secrets & env
api keys and config. encrypted at rest, injected into services at runtime.
floo env setcustom domains
your app on your domain. tls handled for you.
floo domains add04 · access
private beta. the next generation of builders.
we're onboarding the people excited to deliver outcomes with agents. engineer or not, startup or enterprise, your background doesn't matter. what you're building does. if you need a security review, procurement help, or dedicated infrastructure, say so in the note. the floo team reads every one.