InletRedis GUI for Mac
Browse keys by namespace as tables, edit values, TTLs and names without overwriting anyone’s change, and run redis-cli commands with completion. Redis, Valkey and Redis Cluster.
Free for personal use · macOS 26 Tahoe or later · Apple silicon and Intel
Tested on Redis 8 and Valkey 8
Any server that speaks RESP2 or RESP3 connects, such as Redis Cloud, Upstash and ElastiCache. Clusters connect through Redis Cluster, in Pro.
What you can do with Redis
Keys by namespace
The sidebar groups keys by prefix (user:*, session:*). A namespace opens as a grid of key, type, TTL, size and value, and hashes show their fields as columns.
Find any key
Pages come from SCAN, so nothing blocks the server. Filter by a MATCH pattern, by type, or by any value.
Edits that can’t collide
Edit values, TTLs and key names. Each change runs as a Lua script that checks what you loaded first, so a value someone changed isn’t overwritten.
redis-cli, with completion
Commands one a line, completing commands, namespaces and hash fields. HGETALL, ZRANGE WITHSCORES, INFO and CLIENT LIST come back as tables.
Redis ClusterPro
Connect to any node and Inlet finds the rest. Commands go to their keys’ node; MGET, MSET and DEL across slots are split for you.
SUBSCRIBE and MONITOR
Stream until you stop them. Stop also wakes a blocked BLPOP and kills a long script.
Safe on production
Nothing changes until you say so, and nothing you save overwrites a change you never saw. How Inlet keeps data safe
Production opens read-only
Write and admin commands are refused before they’re sent. Unlock for ten minutes when you mean to change something.
Changes wait until you save
Edited values, TTLs and new keys wait, marked in colour, until ⌘S saves them.
No lost updates
Each change compares the key with what you loaded, atomically, before it writes.
Connecting
Paste a redis:// or rediss:// URL and Inlet fills in the form.
ACL users and TLSA user and password, or a password alone. rediss:// is verified TLS, with client certificates when you need them.
SSH tunnelsProThrough the ssh on your Mac. On a cluster, one sign-in with a forward for each node.
Import what you haveFrom TablePlus.
rediss://default:•••@eu1-example-12345.upstash.io:6379redis://app:•••@redis.example.com:6379/0redis://localhost:6379
Redis errors, explained
27 Redis error messages, each reproduced on a real server: what it means, why it happens and the fix. Inlet links to them when they happen.
- Could not connect to Redis at 127.0.0.1:6379: Connection refusedYour client reached the machine, but nothing there accepted a connection on that port, so the operating system refused it. Redis isn’t running, the port is wrong or not published from Docker, or Redis listens only on other addresses.
- NOAUTH Authentication required.The server needs you to sign in, and your connection sent a command before it did. Give your client the password (and user name, for an ACL user), or send AUTH first.
- WRONGPASS invalid username-password pair or user is disabled.The server didn’t accept the user name and password you signed in with. Redis gives the same answer for a wrong password, a user that doesn’t exist and a user that’s turned off, so check all three.
- WRONGTYPE Operation against a key holding the wrong kind of valueYou ran a command for one data type on a key that holds another, such as GET on a hash. Nothing changed. Check the key with TYPE, then use that type’s commands or give the two kinds of data different key names.
- OOM command not allowed when used memory > 'maxmemory'Redis has reached its own memory limit (maxmemory) and its eviction policy can’t or won’t free space, so it refuses commands that would add data. Reads and deletes still work. Free memory, choose an eviction policy that fits your data, or raise the limit.
- MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to diskRedis’s last background save (BGSAVE) failed, and with stop-writes-on-bgsave-error on (the default) it refuses writes until a save succeeds. The log says why: usually a full disk, a directory Redis can’t write to, or fork() failing for lack of memory.
- MOVED 3999 127.0.0.1:6381 (and ASK) in Redis ClusterYou sent a command to a Redis Cluster node that doesn’t hold that key’s slot; the reply names the slot and the node that does. Cluster-aware clients (redis-cli -c, cluster clients in each library) follow it; a client connected to one node shows it as an error.
- CROSSSLOT Keys in request don't hash to the same slotIn Redis Cluster, a command, transaction or script that names several keys only runs if they all fall in the same hash slot, even when both slots are on one node. Put related keys in one slot with a hash tag such as {user:1}, or send one command per key.
- READONLY You can't write against a read only replicaThe server you sent the write to is a replica, and replicas refuse writes by default. Connect to the primary instead: check the endpoint you use, and reconnect after a failover, because the old primary becomes a replica and keeps your connection open.
Redis guides
- Connect to Amazon ElastiCache for Redis OSS or Valkey from your MacA node-based ElastiCache cluster has no public address, so reach it through an EC2 instance in the same VPC with an SSH tunnel to its primary or configuration endpoint on port 6379. Turn on TLS if the cluster has in-transit encryption, and sign in with its AUTH token or an RBAC user. Inlet works with cluster mode disabled, and with cluster mode enabled in Pro.
- Connect to Redis Cloud from your MacCopy the public endpoint (host and port) from the database’s Configuration tab and the default user’s password from its Security settings, then connect as the user default. TLS is off until you turn it on (paid plans only); after that, use rediss:// and Redis Cloud’s CA file.
- Connect to Redis in Docker or Homebrew on your MacStart Redis with docker run -p 127.0.0.1:6379:6379 redis:8 or brew services start redis, then connect to localhost on port 6379. Neither sets a password. The Docker image turns protected mode off so its published port works; Homebrew’s Redis listens on localhost only.
- Connect to Upstash Redis from your MacCopy the endpoint, port and token from your database in the Upstash Console and connect with TLS: rediss://default:<token>@<endpoint>:6379. The token is the password, and TLS can’t be turned off, so a plain redis:// connection fails.
- Connect to Valkey from your MacValkey is the Linux Foundation’s BSD-licensed fork of Redis 7.2.4 and speaks the same protocol, so you connect to it exactly as you would to Redis: port 6379, redis:// URLs, any Redis client. In Inlet, pick Redis.
- Redis connection stringsredis:// and rediss://, every part, with a checker.
Coming from another app?
What’s different, side by side, and how to bring your connections across.
- Inlet vs Redis InsightInlet and Redis Insight compared on a Mac: price, platforms, browsing keys, running commands, production safety, clusters and Sentinel, and switching over.
- Inlet vs TablePlusInlet and TablePlus side by side: price, platforms, engines, production safety and PostgreSQL tools, and how to import your TablePlus connections.
Not in Inlet yet
For Redis, so you know before you download.
- Sentinel, and reading from replicas.
- Managing ACL users.
- Nested namespaces in the sidebar.
Inlet for Redis
Free for personal use, with every safety feature. For work, Pro is $49 once, with a year of updates.
Version 0.1.0 · macOS 26 Tahoe or later · Apple silicon and IntelQuestions
Something else? Write to hello@inletdb.com.
Is Inlet free for Redis?
It’s free for personal use: personal projects, students and open source, with every engine and every safety feature. For work, Pro is $49 once, with a year of updates, and a new install has 14 days of Pro to try it.
Does it work with Valkey?
Yes. Valkey 8 is tested alongside Redis 8, including Valkey Cluster.
Does it work with Upstash, Redis Cloud and ElastiCache?
Yes. Paste the rediss:// URL they give you. ElastiCache with cluster mode on connects through Redis Cluster, in Pro. MemoryDB speaks the same protocol, but hasn’t been tried.
Will browsing keys slow my server down?
Inlet pages through keys with SCAN rather than KEYS, so the server keeps serving everyone else while you browse.