Browsing your data

Browsing is read-only and requires the Viewer role on the resource. It never mutates data — it only issues catalog and SELECT/find/SCAN reads.

SQL engines (PostgreSQL, MySQL/MariaDB)

Database & schema tree

The browser first lists the databases the credentials can see, then the schemas and tables/views inside the selected one. Views are marked separately from tables. For MySQL/MariaDB — where a database is a schema — the tree is scoped to the connected database.

Pick a different database from the selector at the top of the panel to re-scope the tree.

Table structure

Select a table to see its structure, read from information_schema (and pg_indexes / information_schema.statistics for indexes):

• Columns — name, data type, nullability, and default value.
• Primary keys — PK columns are flagged.
• Indexes — index names with their definition (Postgres) or column list (MySQL).

Rows

The Data view pages through the table’s rows. Pagination defaults to 50 rows per page (configurable from 1 to 200) and shows a total row count so you know how far the table goes. Every value is rendered as text, so any column type displays cleanly in the grid.

Column names always come from the catalog, and the (schema, table) pair is verified to exist before any query is built — so browsing can’t be used to inject arbitrary identifiers.

MongoDB

The MongoDB browser walks the same tree shape, one level deeper for documents:

• Databases — from listDatabases.
• Collections — from getCollectionNames() on the selected database.
• Documents — find().skip().limit() with a default page of 20 documents (1–100), plus a countDocuments total. Documents are rendered as EJSON, so MongoDB types (ObjectId, Date, Decimal128, …) survive the round-trip instead of being flattened to plain JSON.

Redis / Valkey

Redis browsing is key-oriented:

• Key list — built with SCAN (cursor-based, 200 keys per batch) and an optional MATCH pattern (defaults to *). Use Load more to advance the cursor.
• Per-key type — each key shows its type (string, list, set, zset, hash, stream).
• Value view — selecting a key fetches its value with the right command for its type:
  • string → GET
  • list → LRANGE 0 500
  • set → SMEMBERS
  • zset → ZRANGE 0 500 WITHSCORES
  • hash → HGETALL
  • stream → XRANGE - + COUNT 100
• TTL — the key’s remaining time-to-live is shown alongside the value.
• Database index — switch between Redis logical databases 0–15 from the selector.

Next steps

• SQL Runner — go beyond browsing and run your own statements.
• MongoDB & Redis — the Mongo Shell and Redis command box.