Keydra documentation
Keydra is a web console for key-value servers: browse keys, run commands, watch a fleet, and let more than one person do it under permissions you decide.
Keydra is a multi-user, deployable web console for key-value servers — Redis, Valkey and the compatible forks, Aerospike and TiKV. It runs on your own infrastructure, holds the credentials for your targets, and gives a team one place to browse a keyspace, run commands, watch what a server is doing, move keys between environments, take backups, and be told when something is wrong.
Everything in this documentation is derived from the Keydra source tree. Where a procedure names a button, that is the label the interface shows.
All sections
Introduction
A web console for key-value servers that a team shares, with credentials held on the server and access decided per person and per target.Installation
Bring Keydra up against the local Redis and Valkey the repository ships, create the first administrator, and sign in.Targets
A connection profile is how Keydra reaches one target. Add one, test it, edit it without re-entering its password, and switch between its databases.Keys and data
Keys stream in as the server scans them, grouped into a namespace tree and filtered by glob and type. Never KEYS, always a cursor.Operating
A command line against one target, with a deny-list in two halves: one this application will never allow, and one a target may take names out of.Automation
Keydra reads from one target and writes to the other a batch at a time, so the two servers never have to reach each other and the keyspace is walked rather than held.Security
Keydra holds the credentials to every server it manages. What that means for encryption at rest, sessions, outbound requests and the key that protects everything else.Running Keydra
What a deployment must set, what to set before exposing Keydra, and the shared store that turns one instance into several.Reference
A REST surface under /api/v1 and a GraphQL one beside it, both calling the same services under the same permissions, plus the sockets and streams.