Warden

Reach everything.
Keep no standing secrets.

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:~$ 

From a pile of keys to one door

Today
A key for every person and every server. Copied, shared, forgotten.
With Warden
Everyone signs in; every access is a certificate. Issued for that session, by one place.
Keys that never expireCopied the day they are made, rotated never.
Networks, not peopleA VPN says which network you are on, not who you are.
Offboarding by hopeAccess outlives the person, in files nobody lists.

Access that exists only while it is needed

  1. You sign in

    With the identity provider you already run: OIDC, SAML or your directory.

  2. Policy decides

    Roles match resources by label and a deny always wins. A role can also ask for a second factor or an approval.

  3. A certificate is minted

    Short-lived, bound to you and to that one resource. Nothing to copy, rotate or revoke.

  4. You are connected

    Through a tunnel the resource opened outward. Nothing on its side listens.

One way in, whatever you are connecting to

SSH

Servers with an agent, or plain OpenSSH hosts through a bastion that verifies the host certificate. No trust on first use.

Kubernetes

Any cluster, managed ones included. Exec sessions can be recorded.

Databases

PostgreSQL statements are logged before they run.

PostgreSQLMySQLSQL ServerOracle

Remote desktop

Windows machines through the RDP client you already have, with optional recording.

Web apps

Internal tools in the browser, behind your sign-in. No client, no VPN.

Machines and CI

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.

Access that is asked for, and ends by itself

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.

  1. A role, a reason, a time

    Anyone can ask for access they do not have.

  2. A colleague approves

    Never your own request. Reviewing can be limited to the right people.

  3. It applies at once

    With the certificate you already hold. No new sign-in.

  4. It ends by itself

    At the deadline, with nobody having to remember.

The same door serves

Engineers and on-call Contractors and auditors Pipelines and automation Providers and groups Incident response

An answer to “who did what”

Every decision is written to a log that proves it was not edited, and every session can be played back.

Verified
Altered at #3
Each event carries the hash of the one before. Change one and the check names where. It runs from cron and exits non-zero.
Sessions replay at the speed they happened, from a bucket you own. Forward the trail to your SIEM too.
SyslogWebhookSplunk HEC

Designed so there is little left to steal

Control plane
User CA Host CA Database CA Kubernetes CA Desktop CA Device CA
One authority per kind of certificate. The key that signs people’s certificates stays with the control plane. Proxies and agents get only what they need to check one.
A shared SSH keynever expires
A Warden certificateone session
Sign-ins renew quietly for a bounded time and cannot be stretched past a fixed age, however often they are repeated.
A second factor on your own machine A key held in hardware, the Secure Enclave on a Mac or Windows Hello on Windows, released by a fingerprint or a PIN.
Nothing allowed unless a role says so A deny always wins, and a role cannot grant a power its author lacks.
A kill switch that reaches everything Lock a user, a machine or a host and access stops on the next request, the management API included.
A way back in with no standing credential A recovery link minted on the server: single use, gone after twelve hours, written to the audit trail first.

One door across organisations

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.

  • Every level decides for itself which roles it grants. Trust is per hop, never inherited.
  • A child joins by consent and can be cut off on the very next request.
  • Built for managed service providers and for groups that keep their companies separate.
A provider cluster at the top, a customer cluster below it, a sub-organisation below that Providerlevel 0 Customerlevel 1 · its own policy Sub-organisationlevel 2 · its own policy sessions recorded at the node, audited at the top

It runs where your data already is

Your peopleapp or command line
Your identity providerOIDC · SAML · directory
sign in and connect
Your infrastructure
Control planeCAs and policy
Proxytunnels end here
PostgreSQLstate and audit
Recordingsyour bucket
agents dial out
Private network
Agentservers, databases
Another cluster
AgentKubernetes
Kubernetes or one VMA Helm chart, or a Docker Compose file. The same binary either way.
Your database, your bucketRecordings, state and certificate authorities stay in your infrastructure.
Offline licenceA problem with a licence never cuts off access someone already has.

Things people ask first

Do I have to install something on every server?

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.

Which identity providers does it work with?

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.

What does it need to run?

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.

What is recorded, exactly?

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.

Do people have to change how they work?

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.

What if our identity provider is down?

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.

Is it open source?

No. Warden is closed-source software from Magicorn, built to be run by you in your own infrastructure.

Get the client

The desktop app and the warden command line, for macOS, Windows and Linux.

macOS

Apple Silicon and Intel
App
brew install --cask magicorntech/warden/warden
Command line
brew install magicorntech/warden/warden-cli

Or download the .dmg from the latest release and drag Warden to Applications.

Windows

64-bit
App and command line, with Scoop
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.

Linux

x86-64 and ARM
Command line
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.