Myrmic is Peeriot’s open runtime for distributed edge applications — the foundation you can inspect, run locally, and build on. The public source goes live on September 10 at RustConf. Until then, this is the short version of what it is and what it isn’t.
Write your application logic once and run it across very different hardware — from Linux gateways down to microcontrollers — while the hardware-near work stays where it belongs.
Application logic is written through one Rust SDK and compiled to portable WebAssembly modules against a single host interface. The same application modules run from Linux gateways down to supported microcontrollers, with target-specific capabilities kept explicit.
The work that doesn’t belong in a portable sandbox — hardware-near, timing-sensitive, target-specific I/O — is handled by Rust-native integration tuned for each target: compiled into firmware on microcontrollers, loaded as native capabilities on OS-based devices.
At runtime, devices form a Swarm: a network of communicating Cell Hosts that coordinate locally — without a central broker. No single point holds the colony together.
Pull the Rust SDK into your project. Familiar from the first line.
Author your application logic once, targeting the single host interface.
Compile to a portable WebAssembly module and run it locally to iterate fast.
Take the same module to a supported target — ESP32-C5 or ESP32-C6.
From September 10, getting started will look familiar to Rust developers. Stay tuned for our launch to become part of the Myrmic community.
Signing, audit trails, and lifecycle management for production fleets belong to EdgeVance, not the open runtime. Myrmic is the foundation; the production controls sit alongside it.
Myrmic’s public source release is coming soon. Until then, our newsletter gives you the short version: what we’re building, what’s coming next, and the repository link the moment it goes live. Join the list to follow the launch and become part of the Myrmic community from day one.
