Own Iroh.

What you'd own.

Every artifact below transfers to your accounts on day one. The whole engine.

• ●Iroh brand identity and community reputation across GitHub and Discord
• ●Open-source codebase, protocol specification, and technical documentation
• ●Documented GTM playbook: free tier to paid relay SLA conversion
• ●Founder relationships and mindshare within decentralized app developer circles
• ●TAM analysis segmenting 18k active decentralized app development teams
• ●Financial model and pricing strategy for managed relay tiers
• ●Customer success playbook for converting self-hosters to managed tier

What Roll Digital builds for you.

Custom scope to take Iroh from MVP shell to operating business.

• ▸Production-grade managed relay infrastructure with guaranteed uptime SLA monitoring
• ▸Subscription billing system for three-tier pricing ($99, $299, $499 monthly)
• ▸Developer dashboard showing relay usage, performance metrics, and cost breakdown
• ▸Multi-team access control, API key management, and usage-based limits
• ▸Migration guide and tooling for converting self-hosters to managed relay
• ▸Automated deployment and failover across multiple geographic regions
• ▸Onboarding flow and email sequence targeting GitHub stargazers and Discord members
• ▸Exhaustive relay performance logging and customer success analytics

Why this could work.

TAM of 18k actively building decentralized teams creates genuine demand. Free tier drives frictionless adoption while paid SLA unlocks revenue from teams hitting nat traversal pain at scale. OSS-first approach builds trust competitors can't replicate. Relay infrastructure becomes strategically critical once applications leave hobby phase. Community funnel is already warm with engaged developers.

What you'd risk.

Self-hosting cannibalizes paid tier: developers who love Iroh run private relay nodes rather than pay. Intense competition from libp2p, WebRTC, and free cloud tiers already winning serious distributed systems engineers. Target market is chronically underfunded: web3 startups burn fast, indie hackers watch budgets. Even with strong product, conversion to paid will likely remain very low. Year 1 projects a loss, requiring patience on profitability.

Who this fits.

Existing B2B SaaS operator with technical credibility in infrastructure or distributed systems. Someone who has monetized developer tools before and understands low year-one revenue runways. Requires patience and deep technical involvement during year one. Not a fit for operators seeking quick exits. Best owned by a solo founder or small team comfortable sustaining losses while building community trust into paid adoption.

Timeline.

From contract signing to operating business.

1. Day 1
   Brand, codebase, community, GTM playbook transfer complete
2. Week 1
   Assess infrastructure needs and prioritize production MVP features
3. Week 3
   Managed relay deployed to staging with basic monitoring
4. Week 6
   Billing live, first 3-5 beta customers onboarded
5. Day 90
   SLA monitoring live, paid tier ramped to 8-12 customers

Pricing.

Three ways in, depending on how much you want to build yourself.