DEV Community: Abdullah Kaya

What getting into thirteen database projects' docs actually took

Abdullah Kaya — Fri, 02 Oct 2026 22:11:51 +0000

Thirteen database projects now list LibreDB Studio, our open source browser SQL IDE, in their official documentation: PostgreSQL, Redis, ClickHouse, MariaDB, DuckDB, Trino, YugabyteDB, StarRocks, DragonflyDB, OpenSearch, Apache Cloudberry, Apache Druid and Aiven (PostgreSQL, MySQL).

Each listing went through that project's own review. Here is what that looked like.

How long it took

DuckDB merged the same day the pull request was opened, and so did Aiven's second guide. Aiven's first one took under three days.
Apache Cloudberry took about five days.
OpenSearch took about two weeks, YugabyteDB about two and a half.
Apache Druid merged in a week, then waited almost six weeks for its site to be republished, which came with the Druid 38.0.0 release.

Read the contributing guide before the docs page

Every project wants the entry in a different shape: a YAML row, a full guide page, one line in a list. Copying what the last tool did in the same file worked better than anything we wrote from scratch.

Test against the engine first

A docs page is a claim that the tool works with that engine. Before opening a pull request we ran the product against a live instance of it, so the page describes what we measured.

Be specific about compatibility

Our compatibility table lists 28 engines that connect through another engine's driver: 18 work fully, 9 partially, 1 only in the query editor. Being specific made reviews shorter.

Why bother

A docs page is where someone lands after they already chose a database and want to know what to use with it. That is a better first impression than an ad, and it only happens if the maintainers agree.

LibreDB Studio is MIT licensed. You deploy it next to your database and open it in the browser.

docker run -p 3000:3000 ghcr.io/libredb/libredb-studio:latest

Repo: https://github.com/libredb/libredb-studio

[Boost]

Abdullah Kaya — Sun, 13 Sep 2026 19:16:52 +0000

Cevheri

Sep 13

Designing a plugin architecture for third-party database providers in a TypeScript application

#sql #nosql #typescript #javascript

2 min read

I got tired of opening ports just to query my own database

Abdullah Kaya — Tue, 11 Aug 2026 11:19:24 +0000

Every time I spun up a managed Postgres, the workflow was identical: database ready in 40 seconds, then open a port, dig an SSH tunnel, or install a desktop app on whichever machine I happened to be at.

So I built something that deploys next to the data, not onto your laptop.

github.com/libredb/libredb-studio

What it does

A self-hosted SQL IDE in a container. You reach it from any browser. Nothing faces outward.

docker run -d -p 3000:3000 ghcr.io/libredb/libredb-studio:latest

Ten plus engines behind one interface: PostgreSQL, MySQL, Oracle, SQL Server, SQLite, MongoDB, Redis, Couchbase, ClickHouse, Druid... Same ER diagrams, same schema diff, same Monaco editor across all of them.

The things that actually matter day-to-day:

Schema diff with auto-generated migration SQL
Interactive ER diagrams (auto-layout, PNG/SVG export)
NL2SQL with any LLM — Gemini, OpenAI, or local Ollama
ORM code generator (TypeScript, Prisma, Go, Python, Java)
OIDC SSO — in the MIT build, not behind a paywall

53 seconds demo:

8 months in. Happy to answer questions about any design decision; drop them below.