Nexus Suite No release

Licenses

One site code
licenses the LAN.

Nexus does not phone home. The license is a site activation code you hold. Clients store only a hash. Management APIs stay closed until that code is present.

How to use it How to use it
01RegisterAsk an operator for a site code
02ControllerHelp → License Information
03ClientsPush the code, or bake activation.code

Get a license

Issue files you can keep.

Public registration is closed. An operator can issue a site code from the admin portal. You still apply that code in the Controller and on Clients. Planned PC counts are notes only; the software does not cap seats.

activation.code

Plain site code

One line, letters and digits, matching Controller → Help → License Information → export.

nexus-license.json

Local record

Organization, optional contact, optional PC count, and the same code. Keep a copy with your records.

How to use it

Apply the same code everywhere.

Minimum 6 letters or digits. Spaces and dashes are ignored. The Controller keeps the plaintext code; each Client keeps only sha256("nexus-activation-v1:" + code).

Controller

Help → License Information

Paste the code, then send it to online clients. Export activation.code from that dialog when you generalize a lab image.

Client UI

This PC page

On an unlicensed Client, enter the same code and Activate. Chat and remote management stay closed until then.

Disk image

Bake the file

Place activation.code next to the Client executable, or in the client data directory (%AppData%\nexus-client on Windows). Clones keep the license and get a new device ID.

Scripted

Env or flag

NEXUS_ACTIVATION_CODE or --activation-code. Unactivated agents stay discoverable; inventory, lock, and files return 403.

After hardware changes, clones keep the code. Reset identity with --reset-identity only when you need a fresh device ID on the same machine. Ask an operator if you need the files again.