Nokku LogoNokku
Nokku LogoNokku

Quickstart

Set up the CLI, enroll one server, assign access, and make an SSH connection.

Last updated on Aug 9, 2026

This guide uses the managed Nokku service and a Linux server where you have root access. It uses the daemon-managed setup; manual setup is described separately.

Create a workspace

Create a Nokku account and workspace. A workspace is the boundary for your members, targets, access assignments, and certificate authorities. Workspace creation creates a default SSH certificate authority.

Install nk

Run this on your workstation:

curl -fsSL https://get.nokku.sh/nk | sh

Sign in

nk login

The CLI opens a browser-based login flow. When it completes, nk registers the machine’s signing identity and synchronizes the workspaces, targets, principals, and certificate authorities available to your identity.

TPM on Linux

On Linux, TPM-backed request signing needs your user in the tss group. If you don’t set this up first, nk uses a software fallback key. On Windows, nk uses the TPM automatically. See Install & Login.

Create and enroll a target

Generate an enrollment token for the workspace. On the target server, run:

curl -fsSL https://get.nokku.sh/nokkud | sudo sh
sudo nokkud --enroll <TOKEN>

Enrollment creates the target in the core automatically. The daemon receives its credentials, synchronizes the target, and starts an embedded SSH server on port 4022 for certificate authentication. Make sure the target firewall allows TCP 4022 to your users. Depending on workspace settings, an administrator may need to approve the daemon.

Assign access

On the target, assign your user to the Linux principal you want to use, such as ubuntu or root.

The principal is the requested Linux username. The certificate identifies the Nokku user separately, so multiple people can be assigned to the same Linux account.

Connect

After the target is online and access is assigned:

ssh ubuntu@your-target-name

nk uses the generated SSH configuration and its proxy command to connect to the target. It requests a user certificate from the core when a usable local certificate is not available.

Verify the setup

nk status
nk ls
nk doctor

If the target is not listed, check the workspace membership and principal assignment before debugging the server.

Next steps