db - floo

floo db exposes read, migration, backup, and restore access to an app’s managed Postgres. It also exposes preview database branch inspection and reset for pull request previews. pgvector is enabled on every managed Postgres, and the vector type resolves unqualified. floo db query, floo db migrate, and your app’s own connection all see it without a CREATE EXTENSION step or a schema prefix. See Postgres → Vector search with pgvector.

query

Run a SQL query against the managed database for an app.

floo db query --app my-app "SELECT id, email FROM users LIMIT 5"
floo db query --app my-app "SELECT COUNT(*) FROM orders" --env prod
floo db query --app my-app "SELECT * FROM logs" --limit 50

Flags

Flag	Default	Description
`--app`, `-a`	inferred from config	App name or ID
`--env`	`dev`	Target environment: `dev` or `prod`
`--limit`	`1000`	Maximum rows to return

schema

Print the current database schema for an app.

floo db schema --app my-app

migrate

Run pending migrations against the managed database.

floo db migrate --app my-app

The CLI ships the migration payload from your current checkout. Use this before or after a deploy when the app depends on a schema change.

connections

Show current Postgres connection usage versus the role’s limit.

floo db connections --app my-app
floo db connections --app my-app --env prod
floo db connections --app my-app --json

Flags

Flag	Default	Description
`--app`, `-a`	inferred from config	App name or ID
`--env`	`dev`	Target environment: `dev` or `prod`

Output

my-app (dev): 18/25 Postgres connections in use (72%)

When the role is near capacity (≥75%), the output adds a heads-up about pooling and a one-line Email team@getfloo.com, we can provision a dedicated instance. Use this command when diagnosing too many connections errors or before turning up app autoscaling.

backup

Create a restorable backup of the app’s managed Postgres schema for one environment.

floo db backup --app my-app
floo db backup --app my-app --env prod
floo db backup --app my-app --name analytics --json

✓ Created Postgres backup for my-app (postgres:default, env=prod).
  Backup ID: 018f3a2e-...
  Env: prod
  Size: 4.2 MB
  Expires: 2026-04-01T14:00:00Z

Backups expire on expires_at; restore or re-create one before then if you need it longer.

Flags

Flag	Default	Description
`--app`, `-a`	inferred from config	App name or ID
`--name`	`default`	Managed Postgres service name
`--env`	`dev`	Environment to back up: `dev` or `prod`

JSON output

{
  "success": true,
  "data": {
    "id": "018f3a2e-...",
    "app_id": "a1b2c3d4-...",
    "managed_service_id": "m5n6o7p8-...",
    "env": "prod",
    "status": "available",
    "size_bytes": 4404019,
    "size_human": "4.2 MB",
    "checksum_sha256": "9f86d081...",
    "created_at": "2026-03-01T14:00:00Z",
    "expires_at": "2026-04-01T14:00:00Z",
    "last_restored_at": null
  }
}

backups

List restorable backups for a managed Postgres service.

floo db backups --app my-app
floo db backups --app my-app --env prod --json

Postgres backups for my-app (postgres:default, env=all):
  Backup ID     Env   Status     Size    Created               Expires               Restored
  018f3a2e-...  prod  available  4.2 MB  2026-03-01T14:00:00Z  2026-04-01T14:00:00Z  -

Flags

Flag	Default	Description
`--app`, `-a`	inferred from config	App name or ID
`--name`	`default`	Managed Postgres service name
`--env`	all	Filter to `dev` or `prod`

JSON output is {"backups": [...], "total": 1} with the same backup fields as floo db backup.

restore

Restore a backup into its original environment’s schema. Pass the backup ID from floo db backups.

floo db restore 018f3a2e-... --app my-app --env dev
floo db restore 018f3a2e-... --app my-app --env prod

✓ Restored Postgres backup on my-app (postgres:default, env=prod).
  Backup ID: 018f3a2e-...
  Restored at: 2026-03-02T09:15:00Z
  Size: 4.2 MB

Restore drops the environment’s schema and loads the backup in one transaction, so the current data is replaced. Take a fresh floo db backup first if you need the current state again. The managed service reports restoring while it runs.

Arguments

Argument	Description
`BACKUP_ID`	Backup ID returned by `floo db backups`

Flags

Flag	Default	Description
`--app`, `-a`	inferred from config	App name or ID
`--name`	`default`	Managed Postgres service name
`--env`	`dev`	Environment to restore: `dev` or `prod`

JSON output

{
  "success": true,
  "data": {
    "backup": {
      "id": "018f3a2e-...",
      "env": "prod",
      "status": "available",
      "size_human": "4.2 MB",
      "last_restored_at": "2026-03-02T09:15:00Z"
    },
    "restored_at": "2026-03-02T09:15:00Z"
  }
}

backup carries the full backup record shown under floo db backup.

branches list

List the managed Postgres branches backing one preview environment.

floo db branches list feat-db-abcde --app my-app
floo db branches list https://my-app-preview-feat-db-abcde.on.getfloo.com --app my-app --json

The preview argument can be a preview slug, preview URL, source branch, or #123 when it resolves to one preview.

JSON output

{
  "success": true,
  "data": {
    "preview": {
      "slug": "feat-db-abcde",
      "environment_name": "preview"
    },
    "database_branches": [
      {
        "name": "default",
        "source_environment": "dev",
        "resource_status": "ready",
        "hydration_mode": "clone-dev",
        "schema_name": "app_123_preview_feat_db_abcde",
        "reset_eligible": true
      }
    ],
    "total": 1
  }
}

The response is agent-safe. It includes branch metadata and reset eligibility, but never plaintext credentials.

branches show

Show one preview database branch.

floo db branches show feat-db-abcde --app my-app
floo db branches show feat-db-abcde --app my-app --name analytics --json

Flags

Flag	Default	Description
`--app`, `-a`	inferred from config	App name or ID
`--name`	`default`	Managed Postgres branch name

branches reset

Drop and recreate one preview-owned managed Postgres branch. Dev and prod are untouched.

floo db branches reset feat-db-abcde --app my-app --name default
floo db branches reset feat-db-abcde --app my-app --name default --yes --json
floo db branches reset feat-db-abcde --app my-app --name default --preflight

Reset is tier 2 because it destroys preview-only data. Non-interactive callers must pass --yes.

Flags

Flag	Default	Description
`--app`, `-a`	inferred from config	App name or ID
`--name`	`default`	Managed Postgres branch name
`--yes`	off	Skip the confirmation prompt

JSON reset fields

{
  "success": true,
  "data": {
    "destructive": true,
    "data_loss": true,
    "tier": 2,
    "scope": "preview",
    "dev_prod_untouched": true
  }
}

Reset is blocked for dev/prod databases, external databases, non-Postgres resources, Redis, Storage, and preview branch rows that are not ready.

Managed Services, declare Postgres in floo.app.toml
floo env, read managed URLs like DATABASE_URL directly
Postgres, the end-to-end managed Postgres model
Preview Environments, supported preview data modes and branch reset behavior

​query

​Flags

​schema

​migrate

​connections

​Flags

​Output

​backup

​Flags

​JSON output

​backups

​Flags

​restore

​Arguments

​Flags

​JSON output

​branches list

​JSON output

​branches show

​Flags

​branches reset

​Flags

​JSON reset fields

​Related

query

Flags

schema

migrate

connections

Flags

Output

backup

Flags

JSON output

backups

Flags

restore

Arguments

Flags

JSON output

branches list

JSON output

branches show

Flags

branches reset

Flags

JSON reset fields

Related