Redis Insight
A graphical Redis client for browsing keys, visualizing data types, running Workbench commands, analyzing queries, managing Redis Search and inspecting slow queries and memory use.
What Redis Insight provides
Redis Insight connects to an existing Redis deployment and adds a graphical view of keys, data types, TTLs, memory information, Workbench commands, Redis Search indexes and stream data. It is a client or web application, not a Redis server and not an independent permission boundary.
Data and network boundaries
The interface can inspect or change data according to the connected ACL user. Connection credentials, Workbench history and other settings can be stored in a local SQLite database. A Docker deployment should use a persistent volume and a fixed encryption key, while its listening address must be protected by network controls, TLS, identity access and Redis ACL.
Maintenance note
This page reviews Redis Insight 3.6.0, desktop and container deployment, Linux ARM64 packages, ACL and TLS, SQLite storage and SSPL or commercial licensing boundaries. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Redis Insight to this cloud drive
Baidu Netdisk
Save Redis Insight to this cloud drive
Redis Insight 3.6.0 least-privilege connection and diagnostics guide
Connect to an isolated test Redis with a narrowly scoped ACL user, verify Browser and Workbench using harmless keys, then open only the commands required for production diagnosis.
Before you start
- Prepare the Redis host, port, TLS CA, username, ACL key pattern and topology information for a cluster, Sentinel or cloud service.
- For Docker or Kubernetes, prepare a persistent volume, a strong random encryption key and a protected proxy or identity entry point.
- Confirm backups, memory limits and query impact before running scans or large-key reads in production.
Installation steps
- 01
Choose the 3.6.0 deployment
Use a desktop build for personal administration or a pinned Docker or Kubernetes deployment for a controlled team environment, matching the target architecture.
- 02
Persist data and restrict listening
Mount the application data directory, keep the same RI_ENCRYPTION_KEY across restarts, and limit host and port exposure through the proxy and firewall.
- 03
Create a least-privilege connection
Create separate ACL users for browsing, diagnosis and changes, enable TLS, verify the certificate, and avoid saving a shared administrator password.
Quick start
- 01
Verify the connection and key pattern
Start with PING and read-only commands, confirm database number, cluster mode and allowed key prefix, and use pagination rather than a full key dump.
- 02
Inspect a small set of data types
Review a few String, Hash, JSON or Stream keys with TTL, memory and encoding information, copying to a test key before editing or deleting.
- 03
Use Workbench and diagnostics carefully
Run small read-only commands first, limit scans and Search plans, and watch server latency while checking slow queries or memory information.
Usage tips
- Redis Insight exposes whatever the ACL user can do; the client cannot revoke permissions already granted by the server.
- Large scans, KEYS-style commands, big-key reads and complex Search queries can affect production latency.
- SQLite data, logs, query history and exports may contain key names or credentials, so protect and redact them in backups and tickets.
Troubleshooting and uninstall
Why did connections disappear after a Docker restart?
Check that the same data volume is mounted and that RI_ENCRYPTION_KEY exactly matches the key used when the data was written. Back up the volume before changing variables.
Why do some commands return a permission error?
Compare the task with the Redis ACL command categories and key patterns, add only the smallest required permission, and reconnect to verify the change.
- Export settings and revoke accessSave connection notes without passwords and revoke dedicated ACL users, cloud tokens and certificate grants that are no longer needed.
- Stop the app and handle data volumesStop the desktop process or containers, back up required diagnostics, then remove SQLite data, logs, exports, volumes and deployment keys according to the retention plan.
Frequently asked questions
Does Redis Insight include a Redis server?
No. It connects to Redis Open Source, Redis Software or Redis Cloud and provides an administration and analysis interface.
Should a Docker deployment be exposed directly to the internet?
Treat the interface as an administrative surface. Put it behind a protected network or identity proxy, use TLS and apply least-privilege Redis ACL.
Where are connection credentials stored?
Desktop and server deployments can store connection information and Workbench history in local SQLite data; Docker deployments can protect it with a fixed RI_ENCRYPTION_KEY.