SSH certificate authority for teams

SSH access that expires on its own.

Replace scattered authorized_keys files with short-lived SSH certificates. Invite people by email, enrol servers with one command, renew automatically when you connect, and take access away in minutes.

Start freeFree for up to 100 servers. No card needed.

From invitation to first login in three steps

  1. Invite your team

    Create an organisation, add environments and departments, and invite people by email. Choose which server accounts each person may use.

  2. Enrol your servers

    Add a server and run the command we give you. The server trusts your CA and checks who may log in every five minutes.

    sshking-server enroll …
  3. Log in with a certificate

    People approve a code in the browser once. After that, ssh fetches a fresh short-lived certificate by itself. No keys to copy to servers, ever.

    sshking-user login

Built for teams who are tired of chasing old keys

Certificates that run out

User certificates last hours, not years. A lost laptop stops working by itself.

Renewal nobody notices

A plain ssh renews the certificate when it runs low. Ask people to confirm in the browser as often as each organisation, environment or server requires.

Accounts and sudo, set in one place

Choose who logs in as which account and who gets sudo. Servers create missing accounts and update sudo within five minutes.

Removal in minutes

Take someone out of a department and every server in it refuses them within five minutes, even before their certificate expires.

Rotation without downtime

New CA keys are published before they sign, and old ones stay trusted until their last certificate expires. Or rotate and revoke at once if a key leaks.

Access that matches your org chart

Grant access to an organisation, an environment, a department or a single server, as member or admin.

Host keys you can trust

Servers present host certificates too, so nobody types yes to an unknown fingerprint again.

A record of every change

Each invitation, certificate, rotation and removal lands in the audit log for your organisation.

Pricing

Free

£0
Up to 100 servers per account
  • Unlimited people and organisations
  • Environments, departments and servers
  • Staged and emergency CA rotation
  • Audit log and email invitations
Start free

More than 100 servers

Let's talk
For larger fleets and companies
  • Everything in Free
  • As many servers as you need
  • Help with roll-out and migration
  • Priority support
Contact us

Questions

What is an SSH certificate authority?

A CA signs SSH keys for a limited time. Servers trust the CA instead of a list of keys, so access is granted by issuing a certificate and ends when it expires, with no authorized_keys files to keep in sync.

How is this different from authorized_keys?

authorized_keys entries never expire and live on every server. With SSHKing, people get certificates that last hours, access is managed in one place, and removing someone takes effect on every server within five minutes.

What counts as a server?

Any server you enrol to accept certificate logins. People, organisations and environments are not counted. The 100 free servers are shared by all organisations you create.

Do existing SSH keys stop working?

No. Enrolment adds certificate logins next to authorized_keys. Remove the old keys when you are ready.

What do people need on their laptop?

OpenSSH and curl. The sshking-user helper is a small shell script that works on macOS and Linux.

Where are the CA keys kept?

Encrypted in the database with a master key that only the service holds. A key that stops signing is destroyed.