> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bragi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to get your AI into hardware products

> Distribution routes for AI companies that want their models and services running on consumer devices — and the trade-offs of each.

For an AI company, the phone app is a crowded doorway. The screenless device — earbuds, wearables, hearables — is the next distribution surface, and it's mostly unclaimed. Getting there is a hardware integration problem that most AI companies aren't built to solve alone.

## What are the routes to device distribution?

1. **Build your own hardware.** Full control, enormous cost. Hardware margins, supply chains, and retail are a different business. The graveyard of AI-company hardware launches is well populated.
2. **App-layer presence.** Your AI lives in a phone app the device connects to. Cheapest route, weakest position — you depend on the user opening the app, and you're one of thousands.
3. **Direct brand partnerships.** Negotiate device-by-device with hardware brands. Works, but each deal is a separate firmware integration on a different chip, and sales cycles run long.
4. **Platform-level embedding.** Your AI ships inside an audio software stack that's already integrated at the SoC and firmware level across multiple brands. One integration, many devices.

## Why is audio hardware hard for AI companies?

Earbuds run on milliwatts and megabytes. Models built for datacentre inference don't port down; they get re-architected. Latency budgets for live audio are tight enough that a cloud round trip breaks the experience. And every SoC platform — Qualcomm, Airoha, BES — has its own toolchain. The engineering is embedded DSP work, not ML ops.

## What does "audio-first" mean versus "app-first"?

App-first AI treats the device as an accessory to the phone: the intelligence lives in the app, the earbuds are a speaker and mic. Audio-first AI runs where the audio is — on the device — so it works without the app open, without the phone nearby, and within live-audio latency budgets. Users don't adopt features they have to remember to launch. \[whitepaper: audio-first vs app-first engagement]

## What do hardware brands want from an AI partner?

Proof the integration is already done. Brands move on 12–18 month hardware cycles and won't gamble a product launch on a first-time port. They want AI that's running on their SoC platform, demonstrable on reference hardware, with power and latency numbers in writing.

## Where Bragi fits

Bragi operates the audio software stack that brands and ODMs already integrate at the SoC level. For AI companies, that stack is a distribution channel: integrate once with Bragi, and your service becomes deployable across the devices the platform reaches — audio-first, on-device, without negotiating each brand and chip separately.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.