Download
Visual Valkey Workspace

Valkey GUI Client for Windows, macOS, and Linux

VisuaLeaf is one visual workspace for Valkey, the open-source, BSD-licensed key-value store that carries Redis forward: scan the keyspace by pattern without blocking the server, open hashes, lists, sets, JSON documents and Bloom filters in the editor that fits them, edit values and TTLs in place, run commands with a real console, and read COMMANDLOG — instead of piecing the picture together one valkey-cli call at a time.

Free to start No credit card required Works on Windows, macOS and Linux
The VisuaLeaf key browser on Valkey 9.1: a scanned keyspace with STRING, HASH, ZSET, SET, LIST, JSON, BLOOM and STREAM keys, and the hash user:1001 open with a JSON field expanded as a tree

Valkey Kept the Protocol. It Also Kept the Blind Spots

Valkey is wire-compatible with Redis, which is why moving to it is easy — and why looking inside it is still a text protocol. VisuaLeaf turns a Valkey instance into a workspace: browse the keyspace by pattern, open a value in the editor that fits its type, watch TTLs, and see what the server itself is struggling with.

KEYS is still the command you must not run

The obvious way to see what is in a database is the one that blocks the server, so exploring production means remembering to reach for SCAN and paging cursors by hand.

Redis clients see Redis 7.2.4

For compatibility Valkey reports a fixed redis_version, so a client built only for Redis shows the wrong product and the wrong version for every server you open.

Modules add types a plain client cannot read

valkey-json and valkey-bloom store documents and filters under their own TYPE names, which come back from most clients as opaque values.

Big payloads hide in the command stream

Valkey 8.1 added COMMANDLOG to catch oversized requests and replies, but reading it still means COMMANDLOG GET and a wall of nested reply lines.

A visual workflow for Valkey

Scan the keyspace safely, open each type in the editor that fits it, edit values and TTLs, run commands, test ACL rules, and read COMMANDLOG — all in one workspace.

Five Workspaces Behind One Valkey Connection

A Valkey connection does not open a table grid or a schema diagram, because Valkey has neither. It opens the workspaces below, each built around the way Valkey actually stores and guards data.

Key Browser

Scan the keyspace by glob pattern with cursor paging, never KEYS *, and read each key with its type and TTL before you touch it.

  • Pattern box, e.g. session:*, with incremental loading
  • Filter the list down to a single type, including JSON and Bloom
  • Shift-click ranges and select-all for bulk work
  • Rename, delete, create a key, export or import matching keys as JSON
The VisuaLeaf key browser on Valkey with a valkey-bloom filter open: capacity, size, error rate and items inserted, with Check and Add

Value Filter

Drag a field out of the tree to build a condition and narrow the keyspace by what is inside the value, not just by key pattern. Stack conditions on a hash field, or on a JSON path inside one.

  • AND-stacked conditions, each on its own field
  • JSON paths into a hash field, e.g. groups[0].type
  • Hash keys only, and values are scanned client-side — Valkey has no server-side index for this
The VisuaLeaf Value Filter panel building an AND condition on a hash field to narrow a Valkey keyspace

CLI

A real command console for the times a GUI is the wrong tool, sitting in the same workspace as the browser you were just using.

  • Searchable command reference, click to insert into the prompt
  • Configurable scrollback buffer
  • Where module commands such as JSON.* and BF.* run
The VisuaLeaf CLI on Valkey running JSON.GET, BF.EXISTS, ZREVRANGE, TTL and HGETALL, each reply numbered with its timing

Security

ACL rule strings are write-only in practice. This screen reads them back as permissions, and lets you check one before you trust it.

  • Users with status, password or passwordless, and effective rule
  • Command permissions and key patterns, allow-all or deny-all
  • Pub/Sub channels and selectors
  • Permission tester built on ACL DRYRUN
The VisuaLeaf security screen on Valkey 9.1.3 listing four ACL users with their command rules and key patterns, and an ACL DRYRUN test refusing SET for the analytics user

Server

The INFO dashboard that knows it is talking to Valkey, on one auto-refreshing screen instead of a wall of key:value lines.

  • The real valkey_version, not the 7.2.4 compatibility level
  • Memory, clients, hit rate, ops/sec and fragmentation at a glance
  • Loaded modules, such as json, bf and search
  • Slow log, and cluster topology with node role, slots and link state
The VisuaLeaf Server screen for Valkey: version 9.1.3, uptime, clients, memory, keys, hit rate and loaded modules json, ldap, bf, search and lua

COMMANDLOG

Valkey 8.1 added a log for the commands that hurt without being slow: the ones that send or return too much. VisuaLeaf reads it as a table.

  • Large Requests and Large Replies tabs beside the Slow Log
  • Size, command, arguments, client address and time for each entry
  • Offered only on servers that have COMMANDLOG
The VisuaLeaf COMMANDLOG large-reply table on Valkey, listing ZRANGE, SORT, LRANGE, HGETALL and GET replies with their sizes and clients

Valkey has no query language, and we do not pretend otherwise

You cannot filter across values server-side in Valkey the way you can with SQL or an aggregation pipeline. VisuaLeaf gives you what is genuinely available instead: pattern scanning over keys, client-side Value Filter conditions on hash fields and JSON paths, and the CLI for module commands when the module is loaded.

The Editor Follows the Type

