Skip to content

Your data, without a desktop client.

Browse schemas and tables, run SQL with completion from your live schema, and read execution plans — all inside your Balta dashboard, with read-only safety and a full audit trail.

  • Included on every plan
  • Read-only by default
  • Every statement audited
acme-prodPostgreSQL 18 · database appAllow writesRead-only
Monthly revenueQuery 2ExplainRun
SELECT c.name,
       date_trunc('month', i.issued_at) AS month,
       sum(i.total) AS revenue
FROM invoices i
JOIN customers c ON c.id = i.customer_id
WHERE i.issued_at >= now() - interval '6 months'
GROUP BY 1, 2
ORDER BY revenue DESC;
Sample query results
namemonthrevenue
Kestrel Studio2026-09-0118,420.00
Aurora Freight2026-09-0112,905.50
Vela Analytics2026-08-019,860.00
Harbor & Pine2026-08-017,312.25
4 rows38 msStatement timeout onRecorded in your audit log

Example view with sample data.

Browse

Every table, one click away.

See every schema, table and view in your database, with their columns, types, indexes, constraints and foreign keys. Follow a foreign key straight to the rows it points at, and page through millions of rows with sorting and filters that stay fast on your largest tables.

customers
RowsColumnsIndexesForeign keys
Columns of the customers table
ColumnTypeNullable
idbigintnot null
nametextnot null
emailcitextnot null
plantext
created_attimestamptznot null
≈ 2.4 million rows · 1.1 GiB

Example view with sample data.

Query

SQL that knows your schema.

Write queries with completion drawn from your actual tables and columns. Run a statement or a whole script and see the results for each one. When something fails, the error tells you exactly where — with PostgreSQL’s own message, hint and detail.

Keep your own query history, and save queries your whole team can reuse.

acme-prodPostgreSQL 18 · database appAllow writesRead-only
Monthly revenueQuery 2ExplainRun
SELECT c.name,
       date_trunc('month', i.issued_at) AS month,
       sum(i.total) AS revenue
FROM invoices i
JOIN customers c ON c.id = i.customer_id
WHERE i.issued_at >= now() - interval '6 months'
GROUP BY 1, 2
ORDER BY revenue DESC;
Sample query results
namemonthrevenue
Kestrel Studio2026-09-0118,420.00
Aurora Freight2026-09-0112,905.50
Vela Analytics2026-08-019,860.00
Harbor & Pine2026-08-017,312.25
4 rows38 msStatement timeout onRecorded in your audit log

Example view with sample data.

Performance

Read the plan, not a wall of text.

Run EXPLAIN or EXPLAIN ANALYZE and see the plan as a tree — every step with its cost, its estimated and actual rows, and the time it took. Spot the sequential scan that should have been an index lookup, without copying text into another tool.

Query planEXPLAIN ANALYZE
  • Sortcost 2,310rows 4 / 438.0 ms
  • Hash Joincost 2,290rows 4 / 437.6 ms
  • Seq Scan on invoicescost 1,980rows 2,000 / 18,41231.2 ms
  • Index Scan on customerscost 180rows 4 / 40.9 ms
Planning 0.4 ms · Execution 38 ms

Example view with sample data.

Powerful, with guardrails.

Read-only by default

Writes are switched on deliberately, per session. Nobody drops a table by accident.

Query time limits

Every statement runs with a timeout, so one heavy query can’t slow your application.

Its own connections

Editor sessions use a separate budget and never take connections from your app.

Every statement audited

Who ran what, when, and how long it took — in your audit log.

Team access

The right access for every role.

Viewers can browse and run read-only queries. Developers and admins can switch on writes for a session. Every query runs as your own database role — so the editor can never do more than your permissions allow — and every statement is recorded in your audit log.

Audit logLast 24 hours
14:06[email protected] restored acme-prod to 14:02:17 into a new service
11:47Balta engineer accessed acme-prodReason recorded: “Investigating slow checkpoints, as requested in your ticket.” Access expired 13:47.
09:15[email protected] revealed connection credentials after confirming identity
08:30[email protected] changed the plan to Business

Example view with sample data.

Questions about the editor.

Is it safe to use on production?
Yes. Every session starts read-only, every statement has a timeout, and editor sessions use their own connection budget so they can’t take connections from your application.
Can I export results?
Yes. Download any result as CSV or JSON.
Who can write data from the editor?
Developers, admins and owners, after switching writes on for that session. Viewers can only read.
Does it cost extra?
No. The data browser and SQL editor are included on every plan.