// RESP · key-value, not SQL

Redis GUI for Mac, Windows and Linux

Redis isn't SQL, and SQLly doesn't pretend it is. Open any key in a key view that pages its value and edits it with the exact command shown first, type commands with completion from the server's own docs, connect to Redis Cluster and Sentinel, and watch the server live - plus Valkey, KeyDB, DragonflyDB, ElastiCache, MemoryDB and Azure Cache for Redis.

Connects over
RESP3 when the server offers it, RESP2 otherwise
Default port
6379
Sign-in
Password with an optional ACL user, or Microsoft Entra for Azure Redis
Topologies
Single server, Redis Cluster, or Sentinel by master name
Paste a URL
redis://, rediss:// or redis+sentinel://

What SQLly does for Redis

Redis is the one engine in SQLly that isn’t a SQL database. So instead of forcing it into tables, SQLly gives it a key view that edits every type, a command editor with real completion, Cluster and Sentinel connections, and live tools that each have a cap and a stop - and the SQL-only tools say plainly why they don’t apply. The Redis GUI page walks through all of it in more detail.

A key view that edits every type

Double-click a key for its type, TTL, encoding, memory and length, with the value in pages of 1,000 and a showing N of M count. Edit strings (keeping their expiry), hashes, lists, sets, sorted sets and JSON documents; each form shows the exact command before Run.

Key view →

Streams and consumer groups

A stream opens with Entries, Groups, Consumers and Pending tabs: lag per group, idle time per consumer, and every unacknowledged entry with its owner, so a dead consumer stands out. Acknowledge, claim, auto-claim, trim and manage groups from the view.

Streams →

Values stay bytes

00014 stays 00014, and binary values are shown and edited as hex. The value viewer decodes JSON, MessagePack, Base64, Protobuf, gzip, zstd, LZ4, deflate, PHP, Java and pickle payloads without changing the stored bytes.

Value formats →

Command IntelliSense

A query tab runs one command per line in redis-cli syntax and completes commands, the options that still fit, subcommands, and key names the explorer already scanned. Hover a command for its syntax and a Write, Destructive or Blocking badge.

Command IntelliSense →

Redis Stack as real grids

FT.SEARCH returns one row per document, TS.RANGE a timestamp column you can chart, and the JSON, Bloom, cuckoo, top-k and count-min commands the columns their replies imply. Search indexes get an Indexes folder with query, explain, profile and a reviewed drop.

Redis Stack modules →

Cluster and Sentinel

Every command goes to the node that owns its slot, a node map rewrites addresses your machine cannot dial, and each node gets its own SSH forward. Sentinel connections find the master by name, can read from a replica, and never re-run a write after a failover.

Cluster and Sentinel →

Rename, copy and export keys

Rename… refuses to overwrite unless you allow it, Copy to Database… and Copy to Connection… carry the value and expiry, and Export as Command File… writes a folder as commands Import Command File… runs back byte for byte.

Bulk actions →

Live tools with a stop

The Profiler is a time-boxed MONITOR on its own connection; the Pub/Sub viewer watches channels, patterns, sharded channels and every key event on a database. The memory analyzer, bulk delete and the slow log threshold round it out.

Redis tools →

An ACL page in the Security tool

Every ACL user with its key, channel and command rules and selectors, next to the server’s recent access denials. Add, Edit and Delete write a reviewed script into a query tab, with new passwords as hashes.

ACL users →

Guardrails for commands

A read-only connection - and every query the AI composes - allows read-only commands only. FLUSHALL, FLUSHDB, DEL, CONFIG SET and SHUTDOWN ask first, and SUBSCRIBE, MONITOR or a blocking pop with no timeout are refused before they can hang the tab.

Read-only connections →
Screenshot to comeredis-key-view-hash-edit.webp — the key view on a hash: header strip, a paged grid of fields, and the Add field form showing the exact HSET above Run
The key view: type, TTL, encoding, memory and length up top, the value in pages, and the command shown before it runs.

