Target Groups
Myrmic provides one edge-first application model, but different teams reach it through different problems.
Choose the path closest to what you are building. Each page separates what the developer preview demonstrates from what the roadmap stages — Partition Tolerance, Durability, and Secure Swarm — are designed to add.
Asset-centric software
Make every asset a first-class application participant
For teams whose software view of a machine, building, room, energy system, or other asset is scattered across telemetry, databases, gateways, and rule engines.
Explore asset-centric software
Connected products
Build the product, not another proprietary device platform
For product teams that need reusable application logic across device generations without giving up native hardware performance.
Real-time applications
Give every room, session, and match a durable home
For teams whose real-time concepts outlive the WebSocket process currently serving them.
Explore real-time applications
Workflows and agents
Give long-running work a place to live
For systems that need durable context, timers, asynchronous continuation, and explicit recovery semantics.
Platform engineering
Give developers one stateful application primitive
For platform teams supporting developers who repeatedly rebuild state, messaging, scheduling, placement, and recovery.
Different entry points, one platform
Across all five groups:
- long-lived concepts become addressable Cells,
- state and behaviour stay together,
- Commands, Events, and callbacks connect the application,
- capability tags guide placement,
- the Signal Layer keeps hardware-near work native,
- the same model spans OS-based and MCU-based Nodes,
- stronger authority and data guarantees arrive in explicit roadmap stages.
See also
- Why Myrmic - the mission behind Myrmic
- Concepts - the vocabulary every other page assumes
- Guarantees - what the current release promises, and what it doesn't yet
- Roadmap - what future stages are intended to add