SSH
Servers with an agent, or plain OpenSSH hosts through a bastion that verifies the host certificate. No trust on first use.
Warden replaces VPNs, bastions, shared SSH keys and static database credentials with short-lived certificates tied to who you are. Self-hosted, with the identity provider you already run.
$ warden loginopening your identity provider…✓ signed in as ada@example.com$ warden ssh acme/db-1✓ allowed by role dba✓ certificate issued for this session only✓ recorded and auditedada@db-1:~$ With the identity provider you already run: OIDC, SAML or your directory.
Roles match resources by label and a deny always wins. A role can also ask for a second factor or an approval.
Short-lived, bound to you and to that one resource. Nothing to copy, rotate or revoke.
Through a tunnel the resource opened outward. Nothing on its side listens.
Servers with an agent, or plain OpenSSH hosts through a bastion that verifies the host certificate. No trust on first use.
Any cluster, managed ones included. Exec sessions can be recorded.
PostgreSQL statements are logged before they run.
Windows machines through the RDP client you already have, with optional recording.
Internal tools in the browser, behind your sign-in. No client, no VPN.
A pipeline gets the same short-lived certificates a person does. With its CI provider’s own token it can hold no Warden credential at all.
Contractors, auditors and anyone on call for a night ask for a role with a reason. It applies at once and goes away on its own.
Anyone can ask for access they do not have.
Never your own request. Reviewing can be limited to the right people.
With the certificate you already hold. No new sign-in.
At the deadline, with nobody having to remember.
The same door serves
Every decision is written to a log that proves it was not edited, and every session can be played back.
Clusters join into a tree of up to three levels: a provider, its customers, and their own sub-organisations. An administrator at the top can reach a node deep below it, recorded where it happens and audited at the top.
Not for SSH: a bastion can relay to ordinary OpenSSH hosts that only trust Warden’s certificate authority, so the target runs no Warden software. For Kubernetes it is one agent per cluster, and a single database or web agent serves every database or app you register. Agents dial out, so no inbound firewall rule is needed.
Any that speak OIDC or SAML, and Active Directory directly. SCIM provisioning (Okta, Entra ID, JumpCloud and others) keeps joiners, movers and leavers in step without anyone touching Warden.
The control plane, a proxy that agents and clients connect to, and PostgreSQL for the state. On Kubernetes, with more than one replica, it also uses Redis or Valkey. The same binary runs either as a Helm chart or as a Docker Compose file on a single VM.
SSH sessions are recorded as what the terminal showed and replay at the speed they happened; typed input is not stored. Kubernetes exec and RDP recording are options you switch on. PostgreSQL statements are written to the audit trail before they run; the other database engines are relayed with access logged but no per-query view. Every access decision is in the hash-chained log.
They sign in with the desktop app or the command line, then use the tools they already have. SSH goes through warden ssh, kubectl uses a kubeconfig Warden keeps fresh, database clients connect to a local port, and RDP uses the remote desktop client you already have.
Signed-in people keep working: their certificates renew without the identity provider for a bounded time, up to seven days after the last real sign-in. To get an administrator back in, someone with access to the server mints a recovery link: single use, valid for twelve hours, and recorded in the audit trail.
No. Warden is closed-source software from Magicorn, built to be run by you in your own infrastructure.
The desktop app and the warden command line, for macOS, Windows and Linux.
brew install --cask magicorntech/warden/warden brew install magicorntech/warden/warden-cli Or download the .dmg from the latest release and drag Warden to Applications.
scoop bucket add magicorn https://github.com/magicorntech/homebrew-warden
scoop install warden Or download the .msi from the latest release (installs for your user, no administrator needed). The installers are not code-signed yet, so Windows may ask you to confirm the first run.
brew install magicorntech/warden/warden-cli Or a tarball from the latest release. There is no desktop app for Linux.
All downloads and release notes. The client talks to a Warden cluster that someone runs for you, or that you run yourself.