There is no single grid that fits a Valkey value. Open a key and the pane that appears is the one that matches what the key holds.

Every editor also carries TTL view and set, rename, delete and copy-key. JSON and Bloom need valkey-json and valkey-bloom loaded, as in valkey-bundle.
Valkey typeWhat opens
string A text editor that detects JSON and switches to a JSON mode, so a cached payload reads as structure rather than one long line.
hash Field and value pairs, editable in Tree, Form or raw JSON view. Per-field TTL is shown and settable where the server supports it.
list An ordered, index-addressable editor, so position is preserved rather than flattened into reply lines.
set A member list with add and remove, and undo on removal.
zset Members beside their scores, sortable by score.
stream Entries with their IDs and raw fields. A dedicated timeline editor is on the roadmap, not shipped.
json A valkey-json document in a JSON editor with Format; Save writes the whole document back with JSON.SET at $.
bloom A valkey-bloom filter’s capacity, size, error rate and items inserted, with Check and Add. A Bloom filter cannot list or remove its items, so neither does the editor.

A Visual Workflow for Everyday Valkey Tasks

VisuaLeaf connects the steps Valkey users usually handle separately: scan the keyspace, narrow it by what is inside the values, drop into a console when you need one, and check who is allowed to run what.

Built for Different Valkey Users

Whether you are migrating off Redis, debugging a cache, tightening ACLs, or learning what the data types actually do, VisuaLeaf gives you a clearer way to work with Valkey.

Developers

Inspect the keys your app writes, check a TTL, and fix a bad cache entry without opening a terminal.

Platform and SRE Teams

Check a migrated keyspace side by side with the Redis it came from, read COMMANDLOG and the slow log, and review ACL users from one workspace.

Data Analysts

Open sorted sets, streams and JSON documents as readable structures, and export what you find without writing a script.

Students and Beginners

Learn the Valkey data types visually, see what a hash or a stream really looks like, and try commands with instant feedback.

Frequently Asked Questions

Is VisuaLeaf a good Valkey GUI?
Yes. VisuaLeaf gives Valkey a visual workspace: scan the keyspace by pattern with cursor-based paging instead of KEYS, see every key with its type and TTL, open hashes, lists, sets and sorted sets in a tree, form or raw JSON editor, read valkey-json documents and valkey-bloom filters, edit values and expiry in place, run commands in a console, and test ACL rules with ACL DRYRUN. It runs natively on Windows, macOS and Linux.
Does VisuaLeaf know it is talking to Valkey rather than Redis?
Yes. Pick the Valkey card when you add a connection, or let Test Connection detect it: the connection is labelled Valkey with its own mark, and the Server screen reports the real valkey_version instead of the fixed 7.2.4 Redis compatibility level Valkey advertises in redis_version.
Can I browse a large Valkey keyspace without blocking the server?
Yes. VisuaLeaf browses with cursor-based SCAN and glob patterns rather than KEYS, so it pages through a large keyspace incrementally instead of asking the server for every key at once. Filter by pattern or by type, switch between database indexes, and keep exploring while the instance stays responsive.
Does it support valkey-json and valkey-bloom?
Yes. When the modules are loaded — as in the valkey-bundle image — JSON documents open in a JSON editor that saves the whole document back with JSON.SET, Bloom filters show their capacity, error rate and item count with Check and Add, the key browser can filter to either type, and you can create new JSON and Bloom keys from the New Key dialog.
Can I see Valkey COMMANDLOG from the GUI?
On Valkey 8.1 and later, yes. The Server screen reads COMMANDLOG and shows the largest requests and the largest replies alongside the slow log, so a client sending oversized payloads or a key returning megabytes is visible without running COMMANDLOG GET by hand. On servers without COMMANDLOG those panels are simply not offered.
Can I manage Valkey ACL users and permissions?
Yes. The security screen lists ACL users with their status, password state, command permissions and key patterns, lets you create, alter, enable, disable and drop them, and includes a permission tester built on ACL DRYRUN, so you can check a command against a user before relying on it.
Does it connect to Valkey over TLS, Sentinel, cluster, or a managed service?
Yes. VisuaLeaf connects to local, Docker, self-hosted and managed Valkey — including services such as Amazon ElastiCache and MemoryDB for Valkey — in standalone, Sentinel or cluster mode, directly or over TLS. Point it at a host, port (6379 by default) and database index with your credentials and the keyspace is browsable immediately.

More Than a Valkey Client

VisuaLeaf started as a MongoDB workspace and grew into a multi-database visual environment. One app, one workflow, across the databases your team actually uses.

And VisuaLeaf does not leave you staring at a wall of protocol replies. It visualizes everything — Valkey values become trees and typed editors, database schemas become interactive diagrams, and SQL and MongoDB query results become charts and dashboards.

MongoDB MySQL MariaDB SQL Server Azure Cosmos DB Amazon DocumentDB Redis SQLite

Built by Developers, For Developers

VisuaLeaf is made by an independent software studio that ships often and listens to the developers who use it every day.

Ready to Work Visually with Valkey?

Download VisuaLeaf Community Edition and scan the keyspace safely, open every data type in the editor that fits it, edit values and TTLs, and read COMMANDLOG in one visual workspace.

Download Free Community Edition
No credit card required
A valkey-json order document open in the VisuaLeaf JSON editor