Skip to content
Docs
Enterprise

In the console, open Devices → Add device.

You can add as many devices as your plan allows. Overview will show you how many are still available. You will also need the admin or owner role to add devices.

Every device enrolls itself with a one-time credential from the console. Once a machine has enrolled, nothing needs approving.

From the Devices → Add device page, choose I will, then Create installer and Download installer. The installer carries the credential required to activate a device, so treat it like a password until a machine has used it.

Open the downloaded .cmd file and accept three prompts:

  1. Keep: your browser warns that .cmd files can be harmful.
  2. Run: Windows says the publisher couldn’t be verified. This is expected until the signed installer ships.
  3. Yes: the administrator prompt for Windows Command Processor.

A window will display the installation progress, and will finish with the model’s first reply.

Under the download button, Install from a terminal instead shows a one-line command with the same credential.

Open Start, type PowerShell, right-click it, choose Run as administrator, then paste the block and press Enter.

When someone else will run the installer, for example an employee on their laptop, select Someone else. The console creates a link you can copy, email, or paste into Slack or Teams.

The receiver opens the link on their machine, which will detect the operating system they are running and display a download button for Cascadia. They don’t need to sign in.

Anyone with the link can add one device until it’s used or expires. Send it directly to the person doing the install, and select Cancel link if it goes to the wrong place.

Admins can monitor the device’s enrollment in the console under Link activity.

Turn on Batch install to enroll several machines with one credential, for example while imaging a batch of laptops.

Set Machines to the number you’re installing now: anyone holding the credential can add devices until it’s used up. A Label such as Portland lab batch shows which credential each device enrolled with.

The device appears on Devices as soon as it enrolls, then reports its hardware, models and status with its first heartbeat. It starts with a small model on the CPU. To serve larger models or use the GPU or NPU, deploy a model from the Fleet Manager.

Each credential has an expiry, shown under Credential details. After a machine enrolls, the credential is spent: create a new one for the next machine.

For a machine that can’t reach the console, open Manual install under the installer. Download the build, save the provision.toml shown there next to it, and run setup on the machine. The machine still needs to reach ca.cascadia.to to enroll.