Skip to content

Database exploration for technical teams

Know your data
before the next query.

Browse records, follow schema relationships, and query a database from one connection workspace. Inspect supported edits before you apply them.

Open your connectionsSee the preview

Browse the databases your team has connected.

Available queries and changes depend on the connected engine and your permissions.

A closer look at Data Explorer.

Product preview · Sample data

Interactive demo

Connection / table workspace

Data Explorer

Table / public.orders

Orders

Sample rows: 3 shownSort: created descNo filter

Sample workspace - local only

Why Data Explorer

From unfamiliar tables to useful context.

01

Find the records that matter.

Filter and inspect records in grid, JSON, or Kanban views, depending on the shape of your data.

Three ways to browse

02

Understand how tables connect.

Follow declared foreign keys and inspect the schema before deciding how to join the data.

Schema maps + connection context

03

Review before you apply.

Stage supported edits and inspect the generated command with its target before applying it.

Data and schema change previews

Practice the underlying skill

Work through a SQL example.

Before you explore a new dataset, check the records behind it. Practice finding duplicate IDs, invalid dates, and missing customers in a small CSV.

Runs locally in DuckDB. Fictional data. No signup required.

Explore the records, then follow the relationships

Use grid view to compare rows, JSON for nested records, or Kanban to group by a field. Filter and sort the data to focus the investigation, then open the schema map to follow the foreign keys your database declares.

Keep that connection context as you move into the SQL or mongosh console. The table, schema, and result belong to the same working view.

Schema map

Trace the relationships your schema declares.

This ERD shows declared foreign-key relationships only. It does not infer relationships or cardinality.

customers

Table 01
  • id uuid
  • name text

orders

Table 02
  • id uuid
  • customer_id uuid
  • status text

order_items

Table 03
  • id uuid
  • order_id uuid
  • sku text

Declared foreign keys

  • orders.customer_id -> customers.id
  • order_items.order_id -> orders.id

Make the change visible before it runs

For supported engines and roles, stage row or schema edits and inspect the generated SQL, mongosh, or Elasticsearch command. Confirm the connection and affected records before applying it. Transaction and rollback behavior depend on the engine.

Read the Data Explorer documentation for connection and editing details.

Before you get started

A few useful answers.

Talk through your use case
Which views can I use?

Browse records in grid, JSON, or Kanban views. Inspect declared foreign-key relationships in the schema view, or work in the connection’s query console.

Can I edit records and schemas?

For supported engines and roles, you can stage changes and inspect the generated command before applying it. Transaction behavior varies; some changes may auto-commit or remain partially applied after a failure.

How does MongoDB querying work?

Use native mongosh, or the SELECT-only Zero-SQL bridge for supported SQL-to-aggregation translation. The bridge does not support subqueries or window functions.

Does the schema map infer every relationship?

It displays the foreign keys declared by the database. Relationships defined only in application logic need to be confirmed separately.

Get familiar with the data behind the question.

Choose a connection, inspect its tables, and follow the relationships into your next query.

Open your connectionsOr book a product walkthrough