Skip to content

00 · floo

the way agents
ship production software.

a deployment pipeline that scales with your team. a fleet of floo-managed services: databases, queues, and caches. all wired up through one typed config file. one cli. one push to production.

floo
$ floo init ops-dashboard
✓ Wrote floo.app.toml
$ floo apps github connect acme/ops-dashboard
Building first deploy...
✓ Live at ops-dashboard.on.getfloo.com
$ git push origin main
✓ New deploy queued from GitHub

01 · thesis

config-as-code is how agents ship.

agents read files, edit files, run commands. they don't click through dashboards. so floo exposes production infrastructure through a typed config file and a git-driven pipeline. your agent writes floo.app.toml, your agent runs git push.

agent prompt

“add a worker that processes the uploads queue. point it at managed postgres. concurrency 4.”

one tool call later
floo.app.toml · diff
name = "ops-dashboard"
 
[services.web]
type = "web"
path = "./web"
port = 3000
 
+[services.uploads_worker]
+type = "worker"
+path = "./worker"
+port = 8080
+max_instances = 4
 
+[postgres]
  • typed, schema-validated

    toml means the agent cannot hallucinate a config that almost works. the platform refuses anything ambiguous.

  • the repo is the truth

    every change is a git commit. git log is your deploy log. rollback is a revert. no dashboard-only state.

  • docs written for agents

    structured, exhaustive, stable schema. an agent ingests the docs once and has platform context forever.

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 set

custom domains

your app on your domain. tls handled for you.

floo domains add

04 · 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.

get access

name and email only. add a note if you'd like. we read everything.

by submitting, you agree to our terms and privacy policy.