Abdohoo.App Developer tools RedisDesk

For Redis, Valkey, KeyDB and compatible servers

Every key type, and never KEYS *.

Browse and edit keys of every type, type commands with completion and a linter that knows which ones hurt, watch the server live, subscribe to channels, manage users, analyse how a keyspace is spent, and move data with exact backups — all from one window.

7compatible servers
3desktop platforms
14 daysfull trial
0telemetry sent

No newsletter, no sharing — one email when it ships.

RedisDeskKey browser Coming soon
keys Smoke Redis 8 5 modulestrial 14d
cache300
config1
events1
session1
user3
hash user:14
hash user:24
hash user:33
 str counter1
 zset leaderboard5
connected · 127.0.0.1:6379 315 keys · RESP3 · db0

What it does

A client that refuses to be the outage.

Every item here is in the product today. The server is identified on connect — flavour, version, modules — and features that need a newer server simply stay hidden on an older one.

Connections

Standalone, Sentinel, Cluster

  • Master discovered by name for Sentinel; slots discovered from seed nodes for Cluster
  • Plain, TLS and mutual-TLS; SSH bastion tunnelling for every host
  • requirepass and ACL user authentication, with a separate Sentinel password
  • RESP3 by default with automatic fallback to RESP2 for older servers, KeyDB and proxies
  • Paste a redis://, rediss:// or valkey:// URL and the fields fill themselves
Keys

A tree that scans, never sweeps

  • SCAN-based tree folded on a delimiter you choose, with type chips, TTLs, sizes and big-key flags
  • An editor per core type: strings, hashes with per-field TTL, lists, sets, sorted sets, streams with consumer groups
  • Module types too: JSON with JSONPath, time series with a chart, Bloom and cuckoo filters, Top-K, t-digest, vector sets
  • Key metadata: encoding, memory, idle time, LFU frequency, cluster slot
  • Folder actions — delete or set a TTL on every key under a prefix — run as a tracked job
Workbench

Completion, and a linter with taste

  • A command catalogue through Redis 8 and Valkey 9, with hover documentation
  • Run one by one, pipelined, or as a MULTI/EXEC transaction; on every cluster master at once
  • Linting for KEYS, FLUSHALL, SMEMBERS on big sets, unbounded ranges, arity mistakes and writes on a read-only connection
  • Replies as redis-cli text, a table, a folded RESP tree or JSON; export to text, JSON, NDJSON, CSV or Markdown
  • Command history with redacted secrets, and saved snippets
Server

Live, and the doctors

  • Memory with policy, persistence state, databases and modules at a glance
  • Charts from INFO: throughput, memory, clients, hits and misses, expirations and evictions, summed across cluster masters
  • Slow log, latency events, the memory and latency doctors, command and error statistics
  • Configuration browser with in-place CONFIG SET and CONFIG REWRITE
  • Replication, cluster slot map, Sentinel masters and failover
Analysis

Where the memory went, and who may touch it

  • SCAN the keyspace and see it by namespace, type and TTL, as a cancellable job
  • Biggest keys by MEMORY USAGE and the longest collections
  • ACL users with their command, key and channel rules; ACL DRYRUN a command as any user
  • The refusal log, the category reference, and save or load of the ACL file
  • Subscribe to channels, patterns and shard channels; MONITOR with an honest note on what it costs
Movement

Exact backups, and the advisor

  • Backups that DUMP every key with its TTL into gzipped NDJSON plus a manifest
  • Restore with database remapping, prefixes, replace and dry run
  • Export to NDJSON, JSON, CSV, redis-cli command lines or RESP for redis-cli --pipe
  • Copy keys between two open connections
  • An advisor on memory limits, eviction, persistence, replication lag, open default users and end-of-life versions — with the command that fixes each

Trial and licence

Fourteen days, then reading still works.

RedisDesk runs fully featured for fourteen days from first launch. After that it keeps reading — browsing, queries, metrics, analysis and export — and only writing needs a licence key.

Someone diagnosing a production incident is never locked out of looking at their own data by a lapsed key. That is a deliberate choice, not an oversight.

A key is an Ed25519-signed statement verified locally against a public key compiled into the binary. Nothing contacts a server, which matters because database tooling is routinely run on machines with no route to the internet. Perpetual keys carry a maintenance window, so a key keeps working forever on the versions it covers.

StateReadWrite
Trial — 14 days from first launchyesyes
Licensedyesyes
Trial endedyesno
Licence expiredyesno
Key does not cover this versionyesno

Pricing is not set yet — ask and we will tell you the moment it is.

Local

Credentials never leave the machine

Connection secrets go to the OS keychain — Keychain on macOS, Credential Manager on Windows, Secret Service on Linux — not to a config file in your home directory. Passwords go straight to the server: never logged, never echoed back, and masked in every statement preview.

Quiet

No telemetry, no account, no check-in

There is no analytics call, no crash reporter phoning home and no sign-in. The app works the same on an air-gapped jump box as it does on your laptop, and the licence check is part of why — it is arithmetic, not a request.

Careful

It shows you the statement first

Destructive actions take typed confirmation, and every write shows the exact command before it runs. A connection can be marked read-only, and that switch is enforced in the main process at the same place the licence gate lives — so a caller that respects one cannot slip past the other.

Honest

It hides what your server cannot do

Dragonfly, Garnet, Redict and Kvrocks speak the protocol but not the same feature set. ACL needs Redis 6, functions and sharded pub/sub need Redis 7, hash field expiry needs Redis 7.4 or Valkey 9, vector sets need Redis 8 — each simply stays hidden where it is not supported.

Coming soonv0.1.0

Want it when it lands?

Needs a reachable Redis 5+, Valkey, KeyDB or compatible server on its port — 6379 by default, Sentinels usually on 26379. Standalone, Sentinel and Cluster deployments are all supported.

No newsletter, no sharing — one email when it ships.

Windows · macOS · Linux

The other two

Coming soon

ScyllaDesk

ScyllaDB and Apache Cassandra