Query every backend through one SQL surface

Most teams don't want a different tool for every backend. Register your sources once and query databases, SaaS apps, and uploads from the same SQL surface without bouncing between consoles or dialects.

How it works

Step 1: Query Postgres through hotdata query

Here postgres.public.orders. GitHub-backed tables use the same connection.schema.table pattern (confirm names with hotdata tables list --connection-id github).

Our app database and GitHub are already linked here. Give me every open order with just order id and dollar total, up to 100 rows.

Heavy or routed queries sometimes return async metadata instead. The engine would rather give you a run id than hold the connection until everything finishes.

Step 2: Query managed-database tables like connection tables

Managed-database tables sit in the same SQL namespace as postgres and github (for example default.public.*).

Pull the first 50 rows from my partner_accounts table with every column included.

Step 3: Mirror everything in the CLI for debugging

Run the open-orders check again, then show the 50 most recently updated GitHub issues (number, title, state). After that, list recent query activity so support can match what was tried.

Step 4: Guardrails with workspace context

Optional workspace docs (like DATAMODEL) spell out joins and naming beyond what the raw catalog shows. See Workspace context.

Who uses this

• Teams shipping one SQL interface to multiple apps or dashboards.
• Products that run agent tools against the same SQL surface across several backends.
• Internal platforms that want one workspace and one governed path for queries.