Explore databases and tables clearly
Browse ClickHouse databases and tables, inspect metadata, and move into live rows without separating exploration from the work it informs.
Take ClickHouse analysis from fast answers to repeatable work.
Explore databases and tables, run ClickHouse SQL, work with data, and connect analytical results to transformations, lineage, models, apps, and functions.
- Type
- Analytical database
- Explore
- Database → table
- Connect with
- Hostname, database, credentials, port, and supported connection options
What WhoDB lets your team do with ClickHouse
Move from exploring ClickHouse 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.
Run ClickHouse SQL where the team works
Use native SQL with results kept beside the source, relationships, and project work that give each analysis meaning.
Work with analytical data directly
Create tables, add and update rows, delete records, import datasets, and generate mock data when the connected account allows it.
Turn analysis into an operating workflow
Build visual transformations, inspect run history, trace dependencies, and deliver results through shared models, functions, and apps.
From connected data to a workflow people can trust
Connect ClickHouse in place
Use the host, database, credentials, port, and supported security settings for the existing deployment.
Inspect before querying
Review databases, tables, metadata, and sample rows before committing time or compute to an analysis.
Make the logic repeatable
Move recurring SQL and transformation steps into a visible workflow with ownership and execution history.
Put the result in front of people
Connect trusted outputs to business models, reusable functions, or internal apps instead of ending with a downloaded result set.
A ClickHouse GUI for work that continues
WhoDB gives teams a clear place to browse ClickHouse, run SQL, and work with data, then preserves the analysis when it becomes a pipeline, lineage question, or internal tool.
ClickHouse can sit beside the rest of the team's operational and analytical sources in the same project, making cross-system work easier to understand and maintain.
WhoDB is a strong fit for
- Analytics teams working with large ClickHouse datasets
- Engineers turning recurring SQL into visible workflows
- Teams connecting analytical results to lineage and models
- Organizations operating ClickHouse beside other data systems
ClickHouse integration questions
Straight answers about setup, everyday tasks, and how WhoDB fits into your workflow.
What can WhoDB browse in ClickHouse?
WhoDB lets teams browse ClickHouse databases and tables, inspect metadata, and work with table rows.
Can WhoDB run native ClickHouse SQL?
Yes. Teams can run ClickHouse SQL and keep the results inside the same project as related workflows, lineage, and tools.
Can teams change ClickHouse data in WhoDB?
Yes. WhoDB supports table creation, inserts, updates, deletes, imports, and mock data when the connected account has the required permissions.
Does WhoDB replace specialist ClickHouse administration tools?
WhoDB is strongest when ClickHouse analysis needs to continue into shared workflows, lineage, models, functions, or apps. Deep server administration may still call for specialist tooling.
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.