Skip to content

Seventeen engines

One interface. Different engines.

Relational, document, key-value, analytical, search and federated query — the same tree, editor and grid over each of them, and each engine's real limits declared rather than papered over.

SQL

Pooled connections, catalog introspection, visual EXPLAIN and ER diagrams.

  • PostgreSQL

    The reference engine — pooled connections, full catalog introspection, visual EXPLAIN, ER diagrams, live health and agent mode.

    Transport
    pg pool · 5432
    Reference
    docs/providers/postgres.md

    Does not do Nothing held back — every capability in the product ships here, including agent mode.

  • MySQL

    Pooled connections with information_schema introspection, EXPLAIN plans and performance_schema-backed monitoring.

    Transport
    mysql2 pool · 3306
    Reference
    docs/providers/mysql.md

    Does not do Agent mode is unavailable, as on every engine but PostgreSQL, SQLite and DuckDB.

  • Oracle

    Pooled connections with introspection and monitoring through the ALL_* and DBA_* data-dictionary views.

    Transport
    oracledb pool · 1521
    Reference
    docs/providers/oracle.md

    Does not do Agent mode is unavailable here. Operate still reads the server's own reporting interface.

  • SQL Server

    Pooled connections with sys.* catalog introspection, estimated plans and DMV-backed monitoring.

    Transport
    mssql pool · 1433
    Reference
    docs/providers/mssql.md

    Does not do Agent mode is unavailable here; the editor, diagrams and health are identical.

  • SQLite

    The embedded engine — a file, no network. Full editor, ER diagrams, EXPLAIN and agent mode.

    Transport
    file · embedded
    Reference
    docs/providers/sqlite.md

    Does not do There is no server to monitor: health reads file size and pragma statistics only.

  • libSQL

    SQLite's dialect over the network — Turso and self-hosted sqld, spoken natively.

    Transport
    hrana · 443
    Reference
    docs/providers/libsql.md

    Does not do Monitoring is limited to what the sqld server itself exposes.

Analytics

Columnar and in-process engines — scan-heavy queries and file-backed tables.

  • DuckDB

    In-process analytics — query Parquet and CSV files directly, with full EXPLAIN support and agent mode.

    Transport
    file · embedded
    Reference
    docs/providers/duckdb.md

    Does not do Single-writer by design: no sessions to list, so health shows storage, not connections.

  • ClickHouse

    HTTP interface with system.* introspection, EXPLAIN pipelines and query-log monitoring.

    Transport
    http · 8123
    Reference
    docs/providers/clickhouse.md

    Does not do No foreign keys exist, so ER diagrams show structure without discovered relations.

  • Apache Druid

    SQL over HTTP with datasource and segment introspection for streaming analytics.

    Transport
    http · 8888
    Reference
    docs/providers/druid.md

    Does not do Append-oriented: row editing is disabled rather than offered and then failed.

Federated

One query across several underlying systems; the catalog is the federation.

  • Apache Trino

    Federated SQL — one query across the catalogs you already have, from object storage to RDBMS.

    Transport
    http · 8080
    Reference
    docs/providers/trino.md

    Does not do Trino queries catalogs; it does not manage a lakehouse. Writes depend on the underlying connector.

Document

Collections and nested documents, with the grid flattening what it can.

  • MongoDB

    Document browsing, aggregation pipelines and index introspection over the native driver.

    Transport
    driver · 27017
    Reference
    docs/providers/mongodb.md

    Does not do No SQL translation layer is faked — queries here are MongoDB queries.

  • Couchbase

    SQL++ queries with bucket, scope and collection introspection over the documented REST surfaces.

    Transport
    http · 8091
    Reference
    docs/providers/couchbase.md

    Does not do Agent mode is unavailable, as on every engine but PostgreSQL, SQLite and DuckDB.

Key-value

Ordered keyspaces. Tables and collections are conventions over the keys.

  • Redis

    Key browsing by pattern, type-aware value views and INFO-backed live monitoring.

    Transport
    resp · 6379
    Reference
    docs/providers/redis.md

    Does not do No SQL, and none is pretended — the editor speaks commands here.

  • LibreDB

    The embedded ordered key-value store — a file, no server and no wire protocol. Mapped onto the interface by convention rather than by emulating SQL.

    Transport
    file · embedded
    Reference
    docs/providers/libredb.md

    Does not do No sessions and no index objects exist, so those two panels are absent with their reason rather than answered empty. Maintenance operations are refused, not faked.

Wide-column

Partition-and-clustering-key stores, where a scan is a decision, not a default.

  • Cassandra

    CQL editor with keyspace, table and type introspection for wide-column data.

    Transport
    cql · 9042
    Reference
    docs/providers/cassandra.md

    Does not do No joins and no EXPLAIN — the grid respects partition-key query rules instead of hiding them.

Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.

The claim is the span, not a count — seventeen engines, one interface. Per-engine detail lives in the provider docs. Read the provider docs ↗