VisuaLeaf is one visual workspace for Redis: scan the keyspace by pattern without blocking the server, open hashes, lists, sets and sorted sets in a tree, form or raw JSON editor, filter keys by what is inside the value, edit values and TTLs in place, run commands with a real console, and test ACL rules before you apply them — instead of piecing the picture together one redis-cli call at a time.
Redis gives you eight data types, per-key expiry and a millisecond command loop, then hands you a text protocol as the only way to see any of it. VisuaLeaf turns a Redis instance into a workspace: browse the keyspace by pattern, open a value in the editor that fits its type, watch TTLs, and read ACL rules back as permissions.
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.
Reading a value means first knowing whether it is a hash, a list, a set, a sorted set or a stream, because HGETALL, LRANGE and XRANGE are not interchangeable.
TTLs are the whole point of a cache and they are stored per key, so nothing shows you which keys are about to vanish without querying each one.
Redis 6 gave you real users, command categories and key patterns — all declared in ACL rule strings that nobody can read back at a glance.
Scan the keyspace safely, open each type in the editor that fits it, edit values and TTLs, run commands, and test ACL rules — all in one workspace.
A Redis connection does not open a table grid or a schema diagram, because Redis has neither. It opens the workspaces below, each built around the way Redis actually stores and guards data.
Scan the keyspace by glob pattern with cursor paging, never KEYS *, and read each key with its type and TTL before you touch it.
user:*, with incremental loading
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.
groups[0].type
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.
FT.* and JSON.* run
ACL rule strings are write-only in practice. This screen reads them back as permissions, and lets you check one before you trust it.
ACL DRYRUN
The INFO dashboard, the slow log and the cluster picture on one auto-refreshing screen instead of three separate commands: memory, clients, stats, replication and persistence; the fifty most recent slow-log entries; loaded modules; and cluster topology with node ID, role, slots, endpoint and link state.
You cannot filter across values server-side in vanilla Redis 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 RediSearch (FT.*) when the module is installed.
There is no single grid that fits a Redis value. Open a key and the pane that appears is the one that matches what the key holds.
| Redis type | What 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. |
VisuaLeaf connects the steps Redis 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.
Scan the keyspace by pattern with cursor paging, filter down to one type, and read every key with its type and TTL before you touch it.
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. Hash keys only, and values are scanned client-side, since Redis has no server-side index for this.
Drop into a real console when a GUI is the wrong tool, with a searchable command reference you can click straight into the prompt and a scrollback buffer you control.
Read ACL users back as permissions rather than rule strings, then check a command against a user with the ACL DRYRUN tester before you rely on it.
Whether you debug a cache, inspect a queue, tighten ACLs, or learn what the data types actually do, VisuaLeaf gives you a clearer way to work with Redis.
Inspect the keys your app writes, check a TTL, and fix a bad cache entry without opening a terminal.
Scan production safely, watch memory and expiry, review ACL users, and read server info from one workspace.
Open sorted sets and streams as readable structures, and export what you find without writing a script.
Learn the Redis data types visually, see what a hash or a stream really looks like, and try commands with instant feedback.
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 — Redis values become trees and typed editors, database schemas become interactive diagrams, and SQL and MongoDB query results become charts and dashboards.
VisuaLeaf is made by an independent software studio that ships often and listens to the developers who use it every day.
Download VisuaLeaf Community Edition and scan the keyspace safely, open every data type in the editor that fits it, edit values and TTLs, and test ACL rules in one visual workspace.
Download Free Community Edition