Device-Native Foundation Models logopeterindia.net
Knowledge Hub

Device-Native Foundation Models

A curated index of foundation models built to run on the device itself — Edge0 language and voice models, device solutions, other on-device model families and the runtimes that run them. Offline, private and with no per-use token cost.

26 topics•5 categories•Updated November 13, 2026

What Are Device-Native Foundation Models?

3 entries

Device-native foundation models are pretrained models designed to run inference on the device itself, such as a phone, laptop, earbuds, glasses or a toy, instead of calling a cloud model. They trade parameter count and memory for low power, offline use, on-device data processing and no per-use token cost. Edge0, whose site is the basis of this page, describes its approach as on-device AI built for consumer hardware.

Edge0 Models

7 entries

The Edge0 language models and Audio8 speech models, with figures as published by Edge0.

Edge0 Device Solutions

5 entries

Edge-cloud SDKs that embed Edge0 models in products.

Other On-Device Foundation Models

6 entries

Model families from other vendors that are built or sized for devices.

Runtimes for Running Models On-Device

5 entries

Engines that load and run models on phones, laptops and embedded hardware.

Related Pages

5 entries

Related research directories on this site.

Frequently Asked Questions

What is a device-native foundation model?

A pretrained model designed to run inference directly on a device such as a phone, laptop, earbuds or glasses, rather than in the cloud. It works offline, keeps data on the device and avoids per-use token costs, at the price of fitting within the device's memory and power budget.

Is parameter count the same as memory use?

No. Edge0 makes this point on its site: it says its 35-billion-parameter sparse mixture-of-experts model runs with 1-3 GB of memory by streaming expert weights from SSD, while dense models of similar size need far more RAM. Memory depends on architecture, quantisation and how weights are loaded.

How do device-native models differ from small language models?

Small language models are defined by size. Device-native models are defined by where they run and are engineered around device limits, and they can include speech, vision and larger sparse models as well as small dense ones.

What is edge-cloud coordination?

It splits work between device and cloud. Frequent, simple commands run on the device for low latency and no cost, while complex tasks go to a larger cloud model. Edge0 describes this approach for earbuds, glasses and robots.

Which runtimes can run these models?

Common choices are ExecuTorch, LiteRT, llama.cpp, MLX and MLC LLM, plus vendor SDKs for specific chips. Check each model's documentation for supported formats, because availability differs by model and device.