Iroh has reached version 1.0 after more than four years of open development, marking its first stable release and a compatibility commitment for applications built around key-addressed, peer-to-peer connections. The project uses cryptographic keys as durable endpoint addresses, an alternative to relying directly on IP addresses that can change or remain unreachable behind firewalls.
In Iroh’s model, the same key identifies an endpoint and secures its traffic. Because the address persists as a device moves between networks, an application can attempt to reach it without managing a fixed public IP. Connections are designed to traverse network boundaries and go directly between devices where possible, using relays when direct paths are unavailable. The maintainers say 95% of data in a typical connection travels directly, although the announcement does not provide the dataset behind that figure.
The 1.0 milestone covers both the wire protocol and language-facing APIs. Iroh says any version 1 endpoint will communicate with another version 1 endpoint regardless of the implementation language or minor release. A future language API could advance independently while retaining wire compatibility; any change that breaks the wire protocol will coincide with a major release. That promise gives developers a clearer upgrade boundary than the 65 pre-1.0 versions that preceded it.
Official support now extends beyond the Rust crate to Python, Node.js, Swift and Kotlin. Foreign-function interface work had previously been paused because rapid API changes imposed too much maintenance overhead. Restoring it with a stable interface allows the stack to be embedded in iOS and Android projects as well as server and desktop software. Documentation and generated API references accompany the bindings.
The maintainers describe uses including video streaming, large-model training, agent communication, secure messaging, games and file transfer. They also say public relays saw more than 200 million endpoints created in the preceding 30 days and that the technology runs on millions of devices. Those are project-reported activity figures, not counts of unique people or continuously active installations.
Iroh operates public relays through a commonly used `n0` preset and plans to update them shortly after releases, usually within 24 hours. Relay changes that would break older clients will receive new URLs. The relay software is open source, while the company also sells hosted relay service. Public relayed traffic is rate-limited, and those limits may change.
Version 1.0 therefore represents an interface and interoperability contract more than an end to development. Developers still need to test traversal behavior, relay dependency and performance in their own network conditions. The release makes that evaluation easier by fixing the protocol boundary and offering maintained bindings across the principal application platforms Iroh targets.
