IdeaWell

Project ideas from Hacker News discussions.

Show HN: BitBang – Reach machines behind NAT from a browser, no account

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

3 Prevalent Themes from the Discussion

# Theme Supporting Quote
1 Account‑less, identity‑based P2P via WebRTC “a device's identity is the hash of its public key, so browser and device verify each other directly. The server keeps no registry, authorizes nothing, and isn’t in the data path.” – narragansett
2 Self‑hostable, minimal relay that stays cheap “it’s open source and self‑hostable … since it’s out of the data path, cheap to run.” – narragansett
3 Practical trade‑off: reach vs. centralisation “It claims to be P2P, but it still needs to bootstrap the connection via central server. I think that always might be a limitation of P2P.” – tadasv

🚀 Project Ideas

BitBang Cloud Broker-as-a-Service

Summary

  • Provide an open‑source, Docker‑ready signaling server that brokers WebRTC connections without holding any keys or user data.
  • Core value: Enables any device or browser to expose a local service via a single URL, zero‑install, while remaining self‑hostable.

Details

Key Value
Target Audience DevOps engineers, hobbyist makers, and self‑hosting enthusiasts who need NAT‑piercing for remote access
Core Feature Stateless broker that only exchanges public‑key hashes and SDP; can be pointed at user‑provided TURN/STUN
Tech Stack Go, Docker, Prometheus, optional Redis for metrics
Difficulty Medium
Monetization Revenue-ready: $9/mo per active tunnel

Notes

  • Hacker News users praised the “phonebook not keyring” model and the ease of opening a link that instantly gives a terminal and file browser.
  • Potential for integration into tools like OctoPrint or Jellyfin to give remote UI without account creation.

BrowserZero Remote Shell Platform

Summary

  • A lightweight web app that lets users drag a generated link onto any device to instantly get a browser‑based terminal, file manager, and web‑app proxy.
  • Solves the friction of installing clients for remote access on borrowed laptops, phones, or temporary machines.

Details

Key Value
Target Audience End users wanting instant remote access, enterprise support staff, and educators
Core Feature Pure WebRTC‑based terminal and file browser that connects to a user’s local service without any server‑side credentials
Tech Stack TypeScript/React, Pion WebRTC (Go), Node.js signaling, WebFileSystem API
Difficulty Low
Monetization Hobby

Notes

  • Directly mirrors the enthusiasm in the HN thread for “no account, just a URL” and the desire to share a link with friends.
  • Could be packaged as an embeddable iframe for docs, forums, or support chats to provide live help.

TURNpool Community Relay Marketplace

Summary

  • A curated registry of low‑cost or free TURN servers that users can subscribe to, with automatic failover and bandwidth caps to stay within free tiers.
  • Addresses the bandwidth‑cost concern raised by HN commenters about relay usage.

Details

Key Value
Target Audience Small‑scale service hosts, hobbyist VPS operators, and developers using WebRTC tunnels
Core Feature API to discover and switch between vetted TURN endpoints, with usage metering and optional paid premium nodes
Tech Stack Python/Flask, PostgreSQL, Celery workers, Docker Swarm
Difficulty Medium
Monetization Revenue-ready: $2 per GB of relay traffic above free tier

Notes

  • HN participants asked for a list of reliable free TURN providers and worried about bandwidth caps; this marketplace solves that.
  • Could be promoted as a “one‑click” add‑on for BitBang or similar projects, creating network effects.

Read Later