Skip to content

Data console

Every managed Postgres database and Valkey cache has a Data tab. It is a small database client inside the dashboard: browse what is there, run a query, fix a row, without installing a client or copying credentials.

On a Postgres database:

  • Tables: every table in the database, with row counts. Click one to page through rows, search, filter by column and sort.
  • Row detail: click a row to see every column, including long text and JSON, formatted.
  • SQL: a console that runs the statement you type and shows the result as a grid. Use Query in console from the table view to start from a SELECT on that table.

On a Valkey cache:

  • Keys: browse keys of every type (strings, hashes, lists, sets, sorted sets, streams) with pattern search, and open one to see its value and TTL.
  • Console: run one Valkey command at a time, with the reply shown as the CLI would print it.

The console is read-only by default. Every statement is planned and classified before it runs; in read-only mode anything that would change data is rolled back and the console tells you so (“Read-only, nothing is saved”).

Owners and admins can flip the Write switch in the console to commit changes. Statements that drop or truncate ask for a second confirmation. The switch is per session and drops back to read-only if your role changes.

Every statement run from the Data tab is recorded in the datastore’s logs as text, never with results, so the team can see who ran what.

  • The datastore needs Public access on. The console connects over the datastore’s public, TLS-encrypted hostname. If public access is off, the tab shows Public access is off with a button to turn it on.
  • A paused datastore shows Paused; a sleeping one shows Asleep with a Wake button. Opening the console wakes it.
  • Members can read; only owners and admins can write. See Organizations and roles.

If you would rather use psql or valkey-cli, okctl connect <id> opens a tunnel and drops you into the right client with the credentials filled in. Add --tunnel-only to keep the tunnel open for a GUI client.