Skip to content
Join the waitlist
Nokku on GitHubQuestions? Send us an email!

Early preview. Self-hosted first.

authorized_keys
is dead. Long live certificates.

Nokku makes SSH certificates something you never have to think about. Your SSO decides who gets in, servers with the daemon hear about it live, and your team keeps typing plain ssh.

~/.ssh/authorized_keys on db-01
  • ssh-rsa AAAAB3…x9q alice@old-laptopleft in 2024
  • ssh-rsa AAAAB3…77f temp-contractorstill active
  • ssh-ed25519 AAAAC3…k1p bob@workstationno expiry
  • ssh-rsa AAAAB3…m2w deploy@ci-runner-04unknown owner
  • ssh-rsa AAAAB3…q0a root@jumphost-oldforgotten
  • and 42 more lines
Grants in workspace acme
  • alice@acme.comroot@db-01
  • team sreubuntu@web-01
  • ci-deploydeploy@web-01

3 grants, every one has an owner

Go on, try to break it.

A small model of a Nokku workspace. One person, one control plane, three servers. Push the buttons and see what gives.

Alice has a grant on three servers. Her ssh goes straight from her laptop to each one. The core hands out policy and stays out of the way.

Who did what, on which server.

Sessions on daemon servers are recorded and tied to a real person, not a key file. Each recording is encrypted with a key of its own. Everything else lands in the audit log, ready for the auditor and your SIEM.

Recording of alice@acme.com as deploy on db-01
  1. deploy@db-01:~$ pg_dump orders | gzip > backup.sql.gz
  2. deploy@db-01:~$ aws s3 cp backup.sql.gz s3://acme-backups/
  3. upload: ./backup.sql.gz to s3://acme-backups/backup.sql.gz
  4. deploy@db-01:~$ psql -c "select count(*) from orders"
  5. 48211
  6. deploy@db-01:~$ exit
Audit log of workspace acme
  1. 14:02:11alice@acme.com got a certificatedeploy on db-01
  2. 14:02:14alice@acme.com opened a sessiondb-01, recording on
  3. 14:19:36bob@acme.com was deniedno grant for root on db-01
  4. 14:31:02admin@acme.com added a grantteam sre as ubuntu on web-01
  5. 14:44:58alice@acme.com closed the sessiondb-01, recording stored
  6. 15:10:27admin@acme.com watched a recordingalice on db-01

Three commands per server.

Enroll a server, grant yourself an account on it in the web app, and connect. The quickstart walks through it.

On the server
  1. $ curl -fsSL https://get.nokku.sh/nokkud | sudo sh
  2. $ sudo nokkud enroll
  3. $ sudo systemctl restart nokkud
On your laptop
  1. $ curl -fsSL https://get.nokku.sh/nk | sh
  2. $ nk login
  3. $ ssh ubuntu@my-server
Port 22 stays yours
The daemon listens on 4022 and never touches the system sshd. If anything goes wrong, your old way in is still there.
No agent, if you prefer
nk sync sets up plain sshd over your own ssh connection. Nothing gets installed on the server.
No bastion to babysit
Servers behind NAT are reached through an encrypted relay. Opening a port only makes it faster.

Rather run the core yourself?

It is one binary and PostgreSQL. Put NOKKU_BASE_URL, NOKKU_SECRET and POSTGRES_PASSWORD in a .env file, then start it with Compose. It runs on Kubernetes and as a plain binary too.

Read the self-hosting guide
On your own hardware
  1. $ git clone https://github.com/nokku-sh/nokku && cd nokku/core
  2. $ docker compose -f compose.prod.yml up -d

Don't trust us. Read the code.

Everything that runs on your servers and your laptop is open source. Check what it does before it gets near sshd.

Your SSO decides
OIDC, with SCIM to add and remove people. Require it for the whole workspace so there is no other way in.
Keys that stay on the device
nk and nokkud keep their keys in the TPM when there is one. A stolen token is useless on another machine.
Passkeys
Phishing-resistant sign-in to the control plane, hardware keys included.
Robots welcome
Service accounts give CI jobs their own identity, with the same grants and the same audit trail as people.
A terminal in the browser
Open a shell on a daemon server from the web app when your laptop is not around.
Your hardware or ours
One binary and PostgreSQL if you host it yourself. Built in Austria and hosted in the EU if you don't.
Access that runs out
Grant a server for an hour or a week. When it ends, servers drop it and close the sessions on it.
Ask, then approve
People ask for an account with a reason, from the web app or nk request. An admin approves it and it expires on its own.
Ready for the audit
Export who can reach what for every review, and stream every event to your SIEM as it happens.

Knock knock.

Who's there? Whoever your SSO says. Self-hosted comes first, the EU cloud follows. Leave your email and we'll tell you when there's something to try.

Or read the quickstart