Build for the disconnected edge
We are building the transport, identity, and coordination layer for the disconnected edge. It has already reached 350,000+ devices across 140+ countries. The hard problems are ahead of us, and we are looking for the people who want to solve them.
Five transports scored on seven factors, switching with hysteresis and cooldown so a fleet in motion never flaps.
A Cortex-M33 leaf under 450 KiB that joins RFC 9420 sessions beside someone else's radio stack.
Map, list, text, and counter documents converging deterministically as compact deltas inside encrypted spaces.
A pipe that classifies every event to a fixed vocabulary, so nothing a remote party typed can ever leave a device.
A gateway contract that lets a zone reach the wider network over Reticulum without trusting the gateway with content.
The same API on iOS, Android, desktop Python, and Rust, with a bridge contract a third party can implement.
Openings
We are always glad to meet builders. If you would work well on offline infrastructure at real scale, send a note about what you would want to build and anything that shows how you work. We keep every note and reply within two business days.
What you would work on
A production offline mesh that has reached 350,000+ devices across 140+ countries. A Rust core with a TypeScript SDK on top, shipping the same surface to iOS and Android, a Python binding for the desktop, and a no_std profile for microcontrollers. The problems are genuinely hard: multi-transport routing and failover, multi-hop relay under real packet loss, end-to-end encryption on constrained devices, and documents that merge deterministically after days offline.
If distributed systems that hold up when the infrastructure does not is the kind of work you want, you will find a lot of it here. Read the platform and the developer reference to see what is already shipped.
What we value
Ship for the edge
We build for the moment the network fails. If it only works online, it does not ship. That constraint shapes every decision we make.
Small team, real ownership
We are early, so the surface you own is large and the feedback loop is short. You will see your work run on real devices in the field.
Architecture over policy
Encryption on by default, keys on the device, nothing emitted until an app asks. We solve problems in the design, not in a document.
Honest and direct
We say what is true, including what is hard or unfinished. We would rather work through a real problem than paper over it.
