Microcontroller substrate for AI Operating Systems
Research · AI Operating Systems

Operating systems that learn, adapt, optimize.

Embedded operating systems are evolving from static schedulers into adaptive AI-native platforms. Our research powers EAI (the embedded AI runtime) and the EoS RTOS scheduler — deployed today across automotive, drones, smart-home, and industrial systems.

EAI Integration

Two variants. Same EoS substrate.

EAI-Min — a lightweight agent runtime for edge and mobile devices. Supports llama.cpp, ONNX, and TFLite. Fits in 312 MB of flash, runs a 1.3B-parameter LLM at 11 tok/s on a Cortex-M85.

EAI-Framework — an industrial-grade AI platform with MQTT, OPC-UA, and CAN connectors, a policy engine, and full observability. Used in factory floors, utility networks, and connected fleets.

Both variants build and deploy via eos-platform 1.0 and run on the EoS RTOS with deterministic scheduling and ASIL-D safety partitions when needed.

Read the EAI product page →
EAI inference visualisation
Application Verticals

Four industries, one operating system

Same EoS substrate, vertical-specific runtime profiles and safety subsets.

Self-driving stacks & in-car AI
Automotive

Self-driving stacks & in-car AI

Real-time perception, decision-making, and control. Sensor fusion across LIDAR/camera/radar, path planning at 100 Hz, ASIL-D safety partitions enforced by EoS-S. Today: in 6 EV models. Tomorrow: SAE Level 4 reference profile.

  • Sensor-fusion runtime (LIDAR + cam + radar)
  • 100 Hz deterministic path planning
  • ASIL-D safety partitions (EoS-S)
  • Over-the-air model updates with attestation
Drone & UAV autonomy
Aerial

Drone & UAV autonomy

On-board AI for navigation, obstacle avoidance, and mission planning. Sub-millisecond control loops on Cortex-M85; INT4 vision models that run between flight-control ticks. Operating today in agriculture, surveying, and SAR.

  • Sub-ms flight control on M85
  • INT4 on-device vision
  • Mesh swarm coordination via EIPC
  • Ground-station HIL via EoSim
Smart home & wearables
Consumer

Smart home & wearables

On-device LLM assistants, gesture recognition, and predictive control across sensors. Voice + intent inference without sending audio to the cloud. Privacy-by-default through the on-device-only attestation flag (Embedded AI Ethics WG draft 0.3).

  • On-device LLM assistants (no cloud)
  • Gesture & voice recognition
  • Predictive HVAC/lighting control
  • Privacy-by-default attestation
Factory floor, fleet, infrastructure
Industrial · Cross-industry

Factory floor, fleet, infrastructure

Predictive maintenance, anomaly detection, and adaptive scheduling across sensor meshes. EAI-Framework variant with MQTT/OPC-UA/CAN connectors and a policy engine. Deployed across 12 industrial sites and 3 utility networks.

  • Predictive maintenance models
  • Adaptive scheduling at the edge
  • MQTT · OPC-UA · CAN connectors
  • Full observability via metrics + traces
Open Research Questions

What we're still figuring out

Active research threads — RFC links, working-group drafts, and academic collaborators welcome.

Can model weights be sealed to silicon?

Today's EAI loads quantized weights from QSPI flash. We're researching attested weight loading where eBoot's runtime attestation gates the weight blob — so a model only decrypts on the device it was provisioned for.

What are the energy bounds for on-device inference?

EAI 0.9 pulls 412 mW peak running a 1.3B-parameter LLM at 11 tok/s. Open question: what's the theoretical lower bound for transformer inference on Cortex-M class silicon? Working with two academic groups on a formal energy model.

How do we standardize on-device AI ethics?

The Embedded AI Ethics working group is drafting a manifest schema where every model declares: trained-data origin, on-device-only flags, opt-out attestation patterns, and post-deployment update policy. Public RFC due Q3 2026.

Can RTOS scheduling adapt to inference workload?

Today the EoS scheduler is workload-agnostic. We're prototyping an inference-aware variant that knows about transformer block fetches and can preemptively wake the QSPI fetcher to avoid weight stalls. Early results: +18% throughput at the same power.

Build with EAI. Contribute to the research.

Read the docs, join a working group, or contribute upstream — every layer is Apache 2.0.