Answer ready in 0.9 s
On deviceOffline
Every answer comes from the device. Nothing is sent anywhere. Best for vehicles, basements and anything sensitive.
Over-the-air updates
Your updates. Your rules.
Every time you improve the AI, your devices get the new version. You decide when they check, what network they use, which devices go first, and how long any device may stay offline. Pause or roll back with one click.
- Signed and checked before loading
- Staged rollouts with auto-pause
- Only what changed is downloaded
- One-click rollback
Staged rollout
How a new version reaches your devices.
A new version goes to a small pilot group first. If people report problems, the rollout pauses on its own. You resume it, or roll everyone back to the last good version.
- TrainedScored 96.4% on your test questions
- SignedPackage 0.73 GB · delta 41 MB
- Rolling outThree rings, health-checked
- LiveEvery device on the new version
-
Pilot5% · 59 devicesWaiting
-
Early25% · 296 devicesWaiting
-
Everyone100% · 1,184 devicesWaiting
Reports per 1,000 answers0.4
Auto-pause above 2.0
Ready to release v15.
Sample data. Try the buttons when the rollout pauses.
Update policy
Set the policy per device group.
Field phones, service-bay tablets and line gateways live different lives. Give each group its own rules for checking, downloading and staying offline. Try the controls.
Check when it suits the device
Every time the app opens, once a day, once a week, or the moment the device comes back online.
Download on Wi-Fi only
Keep mobile data for work. Only the part of the model that changed is downloaded.
Set an offline limit
After a set number of days without a check, the app asks the user to connect once so no device drifts too far behind.
Offline, auto or online mode
Answer on the device, use your larger cloud model whenever there’s a connection, or stay online for always-connected desks and kiosks.
A different policy per device group
Field phones, service-bay tablets and line gateways can each follow their own rules.
Offline limit
Ask the device to connect after
days offline
Devices in this group check as soon as they’re online, download on Wi-Fi only, and connect at least every 14 days. Answers always come from the device.
Offline devices
No device drifts too far behind.
Devices keep answering while they’re offline. When they reach the offline limit you set, the app asks the user to connect once. Then it skips straight to the latest version.
- Keeps answering offline
The device uses the version it has until it can update.
- Asks to connect after your limit
Pick any limit from 1 to 90 days, per device group.
- Jumps to the latest
Missed versions are skipped. Only the changes since its version are downloaded.
Day 1 · OfflineAnswering with v14
v14
Connect once to get the latest answers. Your service manuals have changed since this device last checked.
Answer modes
Offline, auto or online. Your choice.
The same app can answer on the device, use your larger cloud model when there’s a connection, or stay online for desks and kiosks that never lose signal.
Longer answer from your cloud model
Cloud modelAuto
Uses your larger cloud model when connected, and switches to the device the moment the signal drops. Users never see an error.
Answer from your cloud model
Cloud modelOnline
Answers come from the model in your own cloud. Good for desks and kiosks that are always connected and need the largest model.
Admin control
Nothing ships without your say.
Approvals, update windows and device conditions keep every release predictable. Every action is logged.
Approvals
Choose who can publish. Require two approvals before a version leaves the pilot ring.
Service leadIT admin
Update windows
Install only when devices aren’t in use, for example between 1:00 and 5:00 local time.
Device conditions
Download on Wi-Fi only, and install only while charging or above a battery level you choose.
Wi-Fi onlyChargingBattery 30%+
Version pinning
Hold a device group on a known version, for example during an audit or a line changeover.
v14Line 2 gateways pinned until 30 Nov
Bandwidth
Cap download speed per site and spread downloads over time, so a release never fills a store’s connection.
5 MB/s per site
Signed packages
Every package is signed. Devices check the signature before loading, and refuse anything that was changed.
Signature valid
| Time | Who | Action | Target |
|---|---|---|---|
| 09:12 | IT admin | Approved v15 | Pilot ring |
| 11:40 | System | Auto-paused | Early ring · reports 2.3 per 1,000 |
| 11:52 | Service lead | Rolled back to v14 | Early ring · 296 devices |
| 14:05 | IT admin | Pinned v14 | Line 2 gateways |
Sample data.
Questions
Over-the-air updates, answered.
It keeps answering with the version it has. If you set an offline limit, the app asks the user to connect once the limit is reached. When it connects, it skips any versions it missed and downloads only the changes to reach the latest one.
You decide. Updates can install silently when the app is idle, or you can let users choose a later time within the window you allow.
Yes. Pin a device group to a version for as long as you need, then release the pin when you’re ready.
It depends on what changed. A full model for a phone is usually under a gigabyte. Most updates, such as a new price list or manual section, only send the changes, which are much smaller. We measure this for your data during the pilot.
Yes. Device makers and teams with their own device management can deliver the signed packages through their existing channel. The app still checks the signature before loading.
Roll back in one click. Devices return to the previous version, which they keep for this purpose. If reports rise during a rollout, it pauses on its own before reaching everyone.
Put AI where your work happens.
Pick one team and one use case. We’ll have it running on your own devices in weeks.