Get early access
Features · Security & Backup · SSH Session Recording
Security & Backup · SSH Session Recording

Every gated session,
replayable as an asciicast.

When SSH goes through Gatekeeper, each session is optionally captured as an asciinema cast. Search by user, by host, by date. Replay at any speed. Export for evidence. Without slowing the session down.

recorded sessions
sascha → db-prod-01 14:31 · 8m12s
sascha → web-prod-04 11:02 · 2m41s
ci-bot → build-03 09:14 · 42s
format asciinema cast, replayable
retention per policy, exportable
— Why this matters

The question after an incident is always "what exactly did they type?"

01

A login record is not a session record.

Knowing that someone connected at 14:31 tells you nothing about what they did in the twelve minutes that followed.

02

Recording must never lock anyone out.

If the recorder fails to install, the session still happens. Fail-open is the only defensible default — an audit gap beats an outage.

03

Replay beats a transcript.

A cast plays back at the original timing, so you see the pauses, the typo, the moment they realised. A flat log loses all of it.

— What's included

How a session gets captured.

Baked into the certificate
Recording is a force-command in the Gatekeeper cert itself, not something the user can opt out of at the prompt.
Interactive shells
Captured as asciinema casts and replayed in the browser at original speed.
Non-interactive commands
Logged with their stdout and stderr, shown as plain terminal text — no player needed for a one-line command.
Installed by the agent
The wrapper and asciinema are installed for you, via apt, dnf or yum as the host requires.
Per-server toggle
Recording is on or off per host, so you are not capturing your own laptop's test box.
Retention you choose
90 days by default, up to ten years. A daily job prunes what has expired from both database and disk.
Encrypted at rest
Stored through the platform's storage layer — local disk, S3 or Hetzner S3.
Filterable list
By server, by user, by date range, so finding the session you mean does not mean scrolling.
— How it works

In the certificate, not in a wrapper.

1

Baked into the certificate

Recording is an attribute of the issued certificate, so it cannot be skipped by connecting differently.

2

Recorded on the host

Interactive shells and non-interactive commands alike, by a component the agent installs.

3

Encrypted, and expiring

Stored encrypted at rest with the retention you set, and switchable per server for hosts where it is not appropriate.

— Works with

Connected capabilities

SSH Gatekeeper
The JIT access layer recording attaches to.
→
Audit Log
Where session metadata is recorded alongside everything else.
→
Audit Log Signing
HMAC chain that makes recording exports tamper-evident.
→
Policy Engine
Enforce "recording required for prod hosts" as a policy.
→
— FAQ

Questions, answered honestly.

Does it slow down the session? +
Negligibly — asciicast is text-only output capture, not a wire-level tap. Imperceptible to humans.
What about SCP / SFTP / port-forwards? +
File transfer metadata (which file, how big) is logged. Port-forward sessions log the open / close, not the bytes that flow.
Can I opt out per user / per host? +
Yes — Policy Engine controls this. Default on Enterprise is "required for prod, optional elsewhere".

Recorded access without the friction.

SSH Session Recording on Enterprise plans.

Get early access Back to Security & Backup