Skip to main content

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.

For founders, indie hackers, and teams shipping AI-built apps to real users. Paste one line into your agent and your app is live.

​
Get started

Either paste this into your agent or install it yourself. 
Install floo from https://getfloo.com
  curl -fsSL https://getfloo.com/install.sh | bash
Then use floo to deploy my app.
Agent path. Paste tab 1 into Claude Code, Cursor, or any agent inside your project. It installs, signs you in, writes the config, connects GitHub, and pushes the first deploy. Manual path. Install the CLI, then follow the Golden Path.

​
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 control plane. App shape is repo-backed. Durable resources are explicit CLI operations. The dashboard is a window into what is live. 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. floo separates recoverable app shape from stateful resources. Services, routes, workers, and cron are reviewable in floo.app.toml. Managed Postgres, Redis, Storage, env vars, and domains are created with CLI commands, then reflected in reviewable state like .floo/services.lock.

Config in the repo

Declare application services, routes, workers, cron, and managed credential attachments in floo.app.toml.

State through the CLI

Provision managed Postgres, Redis, and Storage with floo services add. Deploy never destroys data from a config edit.

​
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.
See all use cases on getfloo.com

​
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.