Iroh
P2P networking library in Developer tools
An open-source, QUIC-based library for direct, encrypted peer-to-peer connections with hole punching and self-hostable relays; critics find its docs and marketing unclear about what it does.
89 people recommended Iroh in Hacker News comments, 19 had mixed feelings and 25 criticized it, November 2025 to October 2026.
58 of the 89 people who recommend it commented in one thread, “Iroh 1.0”.
Summary written by Claude from 53 comments. Claude agents reviewed it against the quotes on 2 Nov 2026.
133 people gave an opinion
- recommend it
- 89
- mixed feelings
- 19
- warn against or regret it
- 25
The record
Recommended in 9 of 12 months
In 23 different threads.
- November 2025: not recommended
- December 2025: not recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: not recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: recommended
Why it doesn’t carry the badge
- 89 people recommend itNeeds 10 or more, met.
- 3.6 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 9 of 12 monthsNeeds 4 or more, met.
- Recommended in 23 threadsNeeds 5 or more, met.
- 58 of its 89 recommenders came from one threadNeeds half or less, not met.
The same rules apply to every product, and the badge can’t be bought. Mixed feelings count toward neither side. How the badge works
What people say about it
Reasons grouped from a sample of 40 of the 192 opinions about it, picked in proportion to how many people recommend it, have mixed feelings and criticize it. Each mark is one comment in the sample. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Easy P2P connectivity across networks
“appears pretty good for "just get edge device / node connectivity to work" when you don't want end users to bother with networking shenanigans”
Comment from 25 Aug 2026 in “IPFS Maintainers Winding Down” “if you want to do anything with p2p in 2026 you’re going to hard pressed than to find a better option than Iroh”
Comment from 16 Jun 2026 in “Iroh 1.0” “For environments where you want people to access your local instance, I believe Iroh will be a game changer.”
Comment from 15 Jun 2026 in “Iroh 1.0” - Comment from 15 Jun 2026 in “Iroh 1.0”
- Comment from 16 Jun 2026 in “Iroh 1.0”
- Comment from 15 Jun 2026 in “Iroh 1.0”
Fully open source, self-hostable relays
“You can have elaborate Iroh-based projects entirely based on the OSS components without losing features and without paying anything.”
Comment from 16 Jun 2026 in “Iroh 1.0” “Iroh is free-to-use, permissively licensed, relays are self-hostable, and it's all fully open source for all necessary components.”
Comment from 16 Jun 2026 in “Iroh 1.0” “you could deploy pretty extensive Iroh-based software without ever having a financial relationship with number0”
Comment from 16 Jun 2026 in “Iroh 1.0” - Comment from 16 Jun 2026 in “Iroh 1.0”
- Comment from 15 Jun 2026 in “Iroh 1.0”
Built on QUIC and existing standards
“a creative way to leverage all the work the major cloud vendors have poured into QUIC for p2p connections”
Comment from 16 Jun 2026 in “Iroh 1.0” “we try to use existing IETF standards (QUIC, TLS) as much as possible instead of reinventing the wheel”
Comment from 15 Jun 2026 in “Iroh 1.0” “Iroh gets the benefit of having been designed and built from the ground up, based on quic.”
Comment from 15 Jun 2026 in “Iroh 1.0” - Comment from 15 Jun 2026 in “Iroh 1.0”
Small footprint for embedded devices
“If you work on native mobile apps or embedded devices, iroh will be better since it is pretty frugal.”
Comment from 15 Jun 2026 in “Iroh 1.0” “I like Iroh objective of keeping it's footprint small enough to run on low powered devices”
Comment from 16 Jun 2026 in “Iroh 1.0” “It's a demo of how easy it is to make even an ESP32 device available globally with iroh.”
Comment from 11 Jul 2026 in “An iroh powered smart fan”
What people warn about
Each mark is one comment
Docs and marketing don't explain it
“The current stuff about dialling is pretty incomprehensible, as shown by the many confused comments here.”
Comment from 16 Jun 2026 in “Iroh 1.0” “This page is basically useless in explaining what Iroh is or does and why I should care.”
Comment from 15 Jun 2026 in “Iroh 1.0” “From a marketing standpoint, for a technical audience, I think it should be quicker.”
Comment from 15 Jun 2026 in “Iroh 1.0” - Comment from 16 Jun 2026 in “Iroh 1.0”
- Comment from 19 Jun 2026 in “Iroh 1.0”
Unclear security implications
“This is great for simplicity, but having Stun Turn and Signaling live in the same server would make it harder to secure.”
Comment from 15 Jun 2026 in “Iroh 1.0” “I definitely see the value! But I'm not confident I can tell whether there are e.g., security implications”
Comment from 15 Jun 2026 in “Iroh 1.0” “there seems to be no mention of ddos mitigation or shorter routes due to infrastructure”
Comment from 15 Jun 2026 in “Iroh 1.0” Overlaps with Tailscale for many uses
“Looking at the use cases, right now I don't see anything that cannot be done with Tailscale”
Comment from 15 Jun 2026 in “Iroh 1.0” “it just moves the dependency from tailscale's relay servers to iroh's relay servers”
Comment from 21 Aug 2026 in “RustDesk now supports true unattended remote access on Wayland” Traffic relayed through their servers
“Last I checked this project also automatically forwards traffic through their servers when direct connections fail”
Comment from 5 Oct 2026 in “Self-hosted HTTP tunnels with SSH and Nginx”
What people said
40 of the 192 opinions about it, picked in proportion to the three counts, newest first. Each links to the original comment.
“you can do it all in iroh with one identity, the tunnel, the file transfer, the ssh access, and others”
“Last I checked this project also automatically forwards traffic through their servers when direct connections fail”
“so that you can have things like persistent cryptographic identities and addresses that you can carry with you”
“appears pretty good for "just get edge device / node connectivity to work" when you don't want end users to bother with networking shenanigans”
“We built an IPFS-like system for distributing files in the radicle ecosystem with Iroh and iroh-blobs”
“it just moves the dependency from tailscale's relay servers to iroh's relay servers”
“Iroh is probably one of the best shots we have at making IoT finally secure with the built-in endpoint-to-endpoint encryption”
“It's a demo of how easy it is to make even an ESP32 device available globally with iroh.”
“This just tells me that the marketing site doesn't explain what Iroh actually does.”
“You can have elaborate Iroh-based projects entirely based on the OSS components without losing features and without paying anything.”
“I like Iroh objective of keeping it's footprint small enough to run on low powered devices”
“if you want to do anything with p2p in 2026 you’re going to hard pressed than to find a better option than Iroh”
“it's what makes it usable everywhere: Rust, JavaScript (server or browser), Python, Kotlin, Swift, C”
“you could deploy pretty extensive Iroh-based software without ever having a financial relationship with number0”
“Iroh is free-to-use, permissively licensed, relays are self-hostable, and it's all fully open source for all necessary components.”
“The current stuff about dialling is pretty incomprehensible, as shown by the many confused comments here.”
“the project has a lot of appeal already, because it exactly and excellently fulfills a technological need”
“iroh is fully open source though, you can run your own relay server and not have any dependencies on number0”
“a creative way to leverage all the work the major cloud vendors have poured into QUIC for p2p connections”
“Very cool project. I seriously wish one of the printer vendors would use iroh to come up with a network printing standard that just works.”
“If you want to write an app which offers peer to peer connection for some feature, then use iroh.”
“This is great work, but the blog is too esoteric, likely written by the developers.”
“For environments where you want people to access your local instance, I believe Iroh will be a game changer.”
“From a marketing standpoint, for a technical audience, I think it should be quicker.”
“It's a cool idea and I would expect that they'll find a market, but I'm not sure this would be a breakthrough product for me”
“there seems to be no mention of ddos mitigation or shorter routes due to infrastructure”
“iroh connections are just as secure as the QUIC/TLS connections your browser makes to your banking app.”
“I definitely see the value! But I'm not confident I can tell whether there are e.g., security implications”
“If you work on native mobile apps or embedded devices, iroh will be better since it is pretty frugal.”
“This is great for simplicity, but having Stun Turn and Signaling live in the same server would make it harder to secure.”
“I am happy that more remote access products are using QUIC, not WireGuard, for tunneling”
“Iroh gets the benefit of having been designed and built from the ground up, based on quic.”
“an excellent building block for application developers to route around the segmentation”
“Looking at the use cases, right now I don't see anything that cannot be done with Tailscale”
“we try to use existing IETF standards (QUIC, TLS) as much as possible instead of reinventing the wheel”
“In most cases we can give you a direct connection between the two devices very quickly via hole punching”
“I don't understand the problem its trying to solve in the first place, IP works just fine, such as DNS.”
“designed from the ground up, to use existing internet technologies, while avoiding the lock in”
“This page is basically useless in explaining what Iroh is or does and why I should care.”
“I'm thinking of ways in which I can use their iroh library to help with some of the workloads at work”
Counts come from 1,791,911 Hacker News comments labeled by Claude, November 2025 to October 2026, with data through October 31, 2026. Counts updated 2 Nov 2026. How we count. Report a mistake.