Reference

Supported Databases

Supported Databases

The current Community Edition database catalog is defined in the shared connectable database catalog used by the frontend, desktop app, and CLI. This page reflects that catalog instead of older marketing-era summaries.

Current CE Catalog

Database Type
Family Used By WhoDB
Connection Style
Scratchpad
Mock Data
Notes
Postgres
PostgreSQL
Network
Yes
Yes
Schema-aware SQL flow
CockroachDB
PostgreSQL-compatible
Network
Yes
Yes
Uses PostgreSQL-family behavior
YugabyteDB
PostgreSQL-compatible
Network
Yes
Yes
Uses PostgreSQL-family behavior
QuestDB
PostgreSQL-compatible
Network
Yes
Yes
Reduced schema/database switching vs core PostgreSQL
MySQL
MySQL
Network
Yes
Yes
Uses database switching instead of schemas
MariaDB
MySQL-compatible
Network
Yes
Yes
Uses MySQL-family behavior
TiDB
MySQL-compatible
Network
Yes
Yes
Uses MySQL-family behavior
SQLite3
SQLite
File path
Yes
Yes
File-backed connection
DuckDB
DuckDB
File path
Yes
Yes
Available only on supported builds
ClickHouse
ClickHouse
Network
Yes
Yes
Analytical SQL workflow
MongoDB
MongoDB
Network
Yes
Yes
Scratchpad uses shell-style commands (e.g. db.collection.find({})) instead of SQL
FerretDB
MongoDB-compatible
Network
Yes
Yes
Uses MongoDB-family behavior
DocumentDB
MongoDB-compatible
Network
Yes
Yes
AWS-managed, shown through provider discovery
Redis
Redis
Network
Yes
No
Scratchpad uses Redis commands (e.g. TYPE key) instead of SQL
Valkey
Redis-compatible
Network
Yes
No
Uses Redis-family behavior
Dragonfly
Redis-compatible
Network
Yes
No
Uses Redis-family behavior
ElastiCache
Redis-compatible
Network
Yes
No
AWS-managed, shown through provider discovery
Memcached
Memcached
Network
No
No
Cache/key browsing workflow
ElasticSearch
ElasticSearch
Network
No
No
Search/index workflow
OpenSearch
ElasticSearch-compatible
Network
No
No
Uses ElasticSearch-family behavior

Important Notes

Cloud-Managed Variants

DocumentDB and ElastiCache are part of the CE catalog, but they are marked as AWS-managed entries and are intended to be surfaced through cloud provider discovery rather than treated like ordinary manual entries.

File-Based Databases

SQLite3 and DuckDB use a database file path instead of host and port fields. The desktop app adds native file-picker support for these.

Capability Differences

Not every database type exposes the same feature set:

  • SQL-capable databases generally support Scratchpad, graph/schema views, and mock data generation
  • MongoDB-family and Redis-family systems support Scratchpad using their native command syntax rather than SQL
  • Memcached and search systems use narrower capability sets
  • Database switching and schema support vary by family

Build-Specific Availability

DuckDB availability depends on the build target.

Profiles vs Catalog Entries

The connection catalog is broader than the environment-profile system.

  • The catalog defines what the UI can connect to
  • Environment profiles are loaded from registered plugins and currently target the core registered types such as Postgres, CockroachDB, MySQL, MariaDB, TiDB, SQLite3, MongoDB, Redis, ElasticSearch, ClickHouse, DuckDB, and Memcached
  • Cloud-managed variants are configured through provider discovery rather than ordinary WHODB_<TYPE> profile prefixes
Database Connectivity

See how the login flow and advanced options work in the current app.

Cloud Providers

Enable AWS, Azure, and GCP discovery for managed resources.