Efficient IPFS for the whole world right now.
Iroh takes IPFS beyond the theoretical, to offer developers efficient infrastructure that scales data distribution past 10M devices.
Run Iroh Now01
Purpose-built for efficiency.
We have been working on and around IPFS nearly since it's inception, and are starting out on a new implementation because we have unfinished business with IPFS.
We believe the best days of the protocol are ahead, but to get there we need to ship an order-of-magnitude improvement that unlocks new platforms and use cases.
We're building iroh to see just how far we can take IPFS.
Faster
Iroh consistently outperforms Kubo, using fewer resources to serve more requests.
There is a ring of truth to the "rewrite it in Rust" cliché. Adding in lessons learned while working with IPFS over the years doesn't hurt either.
Throughput
Adding Content
Practical
Iroh does fewer things than kubo, with more polish. Iroh targets a subset of the kubo API, aiming at the most commonly-used features of IPFS, while steering users away from pitfalls that have been trapped in kubo to maintain backward compatibility.
If it's shipped in iroh, it will just work.
Platform Specific
Running a single binary in the cloud doesn't make much sense. Neither does duplicating files locally when running IPFS on the desktop
Iroh is a single codebase with multiple platform targets, allowing iroh to be microservices in the cloud, use more natural defaults on desktop.
Mobile Support
Finally, IPFS on a phone.
Iroh can be embedded into iOS & Android applications to speak the IPFS protocol natively. It's not a device-overheating afterthought, it's a ground-up rethink of what IPFS on a phone should look like.