Why we're upgrading iroh's networking engine
The road to iroh 1.0
It is done. After four years of work and various pivots we have released iroh 1.0.
FOSDEM 2026 - iroh p2p connections
iroh is a library to establish direct connections between two peers, wherever they are on the internet. It takes care of using different transports and holepunching as needed, to reliably establish connectivity. To the application a normal QUIC connection is presented. The aim is to be a connection layer for p2p, providing greater user agency.
TIL: Iroh: peer-to-peer networking for app developers
I came across Iroh (via, via) today as it hit 1.0 and found it a really interesting solution to a problem I knew existed but had not thought a lot about. Judging from the comment sections, it seems pretty clear that lots of people are confused as to exactly what Iroh is. I don’t think their launch post does their product justice at all, and their tagline is “IP addresses break, dial keys instead” which sounds cool, but if you think about it for just a second, you’ll end up with lots of questions. The biggest one is: “so how is this different from a mesh VPN like Tailscale, ZeroTier, Netbird, etc.?” It’s only after reading a lot of developers’ comments on the threads that I feel I understand: Iroh is aimed at application developers who want to communicate P2P between machines running their app, while mesh networks are aimed at network admins who want to connect devices they own/manage together.
NAT traversal and hole punching: from UDP to QUIC with iroh
How hole punching works, why TCP and plain UDP fall short, and how QUIC and iroh make direct P2P connections reliable.
Deep dive into iroh: A replacement for WireGuard or a P2P layer for your application?
Just last week, the iroh project announced the release of its v1.0. What is iroh? Well, I'm glad you're asking because it's a very interesting project that I'm following for
iroh 1.0
