# P3X Redis UI: a Redis GUI that ships as a web app and a desktop app > A JavaScript Redis administration interface with a CodeMirror editor for JSON values, support for SSH, cluster and sentinel connections, 54 interface languages, and three GUI front ends in one package, published on npm, Docker Hub and as an Electron build. **patrikx3/redis-ui** — 📡 P3X Redis UI: A highly functional and convenient database GUI that fits in your pocket, accessible on both responsive web and desktop applications. - Repository: https://github.com/patrikx3/redis-ui - Website: https://www.corifeus.com/redis-ui - Stars: 808 · Forks: 76 - Language: JavaScript - License: MIT - Published: 2026-10-20 · Updated: 2026-10-20 · Language: en - Canonical page: https://hysenlabs.com/projects/patrikx3-redis-ui ## One package, three front ends, and a lot of languages P3X Redis UI is described as a Redis GUI that works as a web-based server application or as a standalone desktop app. The distinguishing claim in the description is that it excels at managing JSON data through an integrated CodeMirror editor with GitHub dark and light themes, supports uploading and downloading binary data, and handles SSH, cluster and sentinel configurations. The triple GUI point is worth pausing on, because it is unusual. The features summary lists Angular, React and Vue front ends, which means the package ships more than one client implementation rather than picking one framework. The internationalisation is the other standout. The interface language is switched in Settings, and the README lists 54 languages covering 88 or more countries, from Arabic through Chinese in three variants, Korean, Ukrainian, Swahili and Thai. The project also keeps a comparison document, COMPARISON.md under artifacts/readme, that it describes as an honest breakdown against redis-commander, RedisInsight and AnotherRedisDesktopManager, with a feature matrix, performance at one million keys, and guidance on when to pick each. The existence of that document is useful to know, since choosing among Redis GUIs is a decision people repeatedly have to make. The primary language is JavaScript and the licence is MIT, with the LICENSE file at the repository root. The homepage is corifeus.com/redis-ui. ## The Docker quick start is five commands and one port The shortest path to a running instance is the Docker one, and the README calls it a 30 second quick start: ```bash mkdir -p ./p3x-redis-ui-settings docker run -d \ --name p3x-redis-ui \ -p 7843:7843 \ -v $PWD/p3x-redis-ui-settings:/settings \ patrikx3/p3x-redis-ui ``` You then open `http://localhost:7843`. Two details carry the design. The port is 7843 everywhere: the container, the compose file, the health check and the CLI all agree on it. And the settings live in a mounted volume at `/settings`, which the Dockerfile sets as `P3XRS_DOCKER_HOME`, so your connections survive a container replacement. For Kubernetes and Docker the project is explicit about tag choice: always use the `latest` tag, `patrikx3/p3x-redis-ui:latest`, with `imagePullPolicy: Always`. Version specific tags exist but `latest` is the recommended and supported one. The compose file that ships in the repository is deliberately minimal. It defines one service, `registry`, from the same image, publishing `7843:7843`, mounting a settings volume, and carrying a health check that runs a small Node script which requests `http://localhost:7843/health` and exits non-zero unless the status is 200. The intervals are 30 seconds with a 10 second start period and 3 retries. The Dockerfile declares the same `HEALTHCHECK` instruction, so an orchestrator marks the container unhealthy on its own. ## The npm install gives you the same tool as a CLI If you would rather run it from Node, the install is a global npm package and the command is short: ```bash npm install -g p3x-redis-ui p3xrs ``` Again you open `http://localhost:7843`. The package name on npm is `p3x-redis-ui`, the binary in package.json is `p3x-redis`, and the CLI entry point the README uses is `p3xrs`. The CLI options list is where the security and behaviour controls live. `--readonly-connections` sets the connections to readonly, with no adding, saving or deleting a connection, which is the flag to use when the tool is reachable by people who should not be able to change your connection list. There is a pair of flags for HTTP Basic authentication: `--http-auth-enable` and `--http-auth-disable`, with the username and either a plain password, a bcrypt hash, or a file to read the hash from. `--groq-api-key` supplies the key used for AI powered Redis query translation, and `--groq-api-key-readonly` stops users from changing that key through the interface. `-c` points at the p3xr.json server configuration, and `-n` overrides the connections file name, which otherwise defaults to `.p3xrs-conns.json`. There is an important warning about the configuration file itself. The project notes say not to create the configuration JSON file by hand with a text editor, and to use the interface to generate it, since the resulting file can then be deployed to systems like Kubernetes. That is a small operational instruction but it changes the deployment workflow: the configuration is authored in the browser and exported, not hand written and mounted. ## What the interface actually covers in Redis The features summary points at a set of Redis capabilities that go past key browsing. The monitoring side is described as real time, with four named tools: Pulse, Profiler, PubSub and Analysis. Profiler is the one to know about if you are investigating latency, since it observes command execution rather than sampling from the outside. PubSub gives you a view of the channel traffic, which is useful when a producer is misbehaving. The module coverage is broad: RediSearch, RedisTimeSeries, ReJSON, RedisBloom, VectorSet, Array as in Redis 8.8, and Redis 8.x in general, plus ACL support. The Redis 8.x and Array entries are the ones to note, because they tell you the project tracks the newest server capabilities rather than stopping at the 7.x era. The JSON story is the one the description leads with, and it is a real differentiator. A CodeMirror editor with GitHub dark and light themes means you are editing a JSON value in a proper text editor with syntax highlighting, not staring at a JSON string blob in a textarea. Combined with binary upload and download support, that covers the two data shapes Redis users actually store. There is also an AI configuration document referenced separately, described as working out of the box and covering GUI and CLI configuration, readonly mode and the Groq API key. So the query translation feature is wired to a third party service, and the key handling for it is part of the CLI surface. ## A live demo exists, with its own caveats There is a hosted instance at p3x.redis.patrikx3.com, and the README is straightforward about what to expect from it. The data is reset daily, with certain datasets restored every morning in CET. There is occasional downtime of about one second, caused by automatic updates from Git changes. And the live instance may differ from the GitHub or npm release, because updates are typically published monthly. That last point matters for evaluation. The hosted demo is a moving target that tracks the repository rather than matching a published artefact, so what you see there is not necessarily what the current release contains. The local Docker quick start, which pulls the same image, is the closer approximation of a deployment you would actually run. There is a subtlety in how the demo and the releases relate that is worth stating plainly: the project publishes monthly, the repository is described as under active development, and the version numbers are date based, with the current package version being 2026.10.100. Recent tags follow that pattern, v2026.10.100, v2026.4.3014 and v2026.4.3013, so the year and month are visible in the version and the patch counter trails it. For anyone evaluating the tool, the practical implication is that you should test with a pinned image rather than assuming the live demo represents a stable release. ## Where P3X Redis UI is the wrong choice Three limits are worth naming. The first is that this is an editing tool, and a GUI that can modify keys, upload binary values and manage connections is a privileged position. The README offers `--readonly-connections` and HTTP Basic auth as mitigations, and there is a separate document covering that configuration, but the default posture is a full administration console. Pointing it at a production Redis and exposing it beyond a trusted network without reading that document first is how people cause incidents. The second is the surface area. An Electron desktop build, three web front ends, a server, a CLI, 54 languages, AI query translation through a third party API, and modules for RedisTimeSeries and RediSearch are a lot of moving parts for what some teams need, which is a way to look at a key and copy its value. The project's own comparison document, with its feature matrix and a performance note at one million keys, is the right place to work out whether you need all of that. The third is that the project is explicit about its own state. The banner says this project is under active development, and the version numbers plus the recommendation to use the latest tag say the same thing. That is fine for a tool you run on your own machine against a development Redis. It is a different proposition for something your team depends on for production inspection, where you would want a versioned artefact and a changelog you can read, and the repository does carry a long series of changelog files per year, from change-log.2018.md through change-log.2025.md, plus a current change-log.md, which helps. The alternative to name is a purpose built client for your stack. If you run Redis with RedisInsight already sanctioned by your organisation, or you work primarily through a CLI on a bastion host, the editing power here is surplus to requirements. The difference in approach is that this is a general purpose administration GUI with a wide module surface, where the smaller tools are narrower and easier to reason about for audit purposes. ## Conclusion Adopt P3X Redis UI if you need a Redis GUI that handles the things a simple browser client does not, in particular editing JSON values with a real editor, reaching instances over SSH, and working with cluster and sentinel setups, and if you want one package that serves as a web app or a desktop app. Do not adopt it if you want a read-only tool, since the CLI has a readonly connections flag but the interface is designed for editing, or if you want a stable release stream, because the project states it is under active development and recommends the latest tag. Verify first which Node version your environment has, since the minimum is v22.0.0 and the build targets v24.20.0, and read the comparison document in artifacts/readme before you settle on it against other tools. ## FAQ ### How do I run P3X Redis UI with Docker? Create a settings directory, then run the container with port 7843 published and the settings directory mounted at /settings, then open http://localhost:7843. The image also declares a built-in HEALTHCHECK that polls /health every 30 seconds. ### Which Node.js version does P3X Redis UI need? The minimum Node.js version is v22.0.0, and the project is built on v24.20.0 with NodeJS LTS support. ### Can P3X Redis UI be installed from npm? Yes. Run `npm install -g p3x-redis-ui` and then `p3xrs`, then open http://localhost:7843. The CLI options include readonly connections, HTTP Basic auth with a username and either a plain password, a bcrypt hash or a hash file, and the Groq API key. ### What does the P3X Redis UI interface support for non-English users? The language is switched in Settings, and the README lists 54 languages covering 88 or more countries, including Arabic, Chinese in three variants, Korean, Ukrainian, Turkish and Swahili. ### Is there a hosted demo of P3X Redis UI? There is a live demo at p3x.redis.patrikx3.com, and the README notes three caveats: datasets are reset every morning CET, occasional interruptions of about a second occur during automatic updates, and the live instance may differ from the GitHub or npm release since updates are typically published monthly. ## Sources - [License: MIT](https://github.com/patrikx3/redis-ui/blob/main/LICENSE) - [patrikx3/redis-ui on GitHub](https://github.com/patrikx3/redis-ui) - [Project website](https://www.corifeus.com/redis-ui) - [README](https://github.com/patrikx3/redis-ui/blob/main/README.md) - [Releases](https://github.com/patrikx3/redis-ui/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/patrikx3-redis-ui