The archive · Developer & Business Tools · Product decision · 2026
n0 bets 'dial keys, not IPs': Iroh 1.0 ships after 4 years, 200M endpoints in 30 days
n0 ships Iroh 1.0 after four years and 65 versions: a Rust library that dials devices by key, not IP, aiming to be the connectivity layer for distributed apps.
N0, Inc.
What the business is
N0, Inc. develops iroh, an open-source Rust networking library that lets applications address and connect devices by Ed25519 public key instead of IP address; the company runs public relays and offers hosted relay infrastructure plus paid support schedules to customers.
How it started
Iroh grew out of the belief that IP addressing is the wrong abstraction for application networking: addresses are assigned by networks, change without warning, hide behind NAT and carry no identity. The team built in the open for more than four years across 65 pre-release versions, implementing QUIC multipath and QUIC NAT traversal from IETF drafts so one connection can span and hot-swap routes, plus local-first configurations that work with no internet at all.
What happened
On June 15, 2026, n0 shipped Iroh 1.0 - 'Dial keys, not IPs' - with two commitments that turn a library into a platform: wire-protocol and API stability across languages, and official Python, Node.js, Swift and Kotlin bindings restored after being paused during the API churn of earlier versions. The company paired the release with a support schedule for customers, hosted relays offered through iroh services, and an end date for free public relay support on legacy versions. The announcement reached the top of Hacker News with 1,398 points and 462 comments, and TechTimes covered the launch on 2026-06-16.
No ending yet — it is still running.
Background
On June 15, 2026, N0, Inc. shipped Iroh 1.0, the first stable release of its open-source Rust networking library. Iroh's claim is that applications should address devices by cryptographic key, not IP address: an endpoint generates an Ed25519 keypair, the public key becomes a stable EndpointID that survives network changes and doubles as the authentication and encryption anchor, and connections work from behind NAT through a mix of direct hole-punching and stateless relays.
The release capped more than four years of open development and 65 pre-release versions. The 1.0 line promises wire-protocol and API stability across languages and restores official Python, Node.js, Swift and Kotlin bindings that had been paused during earlier API churn. Under the hood iroh builds on IETF drafts for QUIC multipath and QUIC NAT traversal, supports local-first connections with no internet, and can compile to WebAssembly for browser use, with custom transports like Bluetooth Low Energy and Tor possible under the same key-based abstraction.
The adoption numbers make the bet concrete before the stable release: N0 reports more than 200 million endpoints created on its public relays in the 30 days before launch, with developers using iroh for video streaming, LLM training coordination, secure chat, file transfer and game networking. The announcement hit the top of Hacker News with 1,398 points and 462 comments, TechTimes covered it independently, and N0 positions hosted relays and support schedules as the commercial layer on top of the open-source library.
What has to be true
- IP addressing is genuinely broken for apps that span networks: addresses change, hide behind NAT and carry no identity, so a key-based primitive removes a whole class of connection and security bugs.
- The economics favor giving the library away: stateless relays are cheap to run, and with about 95% of data flowing directly between devices, hosted relays carry the revenue.
- Wire stability plus Python, Node.js, Swift and Kotlin bindings at 1.0 turns a library into a platform that mobile, IoT and distributed-AI teams can schedule roadmaps on.
- Open development built distribution in advance: 65 public versions and 200 million relay endpoints in 30 days meant real adoption happened before the stable launch was announced.
What can be applied
A protocol project earns trust by promising stability, not features: freezing the wire format and shipping language bindings at 1.0 lets outsiders plan roadmaps on your library.
Aftermath
As of September 2, 2026, iroh 1.0 is stable and in production: N0 reports the library on millions of devices, more than 200 million endpoints created on its public relays in the 30 days before launch, and production uses from distributed AI inference to point-of-sale connectivity. Public relay support for the older v0.35 line ends December 31, 2026, while hosted relays are sold through iroh services; whether key-based addressing becomes a default application-layer primitive is still open, but the stability bet has already been answered with production adoption.
Sources
spotted an error? The archive wants to know.
Your turn
You just read one. Describe what you are building, and see who is betting on the same thing.
Free account · 3 free questions · no card