One model, sized for every SKU
The same assistant is compressed for each device’s chip and memory, with an accuracy report per SKU.
Device makers (OEM) · Build, tune and ship
Assistant updates through your OTA
Ship new assistant versions over your own update channel or ours, signed, staged and reversible.
- Desktop
- Online for actions
Desktop assistantOn this device · connects to act
Roll the new assistant version out to 5% of devices first.
Staged rollout set: 5% this week, then 25% if reports stay low. Confirm to start.
Pause the rollout.
Rollout paused at 5%. Devices that updated keep the new version until you decide.
Roll back the last version.
Rollback prepared to the previous version for all updated devices. Confirm to start.
The problem
Device makers already have a firmware update process and don’t want a second one. Shipping a full model with every change wastes bandwidth and storage. A bad update across millions of devices is costly to undo.
Who uses it
Device maker release and platform teams who already run their own update system.
What you train it on
- Release notes
- Rollout policies
- Device groups
How it works on the device
- 1
Signed packages
Every assistant update is signed and checked on the device before it loads.
- 2
Only what changed
Updates contain just the parts of the model that changed.
- 3
Your channel or ours
Ship through your own OTA system or use ours, with staged rollout and one-click rollback.
Why it runs on the device
Fits your release process
No second update system to run.
Small downloads
Only the changes are delivered.
Safe rollouts
Staged by default and reversible.
Questions
No. You can deliver packages through your own update channel.
Each package is signed, and the device checks the signature before loading it.
Yes. Device groups can follow different rollout plans.
Related use cases
All use casesPut AI where your work happens.
Pick one team and one use case. We’ll have it running on your own devices in weeks.