Redis — rdSQL Docs

Redis connections open a dedicated key browser — the same Explorer, shaped around keys instead of tables.

Connect#

Click New Connection and choose Redis as the Database Engine.
Fill in Host and Port (default 6379), plus the username and password if your server requires auth (Redis 6+ ACL users).
If the server requires TLS — Elasticache in-transit encryption, Redis Cloud, rediss:// endpoints — enable Use TLS.
Click Test, then Save.

The browser walks every logical database (DB 0–15) with SCAN, so browsing stays safe on large keyspaces:

Search — glob-pattern matching over keys (user:*, session:1001*), with type and TTL filters alongside.
Types — inspect and edit STRING, HASH, LIST, SET and ZSET values inline; hash fields and list items are edited one by one in place.
Per-key details — TTL, memory footprint and encoding are shown next to the data, so you can see what a key costs and when it expires.
Command log — every command rdSQL sends (SCAN cursors, timings, errors) lands in a dedicated log panel, so you can see exactly what ran against the server.
Health overview — the diagnostics view shows live server info for the connection: memory, clients, hit rate and more.

Creating a key opens a dialog that matches the type — e.g. a hash starts empty and you add field → value pairs, with an optional expiration.

Access denied — with Redis 6+ ACLs, the user needs read/write permissions on the keys you browse (+@read +@write and the key patterns involved).
Connection resets with TLS on — some servers use self-signed certificates; if the handshake fails, verify the endpoint really is TLS (rediss://) and not plain Redis.
Backup of Redis — Backup and Compare & Sync cover the SQL engines for now; Redis isn't a backup source or target yet.