Skip to content

On-device

On-Device Speech Recognition

Speech models that run entirely on phones, wearables, and small hardware: English transcription plus calibrated emotion and speaking-style labels, fully offline.

Free evaluation build · Per-device annual license · No per-minute metering

Request an evaluation build

Free, time-boxed, compiled for your target device. A person replies from access@oruk.ai within one business day.

Want to validate accuracy first? Try the hosted API free — $5 credit, no card.

Audio never leaves the device
Inference runs on the silicon you ship. No cloud round-trip, no connectivity dependency, no per-request data exposure.
Licensed per device, not per minute
One flat annual rate per active device, stepping down with fleet size. Cost never scales with how much your users talk.
More than transcription
The same model family behind the oruk API: English transcription plus 15 calibrated emotion labels and 16 speaking styles — signals no embedded ASR vendor ships.
Shipped devices keep working
Weights run locally, so a model on your hardware cannot be remotely sunset. Support windows and survival terms are written into the license.

How licensing works

  1. 01

    Tell us your hardware. Target chipset, task (transcription, affect, or both), and expected fleet size. A person replies within one business day.

  2. 02

    Free evaluation build. A compiled build for your target device under a time-boxed license — no card, no commitment. Accuracy and latency are measured on your own audio, on your own silicon.

  3. 03

    License per device. If the numbers hold, production is a flat annual per-device rate with model updates included. Custom builds for your footprint and task are scoped separately.

Request an evaluation build

Free evaluation. No card, no commitment.

Why a lab, not a model zoo

The model family

oruk trains its own speech models. On speech-emotion-bench — 64,384 held-out clips, one identical scoring pipeline across 64 systems — the hosted family reaches 77.6% accuracy (trained in-distribution; protocol and caveats on the methodology page). On-device builds are compressed from the same family and validated against your acceptance criteria during evaluation.

The alternative

Free runtimes exist, and for transcript-only prototypes they are a fine start. What they don’t give you: acoustic emotion and speaking-style signals, tuning for your microphone channel and acoustics, a vendor on the hook for accuracy on your hardware, and license terms that survive an acquisition. If your product depends on the speech layer, that gap is the product.

Request an evaluation build

Free evaluation. No card, no commitment.

Exactly what you are buying

The limits below are stated here so you do not discover them after integrating.

English only
Models process English speech. No production multilingual support today.
Specs are measured, not quoted
We do not publish generic size, memory, power, or latency figures — those depend on your chipset and task, and are established during the evaluation on your hardware. Be suspicious of vendors who quote them unseen.
Benchmark numbers are the cloud family
The 77.6% speech-emotion-bench result below was measured on the hosted model family with one open pipeline (methodology, including the in-distribution training caveat). Compressed on-device variants are validated against your acceptance criteria during evaluation.
What emotion scores are — and are not
Calibrated acoustic signals about how speech sounds — not intent, truth, medical, employment, or psychological judgments. See responsible use.
Data and training
On-device inference means we never see your audio at all. Across the whole product line, oruk never trains on customer content.
Prefer hosted?
The same models run behind a synchronous REST API from $0.0045 per audio minute with a $5 trial credit — the fastest way to validate accuracy before committing to a hardware evaluation. See the cloud API.
Request an evaluation build

Free evaluation. No card, no commitment.

Prove it on your silicon

Send your target hardware, task, and expected fleet size. You get a compiled evaluation build and measured numbers on your own audio — then decide.