Deploy an app without a GitHub repository

Your agent built an app in a local folder and you want it running for your team. floo deploy creates a floo-hosted project, pushes the current commit, and waits until it is live at https://<app>-dev.getfloo.app. floo hosts the git repository, so you need no GitHub account. Works with any app that has a Dockerfile and listens on 0.0.0.0:$PORT. floo init does not write one: copy a recommended Dockerfile from Dockerfiles or the build guides for Next.js, Rails, Django, FastAPI and Express.

Agent prompt

Paste into Claude Code, Codex, Cursor, or any agent that can run shell commands. Replace inventory with your app name.

Deploy this app to floo. App name: inventory.
Install the floo CLI if `floo --version` fails: curl -fsSL https://getfloo.com/install.sh | bash. Then run `floo auth login` and have me approve the sign-in.
If there is no Dockerfile, add one following https://getfloo.com/docs/guides/dockerfiles.md. If there is no floo.app.toml, run `floo init inventory`. Set access_mode = "accounts" under [app] so only invited people can sign in, and add [managed.default] with type = "postgres" if the app stores data. Read DATABASE_URL from the environment.
Run `floo preflight --json` and fix every error.
Commit everything with git.
Run `floo deploy --json` and report the live URL. If it stops, run the command in error.suggestion and try again.

You approve one thing: the floo sign-in in your browser.

By hand

curl -fsSL https://getfloo.com/install.sh | bash
floo auth login
floo init inventory
floo preflight
git init && git add -A && git commit -m "Deploy to floo"
floo deploy

floo deploy prints each step and ends with the live URL. Run it again after every commit to ship the next version.

floo.app.toml

A team-only app with a database:

floo.app.toml

[app]
name = "inventory"
access_mode = "accounts"

[services.web]
type = "web"
path = "."
port = 3000
ingress = "public"

[managed.default]
type = "postgres"

access_mode = "accounts" puts floo’s hosted, invite-only sign-in in front of the app. Your code reads the signed-in person from the X-Floo-User-Email header and writes no auth code. See App sign-in.
[managed.default] provisions Postgres for each environment and injects DATABASE_URL. See Postgres.
Add migrate_command under [services.web] to run migrations before traffic moves to a new version.

Invite your team

floo apps invite teammate@example.com --app inventory

They get a one-time link. Everyone else is refused at floo’s gateway before a request reaches your code.

What happens on each run

Run	What `floo deploy` does
First	Creates a floo-hosted project named after `[app] name`, adds a `floo` git remote, replaces the project’s starter commit with yours, and waits for the deploy
Later	Pushes the new commit to the same project and waits for the deploy

It stops with the exact next command when the folder isn’t ready: no floo.app.toml, not a git repository, no commits, or uncommitted changes. All the cases are in the floo deploy reference.

Production

floo deploy ships to dev. When the dev version is right, publish it:

floo releases promote --app inventory

Production gets its own database. A small tool used by a few people can live in dev alone. See Environments.

Move to your own GitHub repository later

You can clone the floo-hosted repository with floo projects clone. To deploy from a repository you own on GitHub instead, follow the Quickstart.

Next steps

floo deploy reference

Flags, error codes, and what each run does.

App sign-in

Invite-only sign-in and identity headers, with no auth code.

Cron jobs

Run a script on a schedule inside the same app.

App API keys

Give an agent its own scoped key to the app’s API.

Get started

Build with your stack

Deploy from your agent

Configure your app

Ship and release

Data

Domains and networking

App users and access

Operate

Team and billing

For agents

Deploy an app without a GitHub repository

Agent prompt

By hand

floo.app.toml

Invite your team

What happens on each run

Production

Move to your own GitHub repository later

Next steps

floo deploy reference

App sign-in

Cron jobs

App API keys

​Agent prompt

​By hand

​floo.app.toml

​Invite your team

​What happens on each run

​Production

​Move to your own GitHub repository later

​Next steps

floo deploy reference

App sign-in

Cron jobs

App API keys

Agent prompt

By hand

floo.app.toml

Invite your team

What happens on each run

Production

Move to your own GitHub repository later

Next steps