# Another Redis Desktop Manager: three installers and two platform traps

> Another Redis Desktop Manager is an MIT licensed Redis GUI client for Linux, Windows and Mac that ships an exe, an AppImage and a dmg instead of one installer. It covers cluster, sentinel, ACL, SSH tunnel and module type views, and two of its routes need a system command before the app will connect or open.

**qishibo/AnotherRedisDesktopManager** — 🚀🚀🚀A faster, better and more stable Redis desktop manager [GUI client], compatible with Linux, Windows, Mac.

- Repository: https://github.com/qishibo/AnotherRedisDesktopManager
- Stars: 34,796 · Forks: 2,712
- Language: JavaScript
- License: MIT
- Published: 2026-08-17 · Updated: 2026-08-18 · Language: en
- Canonical page: https://hysenlabs.com/projects/qishibo-anotherredisdesktopmanager

## Windows gets an exe, Linux gets an AppImage, Mac gets a dmg

There is no single install command, because the project ships three artifact types and splits its instructions by platform. On Windows the primary route is the latest exe from the releases page, or the gitee mirror for users in China, double clicked to install. Two package managers wrap the same thing:

```bash
choco install another-redis-desktop-manager
```

```bash
winget install qishibo.AnotherRedisDesktopManager
```

Linux takes the AppImage and has no install step at all: download it, mark it executable, double click to run. Snap is the packaged route.

```bash
sudo snap install another-redis-desktop-manager
```

macOS uses the dmg, or Homebrew.

```bash
brew install --cask another-redis-desktop-manager
```

Whichever route you take, the first real use is a connection. This client stores profiles rather than a single server: Single Connection Support landed on 2019-02-22 and Connection Group Support on 2026-07-29, so a first session means creating a profile for the host, choosing a connection type, and proving it works. Test Connection Support arrived on 2026-08-15, which is the fastest way to find out whether the address, port and credentials are right before you start walking keys.

## The Windows checkout installs win32 dependencies on 64-bit machines

Contributors do not build from the release artifacts. The client is an Electron app, and the Windows dependency install carries an explicit platform flag that the Linux and macOS instructions leave out. The README states the reason in one line.

```bash
# install dependencies, 32-bit or 64-bit all use win32
npm install --platform=win32
```

Linux and macOS run a plain npm install, with no platform argument. The asymmetry propagates into the packaging scripts, where pack:win and pack:win32 are separate entries, pack:mac and pack:mas produce the App Store build with CSC_IDENTITY_AUTO_DISCOVERY=false, and pack:macm1:publish adds --arm64 and names its own artifact ${productName} M1 ${arch} ${version}.${ext}. Apple Silicon output is therefore a deliberate extra invocation rather than something the standard mac build produces, and pack:prepare is the step that copies the pack/electron contents into dist before any of them runs.

## The snap build cannot read your private key until you connect the interface

Snap confines the app, and SSH is where confinement shows. The failure is named directly: permission denied when selecting a private key. The fix is an interface connection that grants the package access to your ssh folder.

```bash
sudo snap connect another-redis-desktop-manager:ssh-keys
```

This is not an edge case for this client. SSH work accumulated steadily: tunnel connections on 2019-04-09, private key support on 2020-02-16, SSH cluster support on 2020-09-04, and passphrase and timeout handling on 2020-11-03. A database reachable only through a bastion host, or a key file with a passphrase, needs the packaged app to read a file the user owns, and confinement blocks exactly that. Until the interface is connected, the connection form will let you pick the key and then fail to use it, and the message blames permissions rather than the tunnel, so the real cause is easy to misread. The AppImage route has no equivalent step, which is the practical difference between the two Linux options beyond packaging format.

## Gatekeeper leaves the app closed until you strip the quarantine attribute

Both macOS routes can end with an application that will not open, and the remedy sits above the download instructions rather than below them. If the app will not start after installing by brew or dmg, run this and reopen it.

```bash
sudo xattr -rd com.apple.quarantine /Applications/Another\ Redis\ Desktop\ Manager.app
```

Two details are worth reading before you paste it. It is a recursive delete of one attribute, and it needs sudo because the flag lives on a bundle inside /Applications. It is also path specific: if the app sits somewhere other than /Applications/Another Redis Desktop Manager.app, the command clears nothing while you believe the problem is solved. The cost is a deliberate loosening of the gate macOS applies to downloaded applications, scoped by you to this one bundle, with the judgement about the rest left open. Two other routes to the same client exist through the Mac app store and the Windows store, which the project asks readers to buy as a form of sponsorship and states are not free.

## Load All Keys ships with no measurement behind the claim

Support To Load All Keys arrived on 2022-01-05, joined earlier by Big Key Loads With Scan on 2020-04-28. The pitch in the README is blunt about the reason to pick this client: it will not crash when loading massive keys. Nothing in the repository backs that with a key count, a dataset, a memory figure or a timing, so a reader with a large keyspace cannot size the risk from the project's own pages. Two related features shape what to do instead. Readonly Mode, added 2022-03-03 alongside Monitor Support, lets you browse an instance without issuing writes, which is the setting to use on production. The safer path on a big dataset is readonly mode plus search rather than the full load, and search is well covered here: Hash List Set Zset on 2019-05-09, List on 2023-04-01, Stream on 2023-05-26, connections themselves on 2024-06-06, and Search History on 2021-02-28. Point the full load at a copy, not at the instance your service depends on.

