Documentation
Databases

SQL workspace and data explorer

Inspect schemas and run protected SQL from the console.

6 minute read · Updated September 2026

Data explorer

Data explorer lists schemas, tables, columns, nullability, and a bounded preview of live rows. Use it for inspection—not bulk export or application traffic.

SQL workspace

The workspace runs one statement at a time and keeps execution history. Read-only behavior is the default. Enabling writes requires an explicit acknowledgement because a statement can change production data.

Safe inspection
select current_database(), current_user, now();

select schemaname, tablename
from pg_catalog.pg_tables
where schemaname not in ('pg_catalog', 'information_schema')
order by 1, 2;

Operational rules

  • Use a dedicated database role with only required permissions.
  • Inspect the target database and project before executing.
  • Use application migrations for schema changes.
  • Never paste secrets into saved queries.
  • For risky changes, take a restore point and define rollback first.
Was this guide useful?

If anything is unclear or incorrect, tell the support team.

Get help