I help maintain this, so flagging it as a promo post up front. MIT licensed, no paid tier, nothing held back.

The problem it solves for a homelab: you spin up Postgres in a container, then you want to look inside it. So you either open a port, dig an SSH tunnel, or install DBeaver on every machine you might touch it from. On a phone you have nothing at all.

LibreDB Studio goes the other way. It is one container you run beside the database, on the same Docker network or in the same cluster, and you open it in a browser. The database keeps no port facing the outside. Nothing is installed per person.

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

What is actually in it:

  • 42 drivers of its own, reaching 69 engines because another 27 speak one of those wire protocols. Postgres, MySQL, MariaDB, SQLite, MongoDB, Redis, Valkey, ClickHouse, Elasticsearch, InfluxDB, Kafka, Neo4j and the rest share one sidebar.
  • OIDC single sign-on, role based access control, a query audit trail and column level masking. These are in the free build, not an enterprise tier. If you run a homelab with family or friends on it, that is the part that matters.
  • Monaco editor with schema aware completion, visual EXPLAIN, ER diagrams drawn from real foreign keys, schema diff that outputs migration SQL.
  • An optional read-only agent that runs against a model you configure, including a local Ollama, so the schema does not leave your network. It is off unless you turn it on.

Install paths: Docker image, Helm chart, Kubernetes operator, deb and rpm, Snap, Homebrew, winget, or one-click templates on CasaOS, Unraid, YunoHost, Runtipi, CapRover, Portainer and Dokploy.

Known limits, so nobody wastes an evening: Redis is single node only, no Cluster, no Sentinel, no TLS yet. Druid, Elasticsearch, OpenSearch and Trino are configured by host and port rather than a connection string. Druid, Elasticsearch and OpenSearch have no UPDATE and no CREATE TABLE in their own SQL at all, so those controls are reported as unsupported instead of failing when used. Cassandra publishes no row count or size that is true, so the object browser shows neither rather than a wrong number.

Repo: https://github.com/libredb/libredb-studio Demo: https://trial.libredb.org/ (admin@libredb.org / Admin!2026)


AI declaration, per the community rules:

  • Implementation (production code): Assisted - AI acted on part of some tasks, humans did the bulk. Measured on the public history: of 2,508 commits, 31 carry Co-Authored-By: Claude, 8 say “Generated with Claude Code”, and 35 mention Copilot. That is under 3% of commits, and a trailer is a floor rather than a full count.
  • Review: Assisted - Copilot appears in pull request review alongside human reviewers.

The project’s CONTRIBUTING.md states the policy in its own words: using an AI tool to help write a patch is fine, but you must have used the product, reproduced the problem yourself, and stand behind what you submit. Issues and pull requests opened by an autonomous agent are closed without review.

  • ultimaluz@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 hours ago

    I run postgres on a small hetzner vps for a browser game and right now it’s just ssh + psql, read only and with a statement timeout so I can’t break anything by accident. the column masking is the part that would make me try it, I look at prod with player data in it and honestly I’d rather not see some columns at all. one thing I’d want to know, if I close the tab in the middle of a long query does it get cancelled on the server? I had a script that got killed and its query kept running on prod for a while lol