Skip to main content
Your agent can deploy your app with floo deploy. Declare services, managed Postgres, sign-in, and scheduled jobs in floo.app.toml. When a deploy fails or a runtime error repeats, floo can send the context to your agent.

What an app built with AI needs

The agent drives all of it through the floo CLI, where every command takes --json, or the HTTP API at https://api.getfloo.com/v1. When floo deploy --json stops, error.next lists the fix, so the agent knows what to run next.

Deploy one

The app needs a Dockerfile that serves on 0.0.0.0:$PORT. Dockerfiles has one to copy for each common stack.
floo deploy deploys from the GitHub repository the folder pushes to. A folder with no remote takes floo deploy --github (a new private repository in your account) or floo deploy --hosted (floo hosts the code). A new org needs a plan first: floo billing upgrade. A typical app with a database, team sign-in, and a nightly job:
floo.app.toml
For an app open to the public, set access_mode = "public". Every key is in the config reference.

One config instead of several accounts

Review changes to app configuration in git. Dev and prod use separate managed databases, and previews get their own database branches. See Preview environments for data options.

Start from your agent

Claude Code

A FastAPI app with Postgres and migrations from one prompt.

Cursor

A Next.js app behind invite-only sign-in.

Codex

Any app with a Dockerfile, from a GitHub repository or one floo hosts.

Internal tool or admin dashboard

Team sign-in, app roles, Postgres, and a daily scheduled job.

App for your customers

A public prod URL, your own domain, and invite-only dev.

Without GitHub

A local git repository to a live URL with one command.