Phones
A default assistant that works offline, on flagship and entry models alike.
Phone, tablet, PC, car and IoT makers can ship their own assistant as the default, with their own name, voice and wake word. It runs on your chip, answers offline from the first boot, and improves through your own update channel.
Your assistant is set up during first boot, then handles device requests on the device itself.
Users see your brand from first boot to every answer. Nobody else’s name appears on the device.
| SKU | Runs on | Size | Kept |
|---|---|---|---|
| Flagship phone | NPU | 1.1 GB | 97.8% |
| Mid-range phone | NPU + GPU | 0.73 GB | 96.4% |
| Entry phone | CPU | 0.41 GB | 93.9% |
| Tablet | GPU | 0.73 GB | 96.4% |
We compress the model for each SKU’s chip and memory, NPU, GPU or CPU, and report how much accuracy it keeps on your own test questions before anything ships.
New versions go out as signed packages with only what changed. Use your existing system update channel, or the RageEdge one, with staged rollouts and one-click rollback either way.
Every model package is signed and checked on the device before it loads.
Devices download the difference, not the whole model.
Pilot groups first, then everyone, with one-click rollback.
Answers come from the device, so your users’ words stay with them and you don’t pay a cloud provider each time they ask.
Questions and answers are handled locally. Nothing is uploaded to be understood.
Usage grows with your installed base without a matching cloud bill.
No account, network or download is needed before the assistant can help.
A default assistant that works offline, on flagship and entry models alike.
Study, work and family help without a connection.
Built into the OS, using the laptop’s own NPU or GPU.
An in-car voice assistant that keeps working in tunnels and on remote roads.
Voice search and settings help, answered on the box.
Small models for quick requests on the wrist.
Appliances that explain themselves and answer questions about their own settings.
Tell us the chip and memory budget, and we size the model for it.
Pick one SKU and the requests that matter. We run a first build on your hardware.
Your brand, voice and system actions, with an accuracy report on your test set.
Default-assistant setup in your build, and your update channel or ours.
Builds for every SKU, staged rollouts, and a report loop that keeps improving it.
No. Default-assistant integration is for Android builds and makers’ own operating systems. On other platforms, the same engine can run inside your own app.
We build for the NPU, GPU or CPU in each SKU. Tell us your chip and memory budget during evaluation and we confirm what fits, with an accuracy report.
Not to answer. Requests that by nature need the internet, like a web search, can use it when you allow it. Everything else runs on the device.
Yes. Model packages are signed files that your system update channel can deliver. You can also use the RageEdge channel with staged rollouts and rollback.
You do. The assistant carries your name, and the data you train on stays yours. What users say stays on their device.
Pick one team and one use case. We’ll have it running on your own devices in weeks.
Ask ChatGPT, Claude or Perplexity and see what they think. One click, instant insight.