Work with Redis keys in the systems that depend on them.

Browse logical databases and keys, inspect and edit values, and keep Redis work connected to the project, people, and downstream tools that rely on it.

See WhoDB with Redis→View all integrations→

Type: Key-value store and cache
Explore: Logical database → key
Connect with: Hostname, credentials, port, logical database, and supported TLS options

What WhoDB lets your team do with Redis

Move from exploring Redis to building useful workflows, shared tools, and trusted data products—all without losing the context behind the work.

Updated August 25, 2026. Available actions depend on the permissions granted to your connected account.

Find keys without treating Redis like SQL

Browse logical databases and keys through a key-value model designed for Redis rather than forcing cache data into table and column concepts that do not fit.

Inspect the value behind a key

Move from the key list into its metadata and current value so operational checks do not require a separate command-line session for every lookup.

Make focused data changes

Create keys, update existing values, and delete data when the connected Redis account has permission.

Keep cache work beside the wider system

Place Redis in the same WhoDB project as the databases and services it accelerates, giving the team shared ownership and a clearer view of the wider system.

From connected data to a workflow people can trust

Connect the Redis deployment

Use the host, credentials, logical database, port, and supported TLS settings for Redis or a compatible managed service.

Browse the right logical database

Move from a logical database into its keys and inspect values through a workflow designed for Redis.

Review before changing a value

Keep the key, metadata, and current data visible while creating, updating, or deleting the focused record.

Keep the wider system visible

Keep the Redis source inside the project where ownership, related databases, workflows, and downstream tools are already understood.

A Redis GUI that stays honest about Redis

WhoDB gives your team a focused Redis browser and editor alongside the databases, services, and workflows that depend on the cache.

That connection to the wider system makes operational checks easier: people can inspect and update keys, then continue working across the rest of the stack without switching environments.

WhoDB is a strong fit for

Teams checking application cache and operational key data
Engineers working across Redis and its backing databases
Organizations that want shared source ownership and context
Focused value changes without a separate tool for every system

Explore WhoDB features→Review security→

Redis integration questions

Straight answers about setup, everyday tasks, and how WhoDB fits into your workflow.

What Redis objects can WhoDB browse?

WhoDB follows Redis's logical database and key hierarchy. Teams can inspect key metadata and values without translating the source into relational tables.

Can WhoDB create, update, and delete Redis keys?

Yes. Teams can create keys, read and update values, and delete data when the connected Redis account has permission.

Does WhoDB run SQL queries against Redis?

No. WhoDB's Redis experience focuses on browsing keys and working with values. SQL queries, relational graphs, imports, mock data, and database chat are available for other kinds of systems where those tools fit.

Does WhoDB support Redis-compatible services?

Yes. WhoDB supports Redis alongside compatible or managed services such as Valkey, Dragonfly, MemoryDB, ElastiCache, and Azure Managed Redis. Connection settings vary by service.

Explore another source

Give your team one place to explore, understand, and build with data across the systems you already use.

See every supported source →