Skip to main content
floo db exposes read and migration access to an app’s managed Postgres. Use it to ask quick operational questions, inspect the schema, or run pending migrations from the current checkout. 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 Databases → 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

FlagDefaultDescription
--app, -ainferred from configApp name or ID
--envdevTarget environment: dev or prod
--limit1000Maximum 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

FlagDefaultDescription
--app, -ainferred from configApp name or ID
--envdevTarget 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.
  • Managed Services — declare Postgres in floo.app.toml
  • floo env — read managed URLs like DATABASE_URL directly
  • Databases — the end-to-end managed Postgres model