Explore a DuckDB file without server setup
Open a local database file, browse schemas, tables, and views, inspect metadata, and read view definitions without configuring a network service.
Turn a DuckDB file into work the team can build on.
Explore schemas, tables, and views, run DuckDB SQL, work with records, and connect local analytical work to repeatable transformations, lineage, models, and tools.
- Type
- Embedded analytical database
- Explore
- DuckDB file → schema → table or view
- Connect with
- A local DuckDB database file
What WhoDB lets your team do with DuckDB
Move from exploring DuckDB 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 native DuckDB SQL
Analyze local data with DuckDB SQL and keep the results beside the structure and project work that explain them.
Prepare and change data directly
Create objects, add and update rows, delete records, import datasets, and generate relationally aware mock data when the file is writable.
Carry local analysis into shared work
Turn useful results into visual transformations, traceable lineage, shared models, reusable functions, and internal apps.
From connected data to a workflow people can trust
Open the DuckDB file
Choose the local database file directly, without setting up a host, port, or separate database server.
Understand the analytical structure
Browse schemas, tables, views, metadata, and records before writing or reusing an analysis.
Make the analysis repeatable
Move recurring SQL and transformation steps into a visible workflow with execution history and ownership.
Build on the result
Connect approved outputs to lineage, shared business models, functions, or internal apps inside the project.
A DuckDB GUI that connects local analysis to the team
WhoDB provides a clear interface for DuckDB schemas, tables, views, SQL, and record operations, then gives successful analysis somewhere useful to go next.
Teams can keep fast local analytics while adding the ownership, execution history, lineage, and interfaces needed when that work becomes important to other people.
WhoDB is a strong fit for
- Analysts working with local DuckDB databases
- Teams turning exploratory SQL into repeatable workflows
- Developers embedding analytical data in applications
- Projects connecting local analysis to shared tools and lineage
DuckDB integration questions
Straight answers about setup, everyday tasks, and how WhoDB fits into your workflow.
How does WhoDB connect to DuckDB?
Select a local DuckDB database file. No network database server or port is required.
Can WhoDB browse DuckDB schemas and views?
Yes. WhoDB shows schemas, tables, views, metadata, rows, and view definitions inside the connected file.
Can teams edit and import DuckDB data?
Yes. When the file is writable, teams can create objects, insert and update rows, delete records, import datasets, and generate mock data.
Can DuckDB work continue beyond local SQL?
Yes. Teams can use DuckDB data in transformations, execution history, lineage, shared models, functions, apps, and permitted AI-assisted workflows.
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.