Skip to content

Twenty-seven engines

One interface. Different engines.

Relational, document, key-value, graph, vector, time-series, streaming, 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, DuckDB and SQL Server.

  • Oracle

    Pooled connections with introspection through the ALL_* data-dictionary views and monitoring through the V$ views, each read guarded because they need privileges an app user may lack.

    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, DMV-backed monitoring and agent mode under a least-privilege read-only profile.

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

    Does not do The editor has no Explain action: SQL Server's estimated plan is a session mode that a statement prefix cannot express. Only agent mode reads a plan, to admit a statement.

  • Db2 LUW

    IBM Db2 for Linux, UNIX and Windows over DRDA, through a Rust driver that needs no IBM client. Schema introspection, server-side paging, inline edits on tables, and RUNSTATS and REORG one table at a time.

    Transport
    drda · 50000
    Reference
    docs/providers/db2.md

    Does not do No EXPLAIN, no query cancel and no Studio-side timeout in this version, and most monitoring panels are empty on purpose. Db2 for z/OS and for IBM i are out of scope.

  • 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 · 8080 (443 with TLS)
    Reference
    docs/providers/libsql.md

    Does not do Monitoring reads only what SQLite pragmas and dbstat answer over Hrana: no uptime, cache hit ratio, slow queries or sessions, because libSQL publishes none.

Analytics

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

  • DuckDB

    In-process analytics with full EXPLAIN support and agent mode. Admins can query Parquet and CSV files directly; every other role is confined to the database file.

    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 plans that show index usage, 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.

  • Databend

    Self-hosted Databend and Databend Cloud warehouses over its own HTTP query API, with no driver. Catalogs, databases, tables, views and dynamic tables in the tree, EXPLAIN on a SELECT, and monitoring from system tables.

    Transport
    http · 8000
    Reference
    docs/providers/databend.md

    Does not do No inline row or object edit: Databend declares no keys, so a row has no identity to update. Transactions are not exposed, and EXPLAIN ANALYZE is never sent.

Federated

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

  • 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, DuckDB and SQL Server.

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.

  • etcd

    Reads and writes a cluster through a subset of the etcdctl command line, with keys grouped by prefix and an admin's compaction, defragmentation and alarm disarm. Kubernetes-aware.

    Transport
    grpc · 2379
    Reference
    docs/providers/etcd.md

    Does not do Writes under Kubernetes' own prefixes are refused before anything is sent, and Kubernetes secrets, protobuf and encrypted values are withheld on every surface. No agent execution and no MCP.

  • Oxia

    Key lookups, lists and range scans over an Oxia namespace, written as oxia client commands, with its shards in the tree and every key in the Keys panel.

    Transport
    grpc · 6648
    Reference
    docs/providers/oxia.md

    Does not do Read-only whatever the toggle says: Oxia has no authorization and usually holds Pulsar's metadata, so writes, watches and sessions wait for a design of their own.

  • 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.

Graph

Nodes and relationships read in their own query language, and drawn as a graph beside the grid.

  • Neo4j

    Cypher over Bolt, with node labels, relationship types, indexes and constraints in the tree, and a Graph tab that draws the nodes and relationships a result returns.

    Transport
    bolt · 7687
    Reference
    docs/providers/neo4j.md

    Does not do Read-only by construction: a read policy, the server's own classification and a READ session stand between a statement and a write. No EXPLAIN or PROFILE, no APOC and no LOAD CSV.

Vector

Collections of vectors and payloads, searched by similarity in the engine's own request format.

  • Milvus

    Collections, exact counts, queries and vector searches over the gRPC API, typed as Milvus's own REST requests, with integers above 2^53 kept exact.

    Transport
    grpc · 19530
    Reference
    docs/providers/milvus.md

    Does not do Reads only — an admin's Load and Release are the one state change, and a collection is never loaded implicitly. Server-side functions, model rankers and calls to an embedding provider are refused.

  • Qdrant

    Collections, point reads, scrolls, counts, facets and queries over dense, sparse and multivector data, written as Qdrant's own REST requests.

    Transport
    http · 6333
    Reference
    docs/providers/qdrant.md

    Does not do Writes nothing — every request is one of seventeen reads — and refuses every server-side inference input except the local BM25 model.

Time-series

Metric stores read through their own query language; the series is the table.

  • Prometheus

    PromQL over the HTTP API, with the metric, rule and target browser beside it.

    Transport
    http · 9090
    Reference
    docs/providers/prometheus.md

    Does not do Read-only: Studio calls the read APIs only, so there is nothing to write back.

  • InfluxDB (InfluxQL)

    InfluxQL over the v1 query API on InfluxDB 1.x, 2.x and 3, with databases, measurements, tag keys and field keys in the tree.

    Transport
    http · 8086
    Reference
    docs/providers/influxdb.md

    Does not do Read-only whatever the toggle says, and no Flux: Flux is a server-side language, and on a read-only token it still made the server issue HTTP requests, so no read-only Flux policy can be sound.

  • InfluxDB 3 (SQL)

    InfluxDB 3 in SQL over /api/v3/query_sql, the DataFusion dialect its server runs: the tables of one database, their columns and their newest rows.

    Transport
    http · 8181
    Reference
    docs/providers/influxdb3.md

    Does not do Read-only, with no maintenance. Cloud Serverless and Cloud Dedicated serve SQL only over Arrow Flight, which Studio does not use; reach them with the InfluxQL type.

Streaming

Logs of records, browsed by offset or by time rather than queried.

  • Apache Kafka

    Topic, group and broker browser that reads by offset or by time.

    Transport
    kafka · 9092
    Reference
    docs/providers/kafka.md

    Does not do Read-only: it reads records, it does not produce 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 — twenty-seven engines, one interface, plus LibreDB, the embedded store the playground runs on. Twenty-seven more speak one of these wire protocols and connect through the same drivers, each measured against a live instance: fifty-four named engines in all. Per-engine detail lives in the provider docs. Read the provider docs ↗