Valkey Admin
Browse keys, run commands, and monitor your cache from a web UI — at no extra cost.
What is Valkey Admin?
Valkey Admin is an optional web interface for a Valkey cache instance, based on the open-source valkey-admin project. It provides:
- Dashboard — memory, CPU, connected clients, hit ratio, and throughput
- Cluster topology — a view of your instance's shards
- Key browser — browse, search, and edit all data types
- Command console — send commands directly to your cache
- Hot keys — identify the most frequently accessed keys
- Command logs — slow commands and large requests or replies
Valkey Admin is included at no extra cost and is never metered.
Enabling Valkey Admin
Enable Valkey Admin from the cache instance form, in the Valkey Admin section. This section is available both when creating a new cache instance and when editing an existing one.
- Go to your cache instance, or start creating one
- Open Edit (or continue through cache creation)
- Toggle Valkey Admin on
- Optionally set Allowed CIDR Blocks to restrict which client IPs can reach the interface
- Save
Leave this field empty to allow any address to reach the login page. Logging in with the Valkey Admin username and password is always required, regardless of this setting.
Valkey Admin is unavailable on installations without a shared gateway. If your installation doesn't have one, the toggle is disabled.
Accessing Valkey Admin
Once enabled and started, the cache instance detail page shows a Valkey Admin card with:
- The HTTPS link to the admin interface, served on the platform's shared gateway domain — the hostname includes a random suffix (e.g.
cache-admin-k3x9q2ab.gw.sailops.dev), so always open it from the card rather than guessing it - The username and password — reveal and copy actions are available to accounts with the Developer role or above
- A Regenerate action
While the admin interface is starting, the card indicates that it is starting — wait for it to become ready before opening the link.
Opening the link prompts your browser for the Valkey Admin username and password (HTTP basic authentication). This login protects the admin interface itself.
Connecting to your instance
Valkey Admin opens your cache connection automatically when the interface loads, including when your cache has no password. The Valkey password stays on the server and is never sent to or stored by your browser. The topology view, key browser, command console, hot keys, and command logs are available as soon as the connection completes.
Regenerating credentials
Click Regenerate on the Valkey Admin card to replace the Valkey Admin username and password. This does not change your Valkey password — only the credentials used to log in to the admin interface change. Regenerating restarts Valkey Admin, so sessions that are already logged in are closed and must log in again with the new username and password.
Lifecycle
- Valkey Admin stops while the project is suspended, and restarts automatically on resume.
- Changing your Valkey password restarts Valkey Admin automatically. It reconnects with the new password when you reopen or refresh the interface.
Security
Anyone with the Valkey Admin username and password has full read and write access to your cache data — treat these credentials with the same care as your Valkey password.
- Use Allowed CIDR Blocks to restrict access to known client IP ranges
- Regenerate the credentials if you suspect they were exposed