Guest on The Bold Inventors Podcast
A technical, plain-language discussion of FrogNet — the Private Internet — and why privacy failures on the public Internet are structural, not accidental.
Two ways I can help you
Do you need help surviving today’s problems —
or building tomorrow’s infrastructure?
If you’re responsible for a system that can’t quietly fail, start with Consulting. If you want a viable alternative to the public Internet for privacy and resilience, go straight to FrogNet — the Private Internet.
Fix the systems you’re on the hook for today.
Architecture, AI, networking, radios, and infrastructure that actually has to work. I help you diagnose fragile systems, simplify what’s overgrown, and design something you can trust under real constraints.
Privacy by architecture, not policy.
FrogNet is a Private Internet you own: local-first naming, resilient routing, controlled convergence, and optional wide-area links — designed to keep working when WAN is broken, RF is ugly, or cloud dependencies disappear.
The book behind the Private Internet.
The technical-origin story of FrogNet — how refusing to guess, refusing to hide failure, and insisting on local truth led to a new networking fabric: the Private Internet.
Why “Private Internet” matters
The public Internet must expose routing and traffic “envelope” information to function, which means metadata is observable by design. FrogNet avoids that exposure by operating as a membership-based Private Internet with local authority and controlled interoperability.