Skip to content

Add LibreDB Studio to the GUI tools list - #475

Open
kaya-abdullah wants to merge 1 commit into
valkey-io:mainfrom
kaya-abdullah:add-libredb-studio-gui-tool
Open

kaya-abdullah wants to merge 1 commit into
valkey-io:mainfrom
kaya-abdullah:add-libredb-studio-gui-tool

Conversation

@kaya-abdullah

Copy link
Copy Markdown

LibreDB Studio is an open source SQL IDE that runs in the browser and is self-hosted next to the database rather than installed on a laptop. It connects to Valkey through ioredis, so this adds it under tools/gui next to the other GUI clients.

Against a Valkey server it groups key prefixes into a browsable tree using a non-blocking SCAN rather than KEYS, reads health and server metrics from INFO, the slow command log from SLOWLOG GET, and connected clients from CLIENT LIST. Commands are typed and run directly, either as plain text or as a JSON command object.

One caveat so it is not a surprise later: the overview panel reads redis_version from INFO, so a Valkey 9.1.1 server displays 7.2.4, the compatibility level rather than the Valkey release. Everything else was measured against Valkey 9.1.1 and behaved the same as it does against Redis.

Source and license: https://github.com/libredb/libredb-studio, MIT.

LibreDB Studio is an open-source, self-hosted SQL IDE that runs in the
browser. It connects to Valkey through the ioredis driver and exposes a
key browser built on a non-blocking SCAN, health and metrics from INFO,
and slow-query and client panels from SLOWLOG and CLIENT LIST.

Signed-off-by: Abdullah Kaya <abdullahk.0634@gmail.com>
@cevheri

cevheri commented Aug 26, 2026

Copy link
Copy Markdown

screenshot:
image

@cevheri

cevheri commented Aug 26, 2026

Copy link
Copy Markdown

@stockholmux stockholmux left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@stockholmux

Copy link
Copy Markdown
Member

@kaya-abdullah and @cevheri So... uh, I'm glad to merge this but I don't think we're currently using this part of the docs. I know there is work on putting that back in. Would you rather write a blog post about this tool? https://github.com/valkey-io/valkey-io.github.io/issues/new?template=blog_post_template.md

@kaya-abdullah

Copy link
Copy Markdown
Author

@stockholmux Thanks, and no strong preference either way, so please merge it if you're happy to, and I'll do the blog post as well.

For the post, I'll open an issue from the template with the topic, author, and a target date. The angle I'd propose is not another "here is a Valkey GUI" piece, since Valkey Admin already covers that ground, but the multi-engine one: how a team running Valkey next to Postgres or Mongo inspects the keyspace from the same browser tab, with SCAN rather than KEYS, and INFO, CLIENT LIST, and SLOWLOG behind the server, session and slow command views.

There's a write-up of the tool under third-party tools in the Redis docs if it helps to see the format: https://redis.io/docs/latest/develop/tools/#third-party-tools. The Valkey post would be written fresh, not ported from that.

@kaya-abdullah

Copy link
Copy Markdown
Author

Both are up: the proposal is valkey-io/valkey-io.github.io#648, and the post is valkey-io/valkey-io.github.io#649.

Reading the blog contributing guide shifted the angle a little. It now leads on not blocking the keyspace and on bounding the session with an ACL user, and the multi-engine part is down to a sentence, since the guide asks posts not to promote a product.

@kaya-abdullah

Copy link
Copy Markdown
Author

Hi @stockholmux, just following up on this one. Happy for you to merge it whenever works for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants