It enables you to expose a local web server to devices on different networks. Nothing to install on the consuming devices - just a web browser. And no server in the middle. It uses a Service Worker to intercept HTTP requests and WebRTC to tunnel requests/responses directly between consuming devices and the device running the local web server.

To use: install the web-p2p-tunnel CLI program which receives requests, reverse proxies them, and tunnels responses. See the README for details. The website is deployed using Github Pages at https://tunnel.andrewt.io/. Additionally, a signaling server is deployed at https://signal.andrewt.io/.

I've tested on a number of OSs and browsers and with simple static web sites and more complicated apps. A lot of it just works, but there are kinks and edge cases and almost certainly bugs. Let me know :) Currently, there are no TURN servers configured, so connections may fail under certain network conditions.

Motivation: I built some media features using WebRTC at my last job. It's a bit of a pain to use, but it's a powerful technology. On the media side of things, however, P2P quickly turns into more of a client-server situation w/ something like an SFU for common use cases. From my understanding, WebTransport might become the better technology for this use case. This got me thinking about use cases that would specifically benefit from the P2P aspect of WebRTC, which led me here. I was inspired in part by this project: https://github.com/rtctunnel/rtctunnel.

Excited to share the project - I think it could be a useful dev tool. Feedback appreciated!