If any of you runs one of these engines, I would value hearing what is missing. I answer every question here.It installs with Docker or with npx. The code is public: GitHub - libredb/libredb-studio: One browser tab for PostgreSQL, MySQL, Oracle, SQL Server, MongoDB, Redis, SQLite, Couchbase, ClickHouse, Druid, DuckDB, Turso and more. An open-source SQL IDE with SSO, audit trail and AI-assisted queries MIT licensed, with nothing held back behind an enterprise wall. · GitHub
What else it has: a query editor with autocomplete, an object tree, export, an ERD diagram, a monitoring panel for connections and slow queries, and an agent mode that answers questions about the schema with a local model, without sending data outside.How this was checked, so the numbers can be argued with: every engine is started in Docker from the compose file in the repository and driven through the same screens, connection, object tree, query and monitoring panel. What does not work is written down too. Two concrete cases: on Databend the object tree fails because the MySQL driver uses prepared statements and Databend answers “Prepare is not support”; on QuestDB the query is refused because its parser wants double quotes around reserved words. Each engine has its own document in the repository with the exact version it was measured against.2. 28 engines that speak the protocol of those same drivers: MariaDB, TiDB, Vitess, Percona Server, TimescaleDB, Citus, YugabyteDB, CockroachDB, AlloyDB Omni, ParadeDB, OrioleDB, Cloudberry, Materialize, RisingWave, Valkey, KeyDB, DragonflyDB, Garnet, FerretDB, ScyllaDB, Redpanda, VictoriaMetrics, StarRocks, Apache Doris, SingleStore, OceanBase, Databend and QuestDB.1. 18 engines with their own driver: PostgreSQL, MySQL, SQLite, libSQL, DuckDB, Oracle, SQL Server, ClickHouse, Druid, Trino, Cassandra, Elasticsearch, OpenSearch, MongoDB, Couchbase, Redis, Prometheus and Kafka.Version 0.17.0 reaches 46 engines in total:LibreDB Studio is an open source database client that runs in the browser and that you install on your own server. The data does not travel anywhere else: the connection opens from your server straight to the database. If a connection is marked read only, it refuses every write before the statement reaches the engine.Hello. I write on behalf of the team that builds LibreDB Studio. I want to show the project here and hear what is missing.