Browse Elasticsearch as a search system
Move through indexes and documents using views designed for search data rather than translating everything into relational database concepts.
Understand and manage Elasticsearch data without forcing it into tables.
Browse indexes, inspect sampled fields, review documents in grid or JSON form, and make focused changes while keeping Elasticsearch beside the systems that depend on it.
- Type
- Search and document store
- Explore
- Index → document
- Connect with
- Hostname, optional credentials, port, and supported TLS options
What WhoDB lets your team do with Elasticsearch
Move from exploring Elasticsearch 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.
Understand changing document shapes
Inspect sampled fields and types while keeping it clear that the result describes observed documents, not a rigid table schema.
Review documents in the right format
Switch between grid, JSON, and metadata views to inspect the same index from the perspective the task requires.
Make focused document changes
Create, update, and delete documents when the connected Elasticsearch account has permission.
From connected data to a workflow people can trust
Connect the Elasticsearch deployment
Use the hostname, optional credentials, port, and supported TLS settings for the existing cluster.
Choose the index that matters
Browse available indexes, inspect sampled metadata, and review documents before changing anything.
Inspect in grid or JSON
Use a quick grid for scanning or the JSON representation when the exact document structure matters.
Keep dependencies visible
Place Elasticsearch beside the databases, data, and tools that feed it or rely on it, making operational work easier to coordinate.
An Elasticsearch GUI that respects document data
WhoDB gives teams a focused way to browse indexes, inspect documents, understand sampled fields, and make permitted document changes without pretending Elasticsearch behaves like a SQL database.
Its value grows when Elasticsearch is one part of a larger system: the search deployment can live beside related sources, ownership, and downstream work in the same project.
WhoDB is a strong fit for
- Teams investigating search indexes and document shapes
- Engineers making focused operational document changes
- Organizations using Elasticsearch beside operational databases
- Projects that need shared ownership around search data
Elasticsearch integration questions
Straight answers about setup, everyday tasks, and how WhoDB fits into your workflow.
What can WhoDB browse in Elasticsearch?
WhoDB lets teams browse indexes, inspect sampled field metadata, and review documents in grid, JSON, or metadata views.
Can WhoDB edit Elasticsearch documents?
Yes. Teams can create, update, and delete documents when the connected account has the required permissions.
Does WhoDB run SQL against Elasticsearch?
No. WhoDB treats Elasticsearch as a search and document system. The current experience focuses on index browsing, document inspection, editing, deletion, and relationships.
Does WhoDB support OpenSearch?
Yes. OpenSearch is available as a compatible source type and uses the same focused index and document workflow.
Explore another source
Give your team one place to explore, understand, and build with data across the systems you already use.
WhoDB for PostgreSQL
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.
WhoDB for MySQL
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.
WhoDB for MongoDB
Use WhoDB as a MongoDB GUI for collections, documents, sampled schema metadata, editing, mock data, relationship context, visual workflows, and lineage.