Workspaces & Tooling

Query every connected database from one place,
with approval gates where they matter

Query Hub is the unified query workspace for every database connected to Nova. Postgres, MongoDB, Redis, BigQuery, Snowflake. Read queries run instantly. Write queries route through Approval Queue when they touch tier-0 data. Saved queries replace the email-attached SQL files engineers used to share.

Get Started Talk to Sales
app.novaaiops.com / query-hub
● LIVE
Multi-db
unified query workspace
Read
instant, write gated
Per-db
permissions
Saved
queries shareable
Connected Databases

Every database, one workspace

Connect Postgres, MongoDB, Redis, BigQuery, Snowflake (and more) once; query them from one workspace. Each connection has its own permissions and its own approval rules. Switching DBs is a dropdown; cross-DB queries are supported via NovaQL's federated planner.

  • ✓
    One-time connect: add the connection once with credentials and a permission set
  • ✓
    Per-db permissions: role-based; some users read-only on prod, full on staging
  • ✓
    Cross-db via NovaQL: federated queries that join across two backends use the NovaQL planner
app.novaaiops.com / query-hub · dbs
Write Gating

Writes go through Approval Queue

Read queries run instantly. Write queries (INSERT, UPDATE, DELETE, DDL) are scanned by Dangerous Command Guard and routed to Approval Queue when they touch tier-0 data. The approver sees the SQL, the affected row count (estimated), and the rollback plan. Approve, reject, or escalate, same flow as any other agent action.

  • ✓
    Reads run instantly: read-only queries do not need approval; rate-limited per role
  • ✓
    Writes routed: every write goes through Dangerous Command Guard; tier-0 hits Approval Queue
  • ✓
    Estimated impact: before approval, the page shows the estimated row count and a generated rollback plan
app.novaaiops.com / query-hub · gate
Saved Queries

Replace the SQL-files-in-Slack pattern

Save any query with a name, tags, and a description. Saved queries appear in autocomplete and in the team library. Versioned forever; safe to refactor without breaking older shared links. Permissions inherit from the connected DB; users without read access on the underlying DB cannot run the saved query.

  • ✓
    Named library: saved queries with names, tags, descriptions; the team can find them in autocomplete
  • ✓
    Versioned: every save is a new version; older shared links keep working even after a refactor
  • ✓
    Permissions inherited: a user can only run a saved query if they have access to the underlying DB
app.novaaiops.com / query-hub · saved
Cost Visibility

Big queries cost real money

For BigQuery, Snowflake, and other usage-priced backends, every query shows estimated cost before it runs. Soft caps warn the user; hard caps reject. The cost data feeds Quota Cost Control so the tenant has a unified view of database spend alongside AI spend.

  • ✓
    Pre-flight cost estimate: rows scanned, GB read, dollar estimate, shown before run
  • ✓
    Soft and hard caps: soft warns, hard rejects; configurable per tenant and per role
  • ✓
    Unified cost view: database spend appears in Quota Cost Control next to AI spend
app.novaaiops.com / query-hub · cost
Video walkthrough coming soon

Subscribe to Nova AI Ops on YouTube for demos, tutorials, and feature deep-dives.

Stop emailing SQL files around

Query Hub is one place where queries live, run, and get reviewed.

Get Started Request a Demo