Skip to content
Bastyx
Book a Demo
Developers

Built for people who SSH for a living.

Everything you need to judge the work involved: the quickstart, requirements, the one change on your servers, what we integrate with and a four-week pilot. No workspace or call needed to read it.

Terminal session where ssh production is verified by device, identity, security key and policy before connecting.

Quickstart

From zero to a key-touch SSH login.

One pilot team, one server group. Old access keeps working in parallel until you switch it off.

  1. 1

    Connect your directory

    In the Bastyx console, connect Okta, Microsoft Entra ID or Google Workspace, or add people and teams by hand. Pick a pilot team.

  2. 2

    Install the app on pilot laptops

    Install the Bastyx app (.pkg, .msi, .deb or .rpm) by hand or through your MDM. Each person enrolls the device and registers two authenticators, such as the built-in fingerprint sensor and a security key.

  3. 3

    Install the agent on a server group

    Install the bastyx agent package on each server. It adds the Bastyx user CA to sshd, so certificates Bastyx issues are accepted, and ends sessions on revocation. Existing authorized_keys keep working until you switch them off.

  4. 4

    Grant access by policy

    Give the pilot team the server group, and require a security key for anything in production.

  5. 5

    Connect

    The ssh command doesn’t change. The Bastyx app hands OpenSSH a short-lived certificate after a key touch.

    Terminal
    $ bastyx login          # touch your security key or sensor
    $ bastyx status         # check your session
    $ ssh deploy@staging-01 # the command you already use
  6. 6

    Offboard a test user

    Offboard them in the console, then check the audit log. Their open SSH session closes, their laptop won’t unlock, and every change is recorded. See exactly what revocation covers.

Requirements

What you need before you start.

Laptops
macOS, Windows or Linux with the Bastyx app. OpenSSH client 8.2 or later for SSH.
Servers
Linux with systemd and OpenSSH 8.2 or later, such as Ubuntu 20.04+, Debian 11+, RHEL 8+ or Amazon Linux 2023. Root or sudo to install the agent.
Directory
Admin access to Okta, Entra ID or Google Workspace. Without one, a list of people and teams.
Authenticators
Built-in fingerprint sensors or passkeys, or FIDO2 security keys over USB or NFC. We recommend hardware keys for admins and production.
People
One engineer to run the rollout, an owner for each resource you protect, and a pilot team.
Deployment
Bastyx Cloud, or on-premises (customer-hosted) on the Enterprise plan.

Example configuration

The one change on your servers.

The agent trusts the Bastyx user CA using standard OpenSSH directives. No sshd fork, no new client. File names below are examples.

/etc/ssh/sshd_config.d/bastyx.conf · during the pilot
# Accept short-lived certificates issued by Bastyx
TrustedUserCAKeys /etc/ssh/bastyx_user_ca.pub
Check that sshd picked it up
$ sudo sshd -T | grep -i trustedusercakeys
trustedusercakeys /etc/ssh/bastyx_user_ca.pub
/etc/ssh/sshd_config.d/bastyx.conf · after the pilot
TrustedUserCAKeys /etc/ssh/bastyx_user_ca.pub

# Switch off the old ways in
PasswordAuthentication no
KbdInteractiveAuthentication no
AuthorizedKeysFile none

Integrations

Open standards and the tools you already run.

Each entry on the compatibility page is marked available, beta or planned.

Laptops
macOS, Windows and Linux: enrollment, workstation login and the bastyx CLI.
OpenSSH 8.2+
The standard client and server. Bastyx doesn’t replace either.
Okta · Entra ID · Google Workspace
Directory sync. Or manage people in Bastyx.
SAML 2.0 · OIDC
Plus an access proxy and vaulted credentials for apps without SSO.
FIDO2 / WebAuthn
Public-key authentication bound to the origin. The basis of passkeys.
CTAP2
How laptops talk to external security keys over USB and NFC.
Full compatibility matrix

Operating systems, server platforms, identity providers, app access methods and authenticators.

Pilot

Four weeks, one team.

A realistic pilot for one team, one server group and a couple of apps, run by one engineer alongside their normal work.

  1. Week 1

    Identity provider and pilot laptops

    Connect Okta, Entra ID or Google Workspace. The pilot team installs the Bastyx app and registers two authenticators each.

  2. Week 2

    Servers

    Install the bastyx agent on a first server group and grant the pilot team access by policy. Existing keys keep working.

  3. Week 3

    Apps

    Move a SAML or OIDC app to Bastyx, and put one legacy app behind the access proxy or a vaulted credential.

  4. Week 4

    Parallel run and switch-off

    Run old and new access side by side, offboard a test user, check the audit log, then switch off passwords and static keys for the pilot.

A day with Bastyx

Fewer rituals. Same security.

  1. 09:02

    Unlock the laptop

    Fingerprint on the built-in sensor. No password.

  2. 09:15

    ssh staging

    Same command as always. One touch of the security key.

  3. 11:40

    Need production for an hour

    Request access to prod-db. A lead approves it in the flow.

  4. 12:40

    Access ends

    The window closes on its own. Nobody has to remember.

  5. 17:30

    Log off

    Nothing to rotate, nothing to clean up, nothing left behind.

Documentation

More in the open.

The security page covers the architecture and authentication model, the offboarding page states exactly what revocation covers and what happens during an outage, and the SSH guide is useful whether or not you use Bastyx.

See it on servers like yours.

Book a demo and watch an engineer SSH through Bastyx with a key touch, then offboard and read the audit log.