ZeroBits Runtime Layer

Deterministic firmware orchestration without a full RTOS.

ZeroKernel gives microcontroller projects a bounded scheduler, fault-aware supervision, key-based routing, and modular network helpers while staying small enough for real device work.

Read the docs See the numbers

Cooperative and phase-aligned scheduling
Fixed-capacity runtime with no active-path heap allocation
Safe mode, panic flow, watchdog, capabilities, and execution contracts
Optional network modules that stay out of the build unless used

Why teams use it

ESP32 network helpers are now documented as stable enough

+456B accepted module overhead in the ESP32 net compare

4 main target families validated in compile matrix

ABI 2 published runtime contract for reproducible firmware

Execution stack

Keep the core lean. Push optional behavior into modules. Pay only for what is actually linked into the firmware.

1 Application Tasks

2 Optional Net Modules

3 ZeroKernel Core

4 Adapters and HAL

5 Microcontroller

Wemos / ESP8266

Wemos D1 mini / ESP8266

Before After

ESP32

Before After

Built for real embedded workloads

Sensor monitors that must stay on cadence while filtering and alarming

HTTP / MQTT gateway nodes that need bounded queue behavior

Industrial loops that need recovery, task gating, and deterministic control timing

Direct-AP field nodes where transport pressure and sensing happen at the same time

What the docs cover

Install in Arduino IDE or PlatformIO
Core API and quick-start usage
Profiles for small nodes and network-heavy nodes
Examples, scripts, compare runners, and module status

Docs Benchmarks