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

# floo

> The fastest way to turn AI-written code into software real people can actually use.

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.

<CodeGroup>
  ```text Paste into your agent theme={null}
  Install floo from https://getfloo.com
    curl -fsSL https://getfloo.com/install.sh | bash
  Then use floo to deploy my app.
  ```

  ```bash Install it yourself theme={null}
  curl -fsSL https://getfloo.com/install.sh | bash
  ```
</CodeGroup>

**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](/docs/guides/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`.

<CardGroup cols={2}>
  <Card title="Config in the repo" href="/docs/reference/config-spec" icon="file-code">
    Declare application services, routes, workers, cron, and managed credential attachments in `floo.app.toml`.
  </Card>

  <Card title="State through the CLI" href="/docs/guides/managed-services" icon="database">
    Provision managed Postgres, Redis, and Storage with `floo services add`. Deploy never destroys data from a config edit.
  </Card>
</CardGroup>

## What you can ship

<CardGroup cols={3}>
  <Card title="Public products" href="/docs/guides/golden-path" icon="rocket">
    SaaS, APIs, consumer apps on a custom domain. Live logs and analytics built in, so you see what real users are doing, not guess.
  </Card>

  <Card title="Internal tools" href="/docs/companies/internal-tools" icon="wrench">
    Your team signs in with work email and your app knows every user. Build tools personalized to each teammate.
  </Card>

  <Card title="Private betas and demos" href="/docs/companies/sales-demos" icon="chart-mixed">
    Track per-company sign-ins and usage. See which prospects came back for a second look, close more deals.
  </Card>
</CardGroup>

[See all use cases on getfloo.com](https://getfloo.com/use-cases)

## Start building

<CardGroup cols={3}>
  <Card title="Ship my first app" href="/docs/guides/golden-path" icon="rocket">
    Three commands and your app is live. `floo init`, `floo apps github connect`, `git push`. Every push after that deploys automatically.
  </Card>

  <Card title="Understand the model" href="/docs/how-floo-works" icon="book">
    The four pillars that make floo safe for agents to operate. Config in the repo, deploys from GitHub, CLI as the surface.
  </Card>

  <Card title="Learn the CLI" href="/docs/cli/overview" icon="terminal">
    Every command, flag, and error code, with copy-paste examples your agent can parse and script against.
  </Card>
</CardGroup>