Add your first device

A benchmark runs on hardware you own, so the platform needs a machine before it can measure anything. This part registers one, which is a single command on the machine itself.

You need something you can install software on and that can reach the platform over the network: a Linux workstation or server (x86_64, arm64 or armv7), a Jetson or similar single-board computer, a Mac, a Windows machine, or an Android phone. The device dials out to the platform, so it needs no public address and no inbound port. A laptop behind a home router qualifies.

note

If your team already runs a fleet, you can skip this part: the devices are shared across every project of the organization, so they are already in your list. Pick a device is where you choose one.

Start the registration

Open Devices in the sidebar and select Register Device. The dialog asks which platform you are installing on, gives you a one-line command to run there, and lists what that platform does differently.

Two things are true on every platform. The command carries an enrollment token, which is how the machine proves it may join your organization without anyone typing credentials on it. By default that token is single use: it registers one device and expires in 90 days. And the agent connects on its own once installed, so there is no device-side configuration step, and the device appears in the list within a few seconds.

Treat the command as a secret while it is unused. Anyone holding it can put a device into your organization, which is exactly what it is for.

Registering a batch

Register many devices turns the one-time token into a batch one: any number of devices can register with that single command, and it expires after ten minutes. That is the tool for provisioning a rack or a shelf of phones in one pass, and the short life is what keeps a copied command from being useful later.

Linux

Choose curl or wget for the downloader, and whether to install for the current user or system-wide with sudo.

• With sudo, the agent installs to /usr/local/bin and registers a system-level systemd service, so it runs whether or not anyone is signed in.
• Without sudo, it installs to ~/.local/bin and registers a user-level systemd service, with a cron @reboot fallback where user services are unavailable.
• Architectures: x86_64 (amd64), arm64 (aarch64) and armv7, so a Jetson or a Raspberry Pi class board is the same command as a server.

Appending -s -- --help after the | sh lists every installer option and environment override without installing anything, which is the safe way to look before you run.

macOS

macOS needs sudo: the agent registers a system-level launchd daemon and installs to /usr/local/bin. Both Apple silicon (arm64) and Intel (amd64) are supported.

Windows

The command is PowerShell rather than a shell one-liner. Installing as Administrator registers a Windows service that runs even when nobody is signed in. Installing as the current user needs no elevation: the agent lands under %LOCALAPPDATA%\Clika\DeviceAgent\, starts at your sign-in, and runs as you with your file permissions, which also means it stops when you sign out. Both amd64 and arm64 are supported.

Android

Android is an app rather than a script, in three steps: download the APK, open the Clika Runtime Agent on the phone, and scan the enrollment QR code the dialog shows. If the phone cannot scan, the same token is there to paste into the app by hand.

It needs Android 8.0 or newer, and the browser doing the download needs the "install unknown apps" permission when it prompts. The QR code in the screenshot above is deliberately blurred, because it encodes a live enrollment token.

What you have now

A machine in the fleet, connected and reporting. The next part finds it in the device list and reads what the platform knows about it.

• Full detail: Device.
• Next: Pick a device.