## Views arrive with the server release that introduced them

Type coverage tracks Redis history, and the dates in the log tell you the floor for each view. Hash field TTL support is marked Redis>=7.4 and landed on 2024-10-07, so that view needs a recent server. TimeSeries, Vector and ARRAY support with Test Connection Support came on 2026-08-15, two days before the v1.7.4 release on 2026-08-18. Older entries show the encoding and module work a Redis client accumulates: RedisJSON with Brotli, Gzip and Deflate on 2022-01-01, Protobuf and memory analysis on 2022-04-01, Java and Pickle viewers on 2024-02-21, Msgpack on 2021-02-03, Binary View on 2020-11-03. Server plumbing has its own line: SSL/TLS on 2020-06-18, Cluster on 2020-04-04, Sentinel on 2021-06-30, ACL on 2021-06-24, Slow log on 2023-05-26. The consequence is an older server, or one without the modules loaded, leaving views that render nothing, and the log is the only place that names the version a view needs.

## Two processes, localhost:9988, then a fontconfig fix on Linux

A source checkout does not produce a window on its own. The Linux and macOS sequence starts from a shallow clone, runs the dev server with hot reload on port 9988, and then needs a second process for the desktop client.

```bash
# clone code
git clone https://github.com/qishibo/AnotherRedisDesktopManager.git --depth=1
cd AnotherRedisDesktopManager

# install dependencies
npm install

# if download electron failed during installing, use this command
# ELECTRON_MIRROR="https://npmmirror.com/mirrors/electron/" npm install

# serve with hot reload at localhost:9988
npm start

# after the previous step is completed to 100%, open another tab, build up a desktop client
npm run electron
```

Expect the first install to fail on some Linux machines, and the error names the missing header.

```bash
# if error like this
../src/FontManagerLinux.cc:1:35: fatal error: fontconfig/fontconfig.h: No such file or directory

# then try this
sudo apt install libfontconfig1-dev
```

Two things to know before you script around this. package.json marks the project private, so the application is not on npm, and its version field reads 1.1.1 while the published tags reached v1.7.4, so the manifest is not a version source. The last three releases also sit far apart, v1.7.1 on 2024-12-28 and v1.7.2 on 2026-07-29, and the feature log has a 2025-10-01 line that promises features without naming one. getopts ^2.3.0 is in dependencies and Command line(CLI) args support arrived on 2024-01-31, but no page documents which flags the client accepts, so scripting it means reading src.

## Conclusion

Take Another Redis Desktop Manager if you need one client for cluster, sentinel, ACL, SSL/TLS and SSH tunnel connections across all three desktop platforms and you want module aware viewers for RedisJSON, Protobuf and TimeSeries. Skip the snap build if you cannot connect the ssh-keys interface, and skip the paid store routes if sponsorship is not something you want to buy. Verify before you point it at anything important: your server version against the feature log, since hash field TTL needs Redis 7.4 or newer, and the app against a copy of your keyspace, because the claim that it will not crash when loading massive keys carries no published measurement. The newest release is v1.7.4 from 2026-08-18 and the last push was on 2026-08-20.

## FAQ

### what is another redis desktop manager

A cross platform Redis desktop manager, a GUI client for Linux, Windows and Mac released under the MIT license. Its feature log covers cluster, sentinel, ACL, SSL/TLS, SSH tunnel and module type views including RedisJSON, Protobuf, Msgpack and TimeSeries.

### how to install another redis desktop manager

Use the route for your platform. Windows takes the release exe, `choco install another-redis-desktop-manager` or `winget install qishibo.AnotherRedisDesktopManager`. Linux takes the AppImage marked executable or `sudo snap install another-redis-desktop-manager`. Mac takes the dmg or `brew install --cask another-redis-desktop-manager`.

### how to use another redis desktop manager

Create a connection profile for the server first, then browse keys in the views the client supports. Test Connection Support arrived on 2026-08-15 for checking a profile, Readonly Mode on 2022-03-03 for browsing without writes, and Support To Load All Keys on 2022-01-05 for pulling a keyspace into the client.

### another redis desktop manager alternative

The repository names no alternative and no comparison. The project pitches itself on not crashing when loading massive keys, and the code is MIT licensed with free downloads on the releases page, while the Mac app store and Windows store copies are paid routes the author describes as sponsorship.

## Sources

- [Official README](https://github.com/qishibo/AnotherRedisDesktopManager#readme)
- [Project repository](https://github.com/qishibo/AnotherRedisDesktopManager)
- [Release notes](https://github.com/qishibo/AnotherRedisDesktopManager/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/qishibo-anotherredisdesktopmanager