Connections that tell you what went wrong

Test Connection walks a Redis connection one step at a time - name lookup, tunnel or proxy, TCP, TLS, sign-in, protocol and ping, database, cluster state - and an error starts with the step that failed, so “could not connect” becomes TLS failed: … or AUTH failed: …. Connections use RESP3 when the server offers it, name themselves so you can find them in CLIENT LIST, and give up on a command that gets no reply within the query timeout instead of hanging. SSH tunnels send a keepalive after 30 seconds of silence and reopen after a drop without re-running anything.

Screenshot to comeredis-test-connection-steps.webp — the diagnostic log after Test on the TLS fixture, one line per step from Resolve to Session, with the TLS step naming the version, cipher and certificate check
Test Connection on Redis logs every step, so the first failing one says what to fix.

Azure Cache for Redis and Azure Managed Redis can sign in with Microsoft Entra, and TLS can trust your computer’s certificate store as well as a CA file - see TLS modes.

Connect to Redis

  1. Download SQLly for macOS, Windows or Linux from the download page and open it.
  2. Create a connection and pick Redis - or Valkey, KeyDB, DragonflyDB, Amazon ElastiCache or Amazon MemoryDB if that is what you run. Moving from Redis Insight? Import From Other Tools… reads its database export, TLS settings and passwords included.
  3. Enter host and port (6379), an ACL user name if your server uses one, the password, and optionally a logical database number - or paste a redis://user:password@host:6379/2, rediss:// or redis+sentinel:// URL. For a cluster, list several seed hosts separated by commas.
  4. Choose a TLS mode. Anything but Disable switches to Redis’s TLS handshake, the same as a rediss:// URL; MemoryDB requires it. SSH tunnels, proxies and Kubernetes port-forwards work as they do for the SQL engines.
  5. Test, save and connect. Expand the connection to browse keys and double-click one to open it, or type HGETALL user:1 in a query tab and run it.
Screenshot to comeredis-explorer-key-browser.webp — the explorer on the standalone fixture with db3 named “sessions”, keys folded by prefix with type and TTL beside each, and the note row at the bottom of a long listing
The key browser folds keys by prefix and says exactly how much of a long listing you are looking at.

Every SQLly tool on Redis

This is the same engine matrix the app uses to enable or disable its menus, so what you read here is what you get. Where a tool doesn’t apply to Redis, the app says why - and so do we.

SQLly tools and whether they work on Redis
Tool Redis
Explorer, IntelliSense and hover cards Yes A key browser instead of a SQL catalog - logical databases, keys folded by prefix, each key's type and TTL - and command IntelliSense: commands, options, subcommands and scanned key names, with syntax and a Write, Destructive or Blocking badge on hover.
Activity Monitor Yes CLIENT LIST, with kill, plus the Profiler and Pub/Sub viewer tabs.
Query Insights Yes The slow log, with its threshold shown and changed through a reviewed CONFIG SET.
Server Dashboard Yes INFO; on a cluster connection it links to the Cluster Topology view.
Disk Usage and Object Browser Partial Disk Usage shows memory per logical database and the Memory Analyzer breaks it down by type, top keys and TTL; the Object Browser does not apply, so browse keys in the explorer.
Security editor (users, roles, grants) Yes The ACL page: every ACL user and the recent access denials, with reviewed ACL SETUSER / ACL DELUSER scripts. Not offered on ElastiCache and MemoryDB, whose users AWS manages.
SSH tunnels, proxies and Kubernetes port-forward Yes Cluster connections open a forward for every node; Sentinel connections dial directly and refuse tunnels and proxies.
Read-only connections Yes Only read-only commands are allowed; destructive ones such as FLUSHALL go through confirmation.
Edit rows in the results grid No Redis has no rows to edit; open a key from the explorer to change its value in the key view, or use SET, HSET and friends in a query tab.
Estimated execution plans No Redis commands have no execution plan; SLOWLOG GET shows their timings.
Actual (executed) plans No Redis commands have no execution plan; SLOWLOG GET shows their timings.
Maintenance menu No Redis has no vacuum, analyze or reindex verbs to offer.
Schema Compare and Schema History No Redis has no schema to compare; keys are the whole structure.
Data Compare No Redis has no tables to compare; use the key browser and GET / HGETALL.
Data Transfer No Redis has no tables to transfer; right-click a key and choose Copy to Connection… (DUMP / RESTORE), or use Export as Command File… and run the file on the other server with Import Command File….
Test Data Generator No Redis has no tables to fill; write keys with SET / HSET in a query tab.
Table Structure Editor No A Redis key's type is set by the command that creates it.
Index Analyzer No Redis has no indexes to analyze; every key is looked up by name. Search indexes from Redis Stack are listed in the explorer's Indexes folder.
Backup / Restore No Redis snapshots itself on the server: run BGSAVE or BGREWRITEAOF in a query tab.
Create and drop database dialogs No Redis databases are fixed numbered slots; there is nothing to create or drop. Name them and choose which ones the explorer shows instead.
Procedure Mode No Redis has no stored procedures.
SQL Agent, Extended Events and guided designers No SQL Server and Azure SQL only.
Auto-rollback safety wrap No Redis has nothing to roll back, so the wrap refuses anything but read-only commands.

