Turn connection anxiety into confidence
You chose p2p, it's deployed in production. But it's been some time, and now you have two problems:
You're flying blind.
No dashboard. No proof connections are healthy. You find out something's wrong when a user tells you.
When something breaks, blame is a maze.
Is it iroh? Your code? The user's network? Every incident is an investigation with no obvious starting point.
This is connection anxiety. We can help.
Two tools. One cure: confidence in production.
Tested everywhere you deploy
Every commit to iroh runs through simulations and tests across Windows, macOS, Linux, Android, iOS, and embedded targets.
Running on unusual hardware? Send us the device. We'll add it to our test lab and make sure iroh works on your target platform.
Connection anxiety thrives in silence.
iroh Enterprise means messaging the engineers who wrote the code. Your dedicated Slack or Discord channel connects you directly to the Number0 core team: the same people committing to iroh every day, triaging issues, and shipping features.
Dedicated private channel with the OSS team.
When you surface a bug or need a feature, it goes straight to the people with the power and the context to act fast.
Institutional knowledge, on demand.
Architectural decisions, edge cases, upgrade paths: the answers live in the team, not a knowledge base.
iroh is already running at scale
Hundreds of thousands of devices in production.
Video Streaming
Real-time video for millions of concurrent connections.
Read the case study →
Distributed AI Training
Train foundation LLMs across AWS, GCP, Azure, and self-hosted compute.
Read the case study →
Payments & Point of Sale
Tap-to-pay at highway toll booths with no additional servers.
Read the case study →
“Doubling the network speed halves our compute budget.”
— Ari Lotter, Principal Engineer, Nous Research
SLAs that cut through the anxiety
Measured from first contact. Delivered through your dedicated channel.
| Severity | Pro | Enterprise |
|---|---|---|
| Critical — system down, no workaround | Best effort | 4 hours |
| Standard — degraded, operations impacted | Best effort | 1 business day |
| Minor — limited impact, workaround exists | Best effort | 2 business days |
Tier comparison
| Service | Pro | Enterprise | Dedicated Engineer |
|---|---|---|---|
| Support tickets | |||
| SLAs | Best effort | ||
| Managed relays | Pay as you go | Custom | Custom |
| Dedicated private channel | |||
| Custom metrics & monitoring | |||
| Network diagnostics | |||
| Issue & feature prioritization | |||
| Early access to new features | |||
| Training sessions | |||
| Architectural guidance | |||
| Self-hosted relay guidance | |||
| Device testing | |||
| Code reviews | |||
| Custom feature development | |||
| Source code access & collaboration |
Why Number0
- We wrote iroh: no translation layer between your problem and the fix
- Dual MIT/Apache licensed — no lock-in risk
- A small, senior team: you talk to engineers, not a support queue