Servers

4 min read

A server is a machine in your infrastructure where assigned agents run. It can be a VPS, an on-premises server, or a machine on your network. You retain control of that infrastructure; Kujira connects a supervisor that starts and monitors your agents' containers.

Connect a server

From Organization → Servers, register the machine and run the installation command generated by the dashboard. The provisioning token is shown only once and links that supervisor to your organization.

When the supervisor connects, the dashboard automatically updates its status, detected address, and specifications. You can then assign agents to that server.

Protect the provisioning token

Treat it as a temporary credential: do not share it in chats, repositories, or screenshots. If you could not use it or need to reinstall the machine, generate a new one; the previous token becomes invalid.

On a Windows PC

It needs Windows 10 (version 2004 or later) or 11 —not Windows Server—, at least 4 GB of RAM, and virtualization turned on in the BIOS/UEFI. If WSL is missing, the installation installs it and asks you to restart; if Docker Desktop is missing, it installs it and asks you to open it once. Either way the token is not spent: run the installation again with the same one.

In the command box, pick the Windows tab and use either way:

• Download installer: downloads Kujira-Server-Setup.exe and copies the token. Open it, press Install and follow the steps. If the token does not show up, paste it into its field; if something fails, the installer itself says what to do, and Show details shows the full log to copy.
• The command: paste it into PowerShell. It does exactly the same.

The server is only online while the PC is on and Docker Desktop is open. Turn on Start Docker Desktop when you sign in in its settings so it comes back by itself after a restart. The kujira command is installed too, without sudo: open a new terminal and use kujira status, kujira update or kujira uninstall.

What you can monitor

Availability

Check whether the supervisor is connected, awaiting provisioning, or offline, as well as the last time it reported to the dashboard.

Resources

Review the CPU, RAM, and load average reported by the machine to detect resource pressure or size your infrastructure.

Assigned agents

See how many agents depend on every server and open their configuration from the same view.

Estimated capacity is not instantaneous load: it calculates the scenario in which every assigned agent works at the same time. Above 100%, the machine can run out of headroom during peaks even when its observed load is currently low.

Resource limits and alerts

Set default CPU and memory limits for agent containers on a server. They provide a starting point to protect the machine; an agent can have specific limits when its load requires them.

Enable resource alerts to receive notices when load, memory, or storage need attention. Before concentrating more agents on a server, check both its current load and estimated capacity.

Maintenance operations

Operation	When to use it
Update supervisor	When the dashboard indicates an available version. Update starts from Kujira without opening an SSH session manually.
Regenerate installation	When you will reinstall or replace the machine. It creates a new token and invalidates the previous one.
Delete server	When it has no assigned agents and you will not connect it again.

Before removing a machine, reassign or stop the agents that depend on it. Kujira does not let you delete a server that still has linked agents.

Updating the supervisor

If a new feature tells you a server's supervisor is older than it, update it from a terminal on that machine:

sudo kujira update

It downloads the latest version and recreates the supervisor container with the same configuration. Your agents keep running meanwhile: they are separate containers. When it finishes, sudo kujira status confirms it has reconnected.

If the machine says update does not exist, its copy of the command predates June 2026. Download the current one and try again:

sudo curl -fsSL https://api.kujira.so/kujira -o /usr/local/bin/kujira && sudo chmod +x /usr/local/bin/kujira

When to use several servers

One server is enough to start. Add more when you need to separate environments, customers, or networks, reserve resources for demanding agents, or reduce the impact of an incident on one machine.

Each agent runs on its assigned server. Distributing them gives you control over where their containers, credentials, and local connections live. The number of available servers follows your subscribed agent count; see Plans and limits.

Permissions

Action	Permission
View servers and their status	server.view
Register a server	server.create
Edit limits, alerts, or installation	server.edit
Delete a server without agents	server.delete