bugout

No you don't, sort of don't. When you look at the Bugout [1] library, you see that they're using the infrastructure of WebTorrent to fix that. I emailed the author and he said he's working on a form of infrastructure in which the infrastructure takes care of this problem. So yea, you don't need a signaling server then. I'm pretty sure the extended version of this idea also includes STUN servers. And I think you'd always need to pay for TURN servers as the NAT is then simply disabling P2P all-together [2]. [1] https://github.com/chr15m/bugout [2] Context for people who are like what are all these terms? In WebRTC when you have 2 computers behind different corporate networks trying to connect they need to go through a router. A router performs Network Address Translation (NAT), the internal IP (usually 192.168.178.xxx, definitely not always

Note: there's no client-server architecture needed with things such as Figma since it can be done P2P. I'm just past the beginning stages of it. You can use a mix of WebRTC/WebTorrent's infrastructure to get a serverless (i.e. use WebTorrent's signaling services) for P2P. A library called Bugout [1] implemented it this way. If you want to see an example of how it works, check out my side project Doodledocs. I modified the Bugout library a bit for performance improvements, but my project is using its concept on how to spin up a serverless (i.e. not your servers but those of WebTorrent) P2P web app [2]. [1] https://github.com/chr15m/bugout [2] Doodledocs is a collaborative doodling web app that I created as a sideproject, so it is just a bit related to Figma. I didn't make CRDTs yet, since I want a simple doodle environment for pencil/erase