Product · Beta

Warden

With Warden, engineers reach servers, Kubernetes, databases and Windows desktops through their company login, with access that expires by itself and a record of everything they do. It replaces VPNs, shared SSH keys and static database passwords.

Who it is for

Platform and security teams that have outgrown shared keys and VPNs, and service providers that need access to many customer environments, each under the customer's control.

Works with

OpenID ConnectSAML 2.0Active DirectorySCIM 2.0KubernetesPostgreSQLOpenSSHS3-compatible storageSplunk and syslog

What it does

Access that expires by itself

After login, each session gets a short-lived certificate. There is nothing to rotate, and nothing left over when someone leaves.

One login for everything

Servers over SSH, Kubernetes, PostgreSQL, Windows desktops and internal web applications all sit behind the same company login. Warden works with OpenID Connect, SAML 2.0 and Active Directory, and SCIM adds and removes people automatically.

Access when it is needed

Roles can require MFA. People can ask for a role for a limited time, approved by someone else, and you can cut off a user or a machine immediately.

A record of who did what

SSH sessions are recorded and can be replayed, database queries are audited, and the log is tamper-evident: a command checks its integrity. Events can go to your SIEM.

No inbound ports

Agents next to your resources connect outward to Warden over mutual TLS, so protected networks do not need to open a single port.

What it looks like

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.
$ warden loginopening your identity provider…✓ signed in as [email protected]$ warden ssh acme/db-1✓ allowed by role dba✓ certificate issued for this session only✓ recorded and auditedada@db-1:~$ 

Sign in once. Each session gets a certificate of its own, and the session is recorded and audited.

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

How it works

  1. 01

    Sign in

    You log in with your company account. Warden issues a short-lived certificate and renews it in the background.

  2. 02

    Connect

    Each SSH, kubectl, database or desktop session asks for its own certificate. Roles, MFA and locks are checked at that moment, the request is logged, and an agent next to the resource routes and records the session.

  3. 03

    Review

    To find out who did what, verify the audit chain, replay the recording or look in your SIEM.

Shared SSH keys, VPNs and database passwords that nobody rotates make it hard to say who can reach what, and every departure turns into a checklist. Warden replaces them with your company login: each session gets a short-lived certificate for exactly what the person may reach, and when someone leaves, their access is gone.

Service providers can manage many customer clusters from one place, with each customer deciding what flows upward. Warden is self-hosted: one binary and one container image, installed with a Helm chart on Kubernetes or with Docker Compose on a plain VM, with apps for macOS and Windows.

We built Warden because we reach customers’ clusters, servers and databases every day. It runs on our own infrastructure today.

The full feature list, installation steps and answers to the questions people ask first are on the Warden website.

Warden is in beta

How do your engineers get in today?

Tell us how your engineers reach servers, clusters and databases today, and we will show you Warden next to that setup. Pricing and licensing are discussed with each company.

Book a 30-minute demo