deploy with agents. stay in control.
the cloud for human-agent software teams.
ai can code. floo is the cloud where humans and agents collaborate to ship production software.
- production-shaped previews for agent changes
- runtime logs, deploy history, and rollback in one place
- human review for launch, access, spend, and data risk
01 · use floo for
build with agents. ship with humans.
use floo when an agent can move fast, but the app still needs real infrastructure, real users, and human judgment before it affects the business.
core products
run the product your customers depend on. agents work against real infrastructure. humans control what reaches users.
bespoke software
build for one customer, prove value fast, and keep scaling the winner in production.
internal systems
replace generic workflows with software shaped around how your team actually operates.
02 · production loop
agents move fast. humans review what matters.
an agent opens a preview, reads the runtime, repairs the code, and reruns the checks. the change waits at the gate until a person approves it.
agent loop
“open a preview, inspect the failing job, repair the worker, and rerun the checks.”
- reads runtime logs
- inspects deploy history
- opens a preview
- reruns the checks
preview opened
real services, env vars, and managed data
runtime context attached
logs, deploy history, health, and errors
agent repair applied
fix pushed back through the repo
checks passed
ready for human review
human gates
launch
customer-visible release
access
who can open the app
spend
capacity and budget changes
data risk
destructive or high-impact operations
production-shaped previews
agents iterate against a real running app, not a fake local shadow of production.
runtime context for agents
logs, deploys, services, env, and docs point the agent toward the next correct action.
humans at the boundary
agents move quickly below the gate. people review what changes users, data, access, or spend.
03 · access
real software. gated how you choose.
floo is for core products, bespoke software, and internal systems. open it to the world, gate it for a customer, or keep it inside the team.
public when it should be
launch a product, API, demo, or workflow on a real URL people can actually open.
private when it matters
gate internal systems, customer-specific apps, and team tools without turning access into a side project.
review before impact
keep humans in the loop for launch, access, spend, and changes that can affect users or data.
live app
customer demo
who can open it
invite a customer, keep it internal, or open it publicly when the product is ready.
- SRsarah r.ops
- MKmarcus k.finance
- PDpriya d.admin
- JLjames l.ops
api keys
programmatic and agent access included. agents can inspect and operate the app without asking a human to click through a dashboard.
04 · stack
the production shape agents can work against.
floo has the primitives a production team needs: apps, APIs, workers, scheduled jobs, managed data, previews, logs, and rollback. the difference is how agents use them.
web apps and APIs
the user-facing surface and the backend behind it, deployed together from the repo.
live URLs, custom domains, health checks
workers
background jobs off the request path, from syncs to queues to long-running product work.
same app model, same logs, same deploy history
scheduled jobs
reliable work on a clock, such as reports, reminders, cache warmers, and data refreshes.
visible runs, failures, and runtime context
managed data
state for apps that need to remember users, orders, events, files, or workflow progress.
databases, object storage, cache, and queues
preview environments
branch-scoped places for agents to test changes against production-shaped infrastructure.
real services before a human merges
access and launch
open the app publicly, gate it for a team or customer, and review risky changes before launch.
access controls, domains, spend limits, gates
logs and rollback
the operational context agents and humans need when a change breaks or needs to be reversed.
runtime logs, deploy records, one-step rollback
agent-readable operations
stable commands and structured output so agents can inspect, repair, and keep moving.
CLI, docs, JSON output, clear error codes
proof
we run floo on floo.
the customer-facing product, internal operations, and the software we want to test quickly all ship through the same production loop.
this site
the page you are reading
the dashboard
where teams run their apps
floo-crm
our internal app for deploys, usage, and accounts
05 · beta
agents changed who builds. floo is where it ships.
floo is in private beta. bring the product, internal system, or customer build you want to ship with agents. most bets should die. the winners should already be on a cloud that can scale with them. we work high-touch from day one.
shared slack channel
direct access to us for questions, support, and fast feedback.
hands-on onboarding
we work with your team to get your apps onto floo and prove the full production path.
a tight feedback loop
we want to know what helps, what gets in the way, and what your agents need next.
if you need a security review, procurement help, or dedicated infrastructure, review the trust page and say so in the note. the floo team reads every one.