apps

Manage your deployed apps.

list

List all apps on your account.

floo apps list

Your apps:
  Name          Status  Runtime   URL
  my-app        live    nodejs    https://my-app.on.getfloo.com
  api-service   live    python    https://api-service.on.getfloo.com
  landing       stopped static    https://landing.on.getfloo.com

Flags

Flag	Description	Default
`--page N`	Page number	`1`
`--per-page N`	Results per page	`50`

JSON output

{
  "success": true,
  "data": {
    "apps": [
      {
        "id": "a1b2c3d4-...",
        "name": "my-app",
        "status": "live",
        "url": "https://my-app.on.getfloo.com",
        "runtime": "nodejs",
        "created_at": "2026-02-18T10:30:00Z"
      }
    ]
  }
}

show

Show details for a specific app. Accepts app name or UUID.

floo apps show my-app

App: my-app
  Status:   live
  URL:      https://my-app.on.getfloo.com
  Runtime:  nodejs (Next.js)
  Created:  2026-02-18 10:30

JSON output

{
  "success": true,
  "data": {
    "id": "a1b2c3d4-...",
    "name": "my-app",
    "status": "live",
    "url": "https://my-app.on.getfloo.com",
    "runtime": "nodejs",
    "created_at": "2026-02-18T10:30:00Z"
  }
}

delete

Delete an app and tear down its infrastructure.

floo apps delete my-app

This permanently deletes my-app and all its data. Type the app name to confirm: my-app
Deleted my-app

Deleting an app is tier-3 destructive. Interactive mode makes you type the app name to confirm; non-interactive runs require the explicit --yes-i-know-this-destroys-data flag.

Flags

Flag	Description
`--yes-i-know-this-destroys-data`	Skip the name-confirmation prompt. Required in non-interactive contexts (CI, `--json`, pipes). Deliberately verbose: destroying an app and its data must be an explicit, acknowledged decision.

JSON output

{
  "success": true,
  "data": {
    "id": "a1b2c3d4-..."
  }
}

password

Show the shared password for a password-protected app.

floo apps password my-app

invite

Invite a floo identity to an accounts-mode app with an explicit tenant role.

floo apps invite teammate@acme.com --role member --app my-app

Arguments

Argument	Description
`EMAIL`	Email address to invite

Flags

Flag	Description
`--app APP`	App name or UUID (inferred from config if omitted)
`--role ROLE`	Tenant role after acceptance: `member` or `admin` (default `member`)

The raw invitation URL is returned exactly once and treated as a secret. It is redacted from JSON and omitted from human output unless you pass the global --reveal-secrets flag. The durable invitation remains valid if email delivery fails; resend with --reveal-secrets to rotate and copy a fresh URL. App access never grants dashboard or deployment access. For that boundary, see Team Access.

invites

List invitation history for an app.

floo apps invites --app my-app

List responses include next_cursor when another page exists. Continue with --cursor NEXT_CURSOR; floo apps members accepts the same flag. Rotate and resend a pending invitation, or revoke it:

floo apps invite-resend INVITE_ID --app my-app
floo apps invite-revoke INVITE_ID --app my-app

Resending invalidates the previous URL. Revoked and expired invitations cannot be accepted.

members

List active explicit app members:

floo apps members --app my-app

Change a tenant role or remove app access:

floo apps member-role MEMBERSHIP_ID admin --app my-app
floo apps member-remove MEMBERSHIP_ID --app my-app

Changing a role revokes active app sessions that carry the old role. Removing a member also revokes that person’s app sessions and user-bound app API keys.

consumers

Manage named consumers for app API keys. See App API keys and request history for route scopes and storing a key through a pipe.

floo apps consumers list --app my-app
floo apps consumers create daily-report --app my-app
floo apps consumers delete daily-report --app my-app

Deletion accepts a consumer ID or a case-insensitive name and revokes all its active keys. It requires typed confirmation, or the explicit flag in non-interactive or JSON mode:

floo apps consumers delete daily-report --app my-app --yes-i-know-this-destroys-data

Flags

Flag	Description
`--app NAME`	App name (defaults to the app in local config)
`--yes-i-know-this-destroys-data`	Confirm consumer deletion in non-interactive or JSON mode

keys

Create, list, and revoke a consumer’s app API keys.

floo apps keys list --consumer daily-report --app my-app
floo apps keys create reader --consumer daily-report --scope reports.access --rate-limit-rpm 60 --app my-app
floo apps keys revoke KEY_ID --app my-app

Revocation takes a key ID and is idempotent.

Flags

Flag	Description
`--app NAME`	App name (defaults to the app in local config)
`--consumer NAME_OR_ID`	Required for list and create; accepts an ID or a case-insensitive name
`--scope SCOPE`	Required for create; repeat for multiple scopes. `--scope '*'` explicitly grants every scope
`--rate-limit-rpm N`	Per-key requests per minute for create

Human mode prints only the raw key on stdout. The shown-once notice and the key’s ID, prefix, and scopes go to stderr. The key cannot be retrieved again; store it directly in the program’s secret store. See the guide’s piping example.

JSON output

With --json, raw_key is redacted unless you pass the global --reveal-secrets flag. The output sets contains_secrets: true in either case.

github

Manage GitHub integration for auto-deploy on push. See the full reference at GitHub Integration.

floo apps github connect owner/repo --app my-app
floo apps github disconnect --app my-app
floo apps github status --app my-app

Errors

Code	Meaning
`NOT_AUTHENTICATED`	Run `floo auth login` first
`APP_NOT_FOUND`	No app with that name or ID. Check with `floo apps list`
`APP_CONSUMER_NAME_TAKEN`	A consumer with that name already exists in the app
`APP_CONSUMER_CAP_REACHED`	The app has reached its limit of 50 consumers
`APP_CONSUMER_KEY_CAP_REACHED`	The consumer has reached its limit of 100 active keys
`INVALID_SCOPE_LABEL`	A scope label is invalid
`APP_CONSUMER_NOT_FOUND`	No consumer with that name or ID in the selected app
`APP_API_KEY_NOT_FOUND`	No app API key with that ID in the selected app
`INSUFFICIENT_KEY_SCOPE`	The operator credential lacks the required scope
`APP_DELETING`	The app is being deleted

CLI

Config

list

Flags

JSON output

show

JSON output

delete

Flags

JSON output

password

invite

Arguments

Flags

invites

members

consumers

Flags

keys

Flags

JSON output

github

Errors

​list

​Flags

​JSON output

​show

​JSON output

​delete

​Flags

​JSON output

​password

​invite

​Arguments

​Flags

​invites

​members

​consumers

​Flags

​keys

​Flags

​JSON output

​github

​Errors

list

Flags

JSON output

show

JSON output

delete

Flags

JSON output

password

invite

Arguments

Flags

invites

members

consumers

Flags

keys

Flags

JSON output

github

Errors