Hosted and compatible engines

These are choices in SQLly’s connection editor in their own right. Each one sets the right port and encryption default, and a short note under the connection options says what differs from plain Redis.

  • Valkey
  • KeyDB
  • DragonflyDB
  • Amazon ElastiCache
  • Amazon MemoryDB

Questions about Redis in SQLly

Is SQLly a Redis GUI, or only a SQL client?

Both. SQLly connects to Redis natively. Double-click a key and it opens in a key view with its type, TTL, encoding, memory and length, the value in pages, and the edits its type allows; a query tab runs one command per line in redis-cli syntax with command IntelliSense. The SQL-only tools - plans, schema compare and the structure editor - say why they do not apply.

Can I edit Redis values without typing commands?

Yes. The key view edits strings, hashes, lists, sets, sorted sets and JSON documents, and streams get Entries, Groups, Consumers and Pending tabs. Every edit shows the exact command before it runs, is refused on read-only and locked production connections, and asks for a second click wherever a query tab would confirm. Values are handled as bytes, so 00014 is never turned into a number.

Does SQLly support Redis Cluster and Sentinel?

Yes. A Redis connection can list several seed nodes and route every command to the node that owns its slot, with a node map for clusters whose nodes announce addresses you cannot dial and a separate SSH forward per node. Sentinel connections find the current master by name, can read from a replica, and never re-run a write after a failover.

Does SQLly work with Valkey, ElastiCache, MemoryDB and Azure Redis?

Yes. Valkey, KeyDB, DragonflyDB, Amazon ElastiCache and Amazon MemoryDB are choices in the connection editor, and Azure Cache for Redis and Azure Managed Redis can sign in with Microsoft Entra. Valkey, KeyDB and DragonflyDB were run against SQLly's live Redis suites; ElastiCache, MemoryDB and Azure Managed Redis have not been tested against a live instance yet.

Can a read-only Redis connection still change data?

No. With the SELECT-only lock on, and for queries composed by the AI, only read-only commands are allowed, and the key view, bulk actions and imports refuse to write. On a connection that can write, destructive commands such as FLUSHALL, FLUSHDB, DEL, CONFIG SET and SHUTDOWN go through the usual confirmation first.

Can I run SUBSCRIBE or MONITOR in SQLly?

Not in a query tab: commands that would never finish - SUBSCRIBE, MONITOR, or a blocking pop with no timeout - are refused before they are sent, so a tab cannot hang. Use the Pub/Sub viewer and the Profiler instead; each opens its own connection with a cap and a stop.

Read more

// try it on your own Redis

Bring your Redis home to the pig

SQLly is free to start on macOS, Windows and Linux, with no account required.