Metadata
Hardware profiles
Capture hardware specs, firmware targets, and tags per SKU.
Platform - IoT device provisioning
Provision Linux IoT devices with repeatable per-SKU defaults.
Use device classes and organisation-specific install commands to move hardware from factory or field setup into a consistent inventory record.
- Define hardware metadata, tags, and configuration defaults once per device class.
- Bind claimed hardware to the correct customer account and entitlements.
- Issue install commands for the appropriate organisation and device class.
- Carry provisioning, ownership, and activation history into monitoring and support.
Device classes as SKU blueprints
Define defaults once, reuse them across every device.
Config
Provisioning defaults
Set baseline config and policy for each class.
Inventory
Default assignments
New devices inherit class metadata on first check-in.
Ownership, licenses, and warranty
Customer onboarding and entitlements live next to provisioning.
Ownership
Customer accounts
Bind a device to the right customer account.
Licenses
License bundles
Track entitlement counts and coverage windows.
Warranty
Warranty tracking
Warranty starts on first check-in, not on a spreadsheet.
From install command to monitored device
Use the same repeatable workflow for a Raspberry Pi pilot, factory image, or field-installed Linux gateway.
- Generate the install command for the intended organisation and device class.
- Run it on an internet-connected Linux device and confirm its first check-in.
- Verify customer assignment, tags, monitoring, and activation events before scaling.
Install
Provisioning command
Install command is generated from the login flow.
First check-in
Immediate visibility
Device shows up in inventory within minutes.
Ownership
Customer assignment
Assign devices to the right customer during activation.
Ready to validate the workflow?
Install the agent and see inventory and logs in one place.