Six ways to read a result, and a performance grade on every read that returns a cursor.

Table, tree, JSON, result, explain and chart. The view you want depends on the question you are asking, so switching between them costs one click and no re-run.

Query results in a virtualized table, sorted on durationMs, with the country column pinned to the left edge — Fig 01 Results · Table view, virtualized, with a pinned column and a sort

What it does

Table: virtualized, with column pinning, sorting, resize, reorder, multi-select and inline editing
Tree: every value carries its BSON type, with resizable columns and sticky document headers
Explain: a plan graded collection scan, indexed, optimal or ungraded, with the execution plan as a tree, scan efficiency, rejected plans, and the index that would fix it
Auto-explain collects the plan for you, so every read that returns a cursor carries its scan type without you asking. It is skipped where re-running would be unsafe, so a pipeline that writes is never explained
Cross-page search with cell-level highlighting, and a preview drawer that follows the focused row

A table cell open in the inline editor, with a String type selector beside the value and the schema enum offered below it — Fig 02 Results · Editing a value in place, with its BSON type beside it

Query results in tree view with a BSON type badge on every value — Fig 03 Results · Tree view names the BSON type of every value

The explain view grading a query that runs a collection scan, with an index suggestion — Fig 04 Explain · A COLLSCAN graded, with the index that would fix it

A workspace of eight saved charts in a four by two grid: line, area, dual axis, scatter, bar, stacked area, pie, and horizontal bar — Fig 05 Charts · A workspace of saved charts, each panel a query with its own chart Pro

Try it against your own data

38 MB installer. Free forever, and a 14-day Pro trial with no card.

Download Monghoul