Skip to main content
Look inside a managed database without opening a port or handing out its password. The dashboard’s Explorer and SQL Console tabs, the CLI, and the API all go through the control plane, which runs the engine’s own client inside the database container. Credentials never reach the browser and are never logged. Supported engines: Postgres, MySQL, and MariaDB (schema, table data, SQL), and Redis, KeyDB, and Dragonfly (read-only key browser). MongoDB and ClickHouse are not supported yet.

​
Explorer

Open a database and choose Explorer.
  • Schemas, tables, and views with a row estimate and total size.
  • Columns with type, nullability, default, and primary key; indexes with their definitions.
  • A paginated data grid (100 rows per page) with column sorting and a column filter (contains, equals, is null, is not null). Long values are truncated in the grid and open in full when clicked.
For Redis-compatible engines the Explorer is a key browser: pattern scan with SCAN, then each key’s type, TTL, and value. It cannot write.

​
SQL console

Open SQL Console. Statements run read-only by default:
  • One statement per request. Multiple statements, backslash commands, and COPY are rejected.
  • The statement runs in a read-only transaction, with a statement timeout, a row limit, and a result size cap.
  • INSERT, UPDATE, DELETE, DDL, SELECT INTO, data-modifying CTEs, and functions that read server files or signal other sessions are rejected.
  • Explain and Explain analyze show the query plan.
  • History is kept per user and database. Statements can be saved by name.

​
Allowing writes

An administrator (the root ability) can switch the console to write mode: turn on Allow writes, then type the database name to confirm. Each statement then runs in its own committed transaction and is recorded in the audit log with its fingerprint (never its text or results). Write mode is off again whenever the page is reloaded.

​
CLI

db works as a short alias for databases.

​
Permissions

A plain read token cannot see row data. IAM policies scoped to one database apply as they do for the rest of the database routes.

​
Limits

Defaults are tunable through environment variables on the control plane.

​
API

​
Security notes

  • The console connects over the container’s local socket as the database’s own admin role, so the read-only transaction and the statement guard are the protection, not a reduced-privilege role. Do not grant read:sensitive to principals you would not trust with the data.
  • Statement text is stored in your history. Results are never stored or logged. Server logs carry only the database name, mode, a literal-free fingerprint, duration, and row count.
Last modified on October 12, 2026