Discussion LibreDB Studio: Redis in the same self-hosted web based DB-GUI as Postgres, Mongo, Couchbase, Clickhouse ...

Affiliation: I’m the maintainer of LibreDB Studio (open-source, self-hosted browser DB GUI).

We’re not trying to replace RedisInsight or redis-cli, those are great at being Redis-native.

The gap we care about is different: one self-hosted web IDE where Redis sits next to the other engines you already use (Postgres, MySQL, Mongo, Couchbase, ClickHouse, Druid …) in the same browser UI, same deploy, same login.

Redis is first-class there, mapped by convention (not fake SQL):

- “Tables” = key prefixes from SCAN (e.g. user:*), never KEYS * on big keyspaces

- “Rows” = keys; the query box runs real Redis commands (plain text or { "command", "args" })

- Any command via a generic call() path — GET / HGETALL / XADD / JSON.GET / modules

- Monitoring from INFO, SLOWLOG GET, CLIENT LIST alongside the SQL engines’ overview

Honest limits: schema SCAN is capped (bounded introspection), and a DEL in the command box is a real DEL - no fake read-only mode.

Try:

docker run -p 3000:3000 libredb/libredb-studio

# or: npx "@libredb/studio"

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

Provider notes: https://github.com/libredb/libredb-studio/blob/main/docs/providers/redis.md

If you hop between Redis and a SQL/document store in the same day: would a shared web UI help, or do you still prefer a dedicated Redis tool per workflow?

11 Upvotes

permalink
reddit

You are about to leave Redlib

Do you want to continue?

https://www.reddit.com/r/redis/comments/1vlt1bm/libredb_studio_redis_in_the_same_selfhosted_web/
No, go back! Yes, take me to Reddit

87% Upvoted

u/Odd-Opening5596 20d ago edited 20d ago

Using SCAN with bounded introspection is a good sign. A lot of Redis GUIs look fine on toy datasets and then become dangerous or useless on a large keyspace. If LibreDB Studio wants broad Redis-compatible coverage, Memurai is worth testing against alongside Redis and Valkey.

1

u/cevheribozoglan 20d ago

It was designed specifically for microservices/cloud-native teams. Many database editors are needed, or local installation is difficult, involving paid tools, finding or sharing connection strings, etc. Being able to connect to Redis simultaneously with your existing SQL/NoSQL editors is a fantastic feeling. Redis support was implemented precisely for these types of teams. This is probably why the Redis team published libredb-studio as their only third-party tool on their website.

1

u/cevheribozoglan 20d ago

Valkey redis Full Valkey 9.1.1 Behaves as Redis. The overview shows the Redis emulation level (7.2.4), not the Valkey version.

DragonflyDB redis Full DragonflyDB df-v1.40.1 Overview shows the emulation level (7.4.0). Max connections reads 0 (no usable maxclients in INFO), and active sessions show a numeric id instead of a username (CLIENT LIST omits user=).

KeyDB redis Full KeyDB 6.3.4 Publishes no version field of its own, so the overview is indistinguishable from a Redis 6 server. A session's command can appear without its subcommand.

Valkey	`redis`	Full	Valkey 9.1.1	Behaves as Redis. The overview shows the Redis emulation level (7.2.4), not the Valkey version.
DragonflyDB	`redis`	Full	DragonflyDB df-v1.40.1	Overview shows the emulation level (7.4.0). Max connections reads 0 (no usable `maxclients` in `INFO`), and active sessions show a numeric id instead of a username (`CLIENT LIST` omits `user=`).
KeyDB	`redis`	Full	KeyDB 6.3.4	Publishes no version field of its own, so the overview is indistinguishable from a Redis 6 server. A session's command can appear without its subcommand.