Run queries without leaving the browser
A first-class SQL console against any database in your project, with statement history and guardrails on destructive work.
- History per database
- Read and write scopes are separate
- Results you can export
Every database, one console
Pick a database from the project and query it. No local client, no tunnel, no copying credentials into a desktop tool.
Read and write are different permissions
sql.execute.read and sql.execute.write are granted separately, so an analyst account can explore without being able to change anything.
History that survives the tab
Executed statements are kept per database so you can retrace what ran, when and by whom.
Honest about long queries
The editor runs against the same connection budget as everything else. A query that pins a connection for minutes is visible in connection statistics.
Made for the work you actually do
Most database work is a handful of statements: inspect a row, fix a value, add an index, check a plan. The editor optimises for that loop rather than pretending to be a full IDE.
Destructive statements are still destructive
There is no undo for a DELETE without a WHERE clause. Take a backup before schema surgery, and prefer a transaction you can roll back when you are exploring.
select usename, count(*) as connections
from pg_stat_activity
group by usename
order by connections desc;Build the whole backend in one project
One plan, one dashboard, one command line interface. PostgreSQL, applications, functions, storage and realtime.