Iroh On ESP32 — A Device Mesh Without A Cloud IoT SDK

🪩 The Disco Party is MATA's distributed cloud.

The crate is rusty_esp_iroh. The keyword page is esp32 iroh. Iroh on ESP32 is how a sensor, a camera, or a home computer joins a device mesh without a cloud IoT SDK. AWS IoT, Azure IoT Hub, and the vendor SDKs that ship in every development kit all assume the same shape: the chip phones home, the vendor brokers messages, you pay per device per month, and a revoked account bricks the hardware. rusty_esp_iroh puts the iroh mesh on the chip instead. Janus ALPNs name the conversations — rpc, media, telemetry — so peers talk to peers. The cloud is optional. The Disco Party is the network those chips join.

A device mesh is not a MQTT topic with extra steps. It is the same peer-to-peer idea as device sync over iroh, shrunk onto an Espressif part. What Is A Distributed Cloud is the large version. This article is the chip version: why Iroh on ESP32 deletes the IoT middleman, how the crate actually runs, and what changes for hardware that used to rent its own voice.

Why Iroh On ESP32 Beats A Vendor Device Mesh

Cloud IoT SDKs sell you a certificate, a device shadow, and a dashboard. They also sell you a standing copy of every telemetry line and a kill switch. The Electronic Frontier Foundation has spent a decade on exactly this pattern: the "helpful" broker becomes the surveillance broker. Iroh on ESP32 removes the broker. The chip holds an endpoint. Peers connect. Relays, if they exist for NAT, see scramble. MATA is not in the payload path.

Trust is a keypair on the device, verified locally — the same Sovereign ID / mID story, cut down for a chip. Security is QUIC and sealed frames, not a vendor TLS terminator that can be subpoenaed. Incentive is the third Digital Freedom primitive: a home that fronts bandwidth for a device mesh gets paid, instead of a hyperscaler invoicing you for the privilege of reading your own temperature sensor. The Federal Trade Commission keeps a whole desk for products that collected more device data than they needed "to make the app work." A device mesh with Iroh on ESP32 collects what the owner granted. Nothing else.

The Importance of Remade With Rust is why the crate is not a C SDK with a Rust wrapper. Memory-safe on the host is wasted if the chip is a C blob that phones AWS.

How Iroh On ESP32 Builds The Device Mesh

rusty_esp_iroh is Track A: std on ESP-IDF. Iroh needs QUIC and TLS. There is no honest no_std QUIC on these parts today. A bare C6 without PSRAM stays LAN-direct. A part with PSRAM can take relay and short-ticket discovery. That is the measured split, not a roadmap slide.

Janus ALPN — rpc, Media, Telemetry On The Device Mesh

Janus is the doorway between hardware and software — the ESP32/Arduino remake that makes a MATA home computer. Iroh on ESP32 speaks Janus ALPNs so a peer knows what conversation it opened: rpc for commands, media for frames, telemetry for sensors. A device mesh that dumps everything on one anonymous stream is how you reinvent MQTT badly. Named ALPNs keep the IETF HTTP semantics lesson: be explicit about the method. The mesh is not a blob pipe.

What AWS IoT Charges That Iroh On ESP32 Does Not

AWS IoT Core prices connections, messages, and shadows. Vendor clouds add their own MAU-shaped device fees. Iroh on ESP32 has no device registry at a vendor. There is no shadow document on someone else's disk. The Privacy Rights Clearinghouse is a catalog of what happens when that registry leaks. A device mesh that never created the registry cannot leak it. You still have to write firmware that does not log secrets. You do not have to pay Amazon to hold them.

rusty_esp_iroh Replaces The Cloud IoT SDK

The crate is the replacement, not a bridge that still calls AWS "for convenience." Pair it with rusty_esp_mid for device identity and with SpaceDB on the host for local-first storage. Deputy keeps a -sys IoT SDK from sneaking back through a "temporary" feature flag. Source sits with the rest of the remade family at github.com/Remade-With-Rust. Cards live on Remade With Rust.

A Device Mesh With Iroh On ESP32 Joins The Disco Party

Chips are not accessories to the distributed cloud. They are the edge. Digital Freedom Era 2 is peers. Era 3 is the wider mesh. Iroh on ESP32 is how a doorbell or a radio becomes a peer instead of a leased sensor. The Freedom Guide is the human onboarding. What Is Digital Freedom is the frame.

Iroh On ESP32 Does Not Need A Cloud Account To Boot

Vendor provisioning starts with a developer portal. Iroh on ESP32 starts with a flashed endpoint and an owner grant. That is the Trust primitive on metal. The device mesh comes up on the LAN even if every hyperscaler is having a bad Tuesday. Cloud is a later hop, not a birth certificate.

Keep The Device Mesh Small Enough For The Part

No-PSRAM parts do not get a full relay stack. Pretending otherwise bricks the flash partition. Iroh on ESP32 is honest about RAM. A device mesh that respects the die is a mesh that still works in five years when the vendor SDK has moved on to the next chip family and abandoned yours.

Remade Primitives, Disco Party, Digital Freedom

rusty_esp_iroh is a Remade-With-Rust primitive. It becomes a disco party when chips join the same peer-to-peer distributed cloud as laptops and phones. It becomes Digital Freedom when Trust, Security, and Incentive — identity, encryption, payouts — reach the doorbell. Start at the Disco Party and the Learn index. Put Iroh on ESP32. Leave the cloud IoT SDK in the recycling bin.

The keyword landing is esp32 iroh. The doorway those radios walk through is Janus. The identity on the same board is mID on the chip. Phone-and-laptop Iroh, without the chip, is peer-to-peer device sync.