---
title: "Zero Trust, Passwordless SSH at Any Scale - Octelium"
description: "A free and open source, self-hosted platform for secretless SSH access. No keys to distribute, no PKI to operate, with per-request policy and session recording."
canonical: "https://octelium.com/solutions/zero-trust-ssh"
---

Zero trust SSH

# Passwordless, keyless SSH at any scale

Octelium is a free and open source, self-hosted zero trust access platform. Its SSH mode authenticates to the upstream server on the User's behalf, so nobody receives a password or a private key, there is no SSH certificate authority to operate, and every session is authorized per connection and recorded.

[Install in minutes](https://octelium.com/docs/octelium/latest/overview/quick-install.md)[Live Demo](https://demo.octelium.com)[GitHub repo](https://github.com/octelium/octelium)

- Free and open source
- No keys to distribute
- No PKI to operate

The platform

## A unified secure access platform

SSH is one mode of the same platform. Each capability is described in detail below, in the same order.

1. [Unified access platform](https://octelium.com/docs/octelium/latest/overview/how-octelium-works.md)

   [One architecture for client-based zero-config VPN-like access over WireGuard and QUIC tunnels and clientless access over browsers for humans and OAuth2 access for workloads.](https://octelium.com/docs/octelium/latest/overview/how-octelium-works.md)

   [Read more](https://octelium.com/docs/octelium/latest/overview/how-octelium-works.md)
2. [L7-aware access control](https://octelium.com/docs/octelium/latest/management/core/policy.md)

   [Identity-based, application-layer aware ABAC access control with policy-as-code via CEL and OPA, applied on a per-request basis.](https://octelium.com/docs/octelium/latest/management/core/policy.md)

   [Read more](https://octelium.com/docs/octelium/latest/management/core/policy.md)
3. [Secretless access](https://octelium.com/docs/octelium/latest/management/core/service/secretless.md)

   [Dynamic secretless access where teams and AI agents access protected infrastructure without ever holding a credential.](https://octelium.com/docs/octelium/latest/management/core/service/secretless.md)

   [Read more](https://octelium.com/docs/octelium/latest/management/core/service/secretless.md)
4. [Unified identity management](https://octelium.com/docs/octelium/latest/management/core/user.md)

   [Teams, workloads and AI agents share the same model for identity management, access control, and auditing.](https://octelium.com/docs/octelium/latest/management/core/user.md)

   [Read more](https://octelium.com/docs/octelium/latest/management/core/user.md)
5. [Real-time visibility and auditing](https://octelium.com/docs/octelium/latest/management/core/visibility.md)

   [OpenTelemetry-native, real-time, application-layer-aware visibility and structured logging.](https://octelium.com/docs/octelium/latest/management/core/visibility.md)

   [Read more](https://octelium.com/docs/octelium/latest/management/core/visibility.md)
6. [GitOps-friendly management](https://octelium.com/docs/octelium/latest/management/core/service/managed-containers.md)

   [Octelium is administered like Kubernetes. Define your resources in YAML files, store them in a Git repository.](https://octelium.com/docs/octelium/latest/management/core/service/managed-containers.md)

   [Read more](https://octelium.com/docs/octelium/latest/management/core/service/managed-containers.md)

Client-based and clientless

## One architecture for every host you reach

Each SSH server is represented by a Service, which is served by an identity-aware proxy that abstracts away the network details of the upstream behind it. People keep using their ordinary SSH client.

- [The Service is reached over a client-based WireGuard or QUIC tunnel at a stable private name, so a host's actual address, network and environment stop being things anyone has to know.](https://octelium.com/docs/octelium/latest/user/cli/access.md)
- [An upstream can also be an address that is only reachable from the side of a connected host, which covers workstations, private clouds and equipment behind NAT with no inbound port.](https://octelium.com/docs/octelium/latest/management/core/service/overview.md)
- [The embedded SSH mode serves SSH from inside the octelium client itself, without a standalone SSH server on the host and without root privileges, which suits fleets of containers and IoT devices.](https://octelium.com/docs/octelium/latest/management/core/service/embedded-ssh.md)

[Read about accessing SSH Services](https://octelium.com/docs/octelium/latest/user/cli/access.md)

Access control

## Layer-7 aware access control with policy-as-code

Access is authorized using CEL or Open Policy Agent, against the identity behind the connection and the SSH request itself rather than the network path it arrived on.

- [The SSH user requested by the client is part of the request context, and combines with identity, group membership, device posture, session type and time in the same expression.](https://octelium.com/docs/octelium/latest/management/core/policy.md)
- [Subsystem requests such as SFTP and local port forwarding are disabled by default and enabled explicitly per Service, so file transfer and tunnelling are separate decisions from shell access.](https://octelium.com/docs/octelium/latest/management/core/service/ssh.md)
- [Zero standing privileges. No permanent admins or superuser Users. All access is explicitly allowed by a Policy that can be tied by time and context.](https://octelium.com/docs/octelium/latest/overview/zero-trust.md)

[Read about access control and Policies](https://octelium.com/docs/octelium/latest/management/core/policy.md)

Secretless access

## Keys and passwords that are never distributed

The upstream password or private key is stored in the Cluster as a Secret and used by the proxy to authenticate to the SSH server once a connection has been authorized. Nobody receives it, so there is nothing to rotate across laptops when someone leaves.

- [Passwords and private keys are both supported, and the upstream's own public key is pinned in the Service in OpenSSH format so the proxy verifies the host it connects to.](https://octelium.com/docs/octelium/latest/management/core/service/ssh.md)
- The Service can force the upstream SSH user regardless of what the client asks for, which removes shared privileged accounts as a practical concern rather than a policy exception.
- [Dynamic configuration maps different groups to different upstream accounts and credentials on the same host, so an operations group lands in one account and everyone else in another.](https://octelium.com/docs/octelium/latest/management/core/service/dynamic-config.md)

[Read about secretless access](https://octelium.com/docs/octelium/latest/management/core/service/secretless.md)

Identity

## One identity model for humans, workloads and AI agents

Human and workload Users share the same identity management, authentication, access control and visibility model. A deployment job that needs a shell is authorized and recorded exactly as a person would be.

- [People authenticate through any OpenID Connect or SAML 2.0 identity provider, or GitHub OAuth2, with native FIDO2 and WebAuthn passkeys, TOTP and TPM 2.0 authenticators on top of it.](https://octelium.com/docs/octelium/latest/management/core/identity-providers.md)
- [Authenticate workloads with individual access tokens, OAuth2 client credentials or federated OIDC assertions from platforms such as GitHub Actions, cloud providers and Kubernetes.](https://octelium.com/docs/octelium/latest/management/guide/service/devops/github-action.md)
- [The client runs unprivileged where it has to, using a userspace network stack, so it works inside containers and CI runners as well as on a laptop.](https://octelium.com/docs/octelium/latest/user/cli/connect.md)
- [Cordium, built on Octelium, provides isolated sandboxes for agents and developers, where processes reach authorized Services through the Workspace identity with no secrets inside the sandbox.](https://octelium.com/docs/cordium/latest/overview/intro.md)

[Read about identity and Users](https://octelium.com/docs/octelium/latest/management/core/user.md)

Visibility and auditing

## Session recordings, streamed as they happen

Every SSH session produces AccessLogs identifying the User, Session and Device alongside the SSH detail of the session itself, emitted in real time to your OpenTelemetry OTLP receivers.

- [Entry types cover session start and end, shell, exec and subsystem requests, direct TCP forwarding start and end, and the session recording itself.](https://octelium.com/docs/octelium/latest/management/core/service/ssh.md)
- Recording can be disabled per Service, and stdin recording enabled explicitly, which matters for non-interactive sessions where stdin is not echoed back through stdout.
- [Export structured AccessLogs in real time over OpenTelemetry OTLP to the observability and SIEM systems you already operate.](https://octelium.com/docs/octelium/latest/management/core/visibility.md)

[Read about visibility and auditing](https://octelium.com/docs/octelium/latest/management/core/visibility.md)

Deployment and scale

## Self-hosted, Kubernetes-native and fully programmable

Run the Cluster on Kubernetes infrastructure you control, scale the data plane horizontally, manage resources declaratively, automate the platform through APIs and SDKs, and optionally deploy containerized Service upstreams with the Cluster itself.

- [Hosts, their Services, the Groups that may reach them and the Secrets they use are all YAML in a Git repository, applied with a single octeliumctl apply that reproduces the entire Cluster state.](https://octelium.com/docs/octelium/latest/overview/management.md)
- [Managed containers deploy, scale and serve containerized applications as Service upstreams, alongside the SSH Services that reach the hosts running them.](https://octelium.com/docs/octelium/latest/management/core/service/managed-containers.md)
- [Management is centralized over the Cluster's gRPC APIs, so onboarding a new fleet of hosts can itself be automated.](https://octelium.com/docs/octelium/latest/management/guide/sdk.md)

[Read the management guide](https://octelium.com/docs/octelium/latest/overview/management.md)

SSH at scale

## What SSH access has to solve, and what solves each part

SSH itself is not the difficult part. These are the problems that appear once more than a handful of people reach more than a handful of hosts, next to the mechanism in an Octelium Cluster that handles each one.

1. 01

   ### Getting a key onto the right machines

   Nothing is distributed. The upstream password or private key is stored in the Cluster as a Secret and used by the identity-aware proxy to authenticate to the upstream, so no authorized_keys file has to be maintained across a fleet.

   [Read more](https://octelium.com/docs/octelium/latest/management/core/service/secretless.md)

2. 02

   ### Taking it away again

   Revoking access is a Policy change or a Session revocation rather than a key removal on every host someone could reach, which is what makes offboarding reliable rather than a checklist.

   [Read more](https://octelium.com/docs/octelium/latest/management/core/policy.md)

3. 03

   ### Avoiding a certificate authority to run

   There is no SSH PKI to operate, no signing service to keep available and no certificate lifetime to tune. Authentication to the Cluster is your existing identity provider, and authentication to the upstream is the Cluster's own credential.

   [Read more](https://octelium.com/docs/octelium/latest/management/core/identity-providers.md)

4. 04

   ### Deciding which account someone lands in

   The Service can force the upstream SSH user regardless of what the client asks for, and dynamic configuration can map different groups to different accounts and credentials on the same host.

   [Read more](https://octelium.com/docs/octelium/latest/management/core/service/dynamic-config.md)

5. 05

   ### Verifying the host being connected to

   The upstream's public key is pinned in the Service in OpenSSH format and verified by the proxy on connect, so host key checking is configuration rather than something each person confirms on first use.

   [Read more](https://octelium.com/docs/octelium/latest/management/core/service/ssh.md)

6. 06

   ### Reaching hosts that cannot run a server

   The embedded SSH mode serves SSH from inside the octelium client itself, without a standalone SSH server on the host and without root privileges, which suits fleets of containers, IoT devices and confined environments.

   [Read more](https://octelium.com/docs/octelium/latest/management/core/service/embedded-ssh.md)

7. 07

   ### Limiting what a session can do

   SSH subsystem requests such as SFTP and local port forwarding are both disabled by default and enabled explicitly per Service, so file transfer and tunnelling are decisions rather than side effects of shell access.

   [Read more](https://octelium.com/docs/octelium/latest/management/core/service/ssh.md)

8. 08

   ### Being able to show what happened

   Sessions are recorded and streamed in real time over OpenTelemetry, alongside exec requests, subsystem requests and port forwarding events, each identified by the User, Session and Device behind it.

   [Read more](https://octelium.com/docs/octelium/latest/management/core/visibility.md)

Certificates shorten the life of a credential, which helps. They do not remove the credential from the person's machine, and they add a certificate authority to operate. Injecting the credential at the proxy removes both.

On every Octelium Cluster

The same platform capabilities ship with every deployment, whichever way you use it.

- [OIDC & SAML 2.0 SSO](https://octelium.com/docs/octelium/latest/management/core/identity-providers.md)
- [Native FIDO2, TPM 2.0 & TOTP](https://octelium.com/docs/octelium/latest/management/core/authenticator.md)
- [OpenTelemetry auditing](https://octelium.com/docs/octelium/latest/management/core/visibility.md)
- [GitOps management](https://octelium.com/docs/octelium/latest/overview/management.md)
- [Policy-as-code with CEL & OPA](https://octelium.com/docs/octelium/latest/management/core/policy.md)
- [Managed containers](https://octelium.com/docs/octelium/latest/management/core/service/managed-containers.md)
- [Clientless BeyondCorp access](https://octelium.com/docs/octelium/latest/management/core/service/clientless.md)
- [Anonymous public access](https://octelium.com/docs/octelium/latest/management/core/service/anonymous-access.md)
- [gRPC API & SDKs](https://octelium.com/docs/octelium/latest/management/guide/sdk.md)

Questions

## Frequently asked

- How do people connect?

  With their ordinary SSH client. The Service is reachable at a stable private name over the client-based tunnel, and the identity-aware proxy authenticates to the upstream on the User's behalf. Nothing about the local SSH workflow changes, and no key or password is entered.

- Do I have to run a certificate authority?

  No. There is no SSH PKI to operate. People authenticate to the Cluster through your existing OpenID Connect or SAML 2.0 identity provider, and the Cluster authenticates to the upstream with a password or private key held as a Secret. Which credential is used, and which upstream account it maps to, can be selected per request from identity and context.

- Can it SSH into hosts that do not run an SSH server?

  Yes. The embedded SSH mode lets a connected client serve SSH from inside the octelium client itself, without a standalone SSH server on the host and without root privileges. Authorized Users then SSH into a host by using that Session's name as the SSH user. A Cluster ships with a built-in Service for this, so nothing has to be defined to use it.

- Are sessions recorded?

  Yes. SSH Services emit full session recordings alongside exec requests, subsystem requests and port forwarding session events, streamed in real time over OpenTelemetry to your own log management and SIEM providers. Recording can be disabled per Service, and stdin recording can be enabled explicitly, which is useful for non-interactive sessions where stdin is not echoed.

- Can SFTP and port forwarding be used?

  Both are disabled by default and enabled explicitly per Service, with enableSubsystem for subsystem requests such as SFTP and enableLocalPortForwarding for local forwarding. Port forwarding sessions are recorded as their own event types in the access logs.

- Is Octelium free and open source?

  Yes. Octelium is designed for self-hosting and does not require a proprietary hosted control plane. The core platform is free and open source. An optional enterprise package adds capabilities for organizations with additional operational, identity-management and security requirements, including the web console, SCIM provisioning and Secret encryption at rest.

Keep reading

## Related solutions

### [Zero trust database access](https://octelium.com/solutions/zero-trust-databases.md)

[Secretless PostgreSQL and MySQL access with identity-aware authorization and application-layer database auditing.](https://octelium.com/solutions/zero-trust-databases.md)

[Read more](https://octelium.com/solutions/zero-trust-databases.md)

### [Zero trust Kubernetes access](https://octelium.com/solutions/zero-trust-kubernetes.md)

[Authorize Kubernetes access by identity, verb, resource and namespace while keeping the upstream kubeconfig in the Cluster.](https://octelium.com/solutions/zero-trust-kubernetes.md)

[Read more](https://octelium.com/solutions/zero-trust-kubernetes.md)

### [StrongDM alternative](https://octelium.com/solutions/strongdm-alternative-open-source.md)

[Identity-aware zero trust remote access to SSH, databases, Kubernetes and other infrastructure.](https://octelium.com/solutions/strongdm-alternative-open-source.md)

[Read more](https://octelium.com/solutions/strongdm-alternative-open-source.md)

Get started

## Run Octelium on your own infrastructure

Install a self-hosted Cluster and start applying identity-aware access control to your Services.

[Quick install guide](https://octelium.com/docs/octelium/latest/overview/quick-install.md)[GitHub repo](https://github.com/octelium/octelium)[Enterprise package](https://octelium.com/enterprise.md)
