Browse MongoDB on its own terms
Move through databases and collections, inspect documents in grid or JSON views, and keep indexes and read-only views visible in a workflow designed for document data.
Explore databases, collections, views, indexes, and sampled document shapes; work safely with records; and connect MongoDB to the transformations, lineage, and tools around it.
Move from exploring MongoDB to building useful workflows, shared tools, and trusted data products—all without losing the context behind the work.
Updated August 25, 2026. Available actions depend on the permissions granted to your connected account.
Move through databases and collections, inspect documents in grid or JSON views, and keep indexes and read-only views visible in a workflow designed for document data.
WhoDB samples collection data to show useful fields and data types while clearly labeling the result as a sample rather than a fixed schema.
Create collections, add documents, update or delete records, and generate representative mock documents while respecting the connected user's permissions.
Use MongoDB data inside project transformations, lineage, semantic models, functions, and apps alongside the SQL, analytical, cloud, and business systems it interacts with.
Use a normal host or a MongoDB SRV connection URL, with supported authentication and TLS options for the environment.
Browse collections and documents, review sampled fields and types, and inspect indexes before making assumptions about flexible data.
Combine document data with other project sources through visible transformations and keep execution history beside the logic.
Follow project relationships into datasets, transforms, models, functions, and apps so a collection change is not evaluated in isolation.
MongoDB's flexible model is valuable precisely because it is not a table with a rigid schema. WhoDB preserves that distinction through document-oriented browsing and sampled metadata, then gives the team a shared place to connect those documents to everything downstream.
WhoDB gives MongoDB teams a clear way to browse collections, understand document structure, edit data, generate mock documents, and see relationships across the wider project.
Straight answers about setup, everyday tasks, and how WhoDB fits into your workflow.
Yes. The MongoDB connection flow accepts a hostname or MongoDB SRV URL, plus database, authentication, port, and supported TLS settings.
WhoDB samples documents to show useful fields and data types. Because documents in one MongoDB collection can have different shapes, WhoDB clearly labels this as a sample rather than a fixed schema.
Yes. Teams can create collections, insert and update documents, delete data, and generate mock documents when their MongoDB permissions allow it.
WhoDB is the stronger fit when MongoDB work must continue into cross-source transformations, lineage, semantic models, apps, or functions. Teams needing specialist MongoDB administration or a full Mongo shell may still use a dedicated tool alongside it.
Give your team one place to explore, understand, and build with data across the systems you already use.
Use WhoDB as a PostgreSQL GUI and shared data workspace for SQL, EXPLAIN ANALYZE, record editing, imports, mock data, lineage, pipelines, and AI-assisted work.
Use WhoDB as a MySQL GUI and data workspace for schema exploration, native SQL, record editing, imports, mock data, visual pipelines, lineage, apps, and AI.
Use WhoDB as a Snowflake SQL client and data operations workspace for exploration, editing, imports, visual pipelines, lineage, semantic models, apps, and AI.