Overview
Keyreeve puts one audited gateway in front of the Linux hosts and Kubernetes clusters you already run. People sign in with your identity provider, Keyreeve issues a short-lived SSH certificate instead of handing out keys, decides what each person may do on each host, and records what happens.
The pieces
| Piece | What it does | Where it runs |
|---|---|---|
| Server | Certificate authorities, access rules, the web interface, session relay, Kubernetes access decisions and the recording index | One container in your environment, or several as a cluster (Enterprise) |
Host agent (keyreeved) | Enrols the host, manages Keyreeve's sshd settings, decides each login from the rules the server sends it, records sessions | Each managed Linux host |
Cluster agent (keyreeve-kube) | Keeps the RBAC bindings Keyreeve manages and carries Keyreeve's requests into the cluster, acting as the person | Inside each Kubernetes cluster |
CLI (keyreeve) | Signs in, loads a certificate into ssh-agent, reaches hosts through the gateway, signs kubectl in (keyreeve kube login) | Each person's workstation |
| Desktop app | Tabs on hosts and Kubernetes pods, file transfer, port forwards, several accounts and servers, login scripts, AI assistance, your own SSH connections in a vault | Each person's workstation |
How a session happens
- A person signs in with your identity provider. Keyreeve resolves their groups to a role.
- Keyreeve's user CA issues them a certificate that expires after a few hours (8 by default), not a key that lives on their laptop.
- They connect — from the desktop app, the browser, or their own
ssh. - The host's agent decides whether this person may log in, as this account, from the access rules the server has sent it. The decision is made on the host, so it doesn't depend on reaching the server at that moment.
- The session is recorded on the host, redacted, and streamed to your storage.
Agents dial out to the server, so no host needs an inbound port opened for Keyreeve. People who connect through the desktop app, the browser or the gateway don't need to reach the host either; plain ssh to a host needs the host's sshd to be reachable from the workstation.
Where to go next
- Install the server
- Enrol hosts
- Decide who may reach what
- Connect
- Break-glass access, for when Keyreeve can't be reached

