Devices

A device is a Pantavisor machine registered to your account. The device registry is the central list of your devices, holding both metadata the device reports and details you add yourself.

API: the devices service — request flows, plus the /devices endpoint reference to try calls live.

Identity and claiming

A device is created in the registry and given a device token it uses to authenticate to the cloud. There are two common flows:

• Device-created — the device registers itself on first boot, either joining your account directly via an auto-join token baked into its image, or registering unclaimed and waiting for you to claim it with its challenge. See How onboarding works for the full comparison.
• User-created — you create the device record first, then configure the device with the resulting token.

Until a device has talked to the cloud at least once, it shows as never seen — usually a sign the client isn't configured with the right token.

What a device reports

Once a device checks in, it announces information about itself: hardware and machine info, the software stack it runs, and which cloud APIs/providers it supports. The UI surfaces this on the device detail view; the same data is available through the API.

Device state

A device's actual configuration lives in its trail — the device reports the revision it is running, and you drive changes by appending steps. So "managing a device" is mostly: inspect its current revision, then append a step to move it to a new goal.

Metadata

Beyond the reported system info, you can attach your own metadata to a device (labels, notes) to organize and find devices. See the device endpoints in the API Reference for the exact fields.