中文 | English

The Redis GUI that opens a million-key database without the spinner — native, GPU-accelerated, Rust 🦀 × GPUI ⚡️

Features · Install · Web version · Full feature tour · Website

Zedis is a native Redis and Valkey GUI. GPUI — the engine behind the Zed editor — draws every frame on the GPU, and SCAN is virtual-scrolled, so a million keys stay at 60+ FPS on a small memory footprint.

• 🧠 Reads your values — decompresses and decodes on its own: JSON, Protobuf, MessagePack, JWT, images and more, with a viewer for every Redis type and module.
• 📊 Observability in the same window — live metrics, a memory analyzer, hot keys, slow log, MONITOR and cluster health.
• 🔐 Safe on production — Prod connections start write-locked, a destructive command there asks for the server's name, secrets are encrypted per machine, and there is no telemetry.
• 🌐 Connects to what you actually run — TLS, SSH, Cluster, Sentinel; Redis and Valkey as first-class; Dragonfly, Garnet, proxies and managed clouds grey out what they lack, with the reason.
• ⌨️ For people who live in Redis — ⌘K, a redis-cli with completion, an AI command assistant, copy and diff across servers, and the same app in the browser.

Already on Redis Insight, ARDM or Tiny RDM? Paste the export and every connection lands at once.

📖 Every panel, viewer and shortcut →

brew install --cask zedis

scoop bucket add extras
scoop install zedis

Arch Linux (AUR):

yay -S zedis-bin

Other distributions: .deb, .rpm, an AppImage and a plain tarball (x86_64 and aarch64) are attached to every release.

# From crates.io — may be an older version
cargo install --locked zedis-gui

# Latest: build straight from GitHub (resolves the git dependencies)
cargo install --git https://github.com/vicanso/zedis --locked zedis-gui

Key browser & data viewer	Memory analyzer	Live metrics
Geo map	Vector Set + KNN	Command palette (⌘K)

The same GUI, compiled to WebAssembly. Host it next to Redis; the team opens a tab. zedis-bridge serves the page and talks to Redis — passwords stay on the bridge, encrypted at rest, and never reach the browser.

docker run -d --name zedis-web -p 7379:7379 \
  -e ZEDIS_BRIDGE_USERS="admin@change-me" \
  -v zedis-data:/data \
  vicanso/zedis-web:latest --listen 0.0.0.0:7379 --insecure-cookie

Open http://localhost:7379 as admin / change-me. That command is a plain-http trial: drop --insecure-cookie and put HTTPS in front.

• Accounts, roles, SSO — sign-in is required; an entry is private until it is shared; an account can be read-only or limited to some servers; identity can come from a reverse-proxy header.
• Production stays locked — Prod entries open for 15 minutes at a time; the audit log records logins, entry changes and every confirmed command.
• MCP — Claude Code, Cursor or any MCP client reads Redis as a read-only account, every call audited.

Early preview. linux/amd64 and linux/arm64 (~26 MB). A few desktop panels are missing in the browser; the guide lists them.

📖 Self-hosting: HTTPS, accounts, SSO, audit log, MCP →

Valkey is first-class, not a compatibility mode. Each version-gated feature has its own Redis floor and Valkey floor, so a server is never sent a command it did not ship. What only Valkey has — COMMANDLOG, atomic slot migration, multiple databases in cluster — has a panel. Copy works both ways even though DUMP payloads do not. CI runs Redis 6.2–8 and Valkey 8.0–9.1 on every change. Dragonfly and Garnet connect too: each is named in its own version, and the commands it does not have are probed and left out (Garnet, for one, has no streams). A smoke lane in CI keeps both connecting; neither is held to the full matrix.

📖 Compatibility matrix →

• Full feature tour — every panel, viewer and shortcut.
• Web version: self-hosting guide — deployment, accounts, SSO, the audit log and MCP.
• Redis and Valkey — what differs between the two, and how a copy between them works.
• Security policy · Changelog

macOS builds are signed and notarized with the maintainer's Apple Developer ID.

Team

• Committers and reviewers: @vicanso
• Approvers: @vicanso

Changes from outside the team arrive as pull requests and are reviewed by a committer before they are merged.

Privacy policy

This program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it, with two exceptions, both under your control:

• Update check. On startup, at most once every two days, Zedis downloads the release manifest from GitHub Releases to learn whether a newer version exists. If GitHub cannot be reached, the same request is retried against the Gitee mirror, which the release workflow copies every tagged release to — so the check, and any download you start, still work on networks where GitHub does not. Either way the request carries nothing but the app version in its User-Agent — nothing about you, your machine or your data — and a download is verified against the SHA-256 in the release manifest, so a mirror serving anything else fails the same check a corrupted transfer would. Turn it off with Settings → Check for Updates Automatically; a new version is only downloaded when you click Update.
• AI assistant. Only after you enter an endpoint under Settings → AI Base URL, the text you explicitly hand it — a command description, a memory report — is sent to that endpoint and nowhere else.

Your Redis servers, SSH tunnels and the optional proxy connect only where you point them. Zedis has no telemetry and sends no crash reports: they stay on disk until you export a diagnostics bundle yourself.

Issues and PRs are welcome — features, translations, bug fixes. Opening a PR means you agree to the Contributor License Agreement (CLA).

Zedis is open-source software licensed under the Apache License, Version 2.0.