esp32 iroh — The Mesh On The Chip Without AWS IoT
esp32 iroh is rusty_esp_iroh: an iroh endpoint on ESP32, Janus ALPNs for rpc/media/telemetry, and a bridge for no_std nodes — no AWS IoT SDK.

🪩 The Disco Party is MATA's distributed cloud.
esp32 iroh is the crate that puts the iroh mesh on an Espressif part. The repo is rusty_esp_iroh. Search for esp32 iroh and that is the tool: an endpoint on ESP32 (std / ESP-IDF), Janus ALPN protocols for rpc, media, and telemetry, a host client, and a bridge that fronts no_std nodes. It replaces cloud-IoT device SDKs and connects natively to a MATA Home Computer and the Disco Party.
AWS IoT, Azure IoT Hub, and the vendor SDKs in every development kit assume the chip phones home. esp32 iroh assumes the chip is a peer. What Is A Distributed Cloud is the large version. This page is the keyword and the crate: why esp32 iroh exists, how it runs, and what it deletes.
Why esp32 iroh Beats A Cloud IoT SDK
Cloud IoT sells you a certificate, a device shadow, and a dashboard. It also sells a standing copy of every telemetry line and a kill switch. The Electronic Frontier Foundation has spent a decade on exactly this pattern. esp32 iroh 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 — mID on the chip via rusty_esp_mid. Security is QUIC and sealed frames, not a vendor TLS terminator. Incentive is the third Digital Freedom primitive: a home that fronts bandwidth for an esp32 iroh node can get paid, instead of a hyperscaler invoicing you to read your own temperature sensor. The Federal Trade Commission keeps a desk for products that collected more device data than they needed "to make the app work."
The Importance of Remade With Rust is why esp32 iroh is not a C SDK with a Rust wrapper. Memory-safe on the host is wasted if the chip is a blob that phones AWS.
How esp32 iroh Runs On ESP32
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. esp32 iroh is honest about that. A bare C6 without PSRAM stays LAN-direct, long tickets with the IP, relay off. A part with PSRAM takes relay and short-ticket discovery. That is the measured split n0 published on ESP32 / S3 / C6 / C61 / P4 — not a slide.
Janus ALPNs — What esp32 iroh Names
Janus is the doorway between hardware and the mesh. esp32 iroh 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 MQTT with extra steps. Named ALPNs keep the IETF HTTP semantics lesson: be explicit about the method.
The Bridge — When The Part Cannot Hold QUIC
Not every Janus board has the RAM for esp32 iroh's full endpoint. no_std nodes reach the mesh through a bridge — a Pi, a PSRAM ESP — that verifies the mID session and fronts them. The crate ships that bridge and a host client. The catalog card lives on Remade with Rust. Source is github.com/Remade-With-Rust/rusty_esp_iroh.
What AWS IoT Charges That esp32 iroh Does Not
AWS IoT Core prices connections, messages, and shadows. Vendor clouds add MAU-shaped device fees. esp32 iroh 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 mesh that never created the registry cannot leak it.
esp32 iroh Joins The Disco Party As A Peer, Not A Sensor
Chips are not accessories to the distributed cloud. They are the edge. Digital Freedom Era 2 is peers. Era 3 is the wider mesh. esp32 iroh 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.
esp32 iroh Does Not Need A Cloud Account To Boot
Vendor provisioning starts with a developer portal. esp32 iroh starts with a flashed endpoint and an owner grant. 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. Deputy keeps a -sys IoT SDK from sneaking back through a "temporary" feature flag.
Keep The Binary Small Enough For The Part
No-PSRAM parts do not get a full relay stack. Pretending otherwise bricks the flash partition. esp32 iroh is honest about RAM. A mesh that respects the die 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. Search esp32 iroh and you should land here, then on the repo. 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. Flash esp32 iroh. Leave the cloud IoT SDK in the recycling bin.
The longer device-mesh cut is Iroh on ESP32 without a cloud IoT SDK. 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.

