[drivebyacct2]

Signaling isn't really that hard, and I say that as someone who wrote a signaling and chat server for webrtc. Fortunately, the chat server is no longer necessary and that functionality can ride on webrtc itself. (And I assume you didn't write your own STUN server and are just hosting/running an existing one.)

Do you run a TURN server?

[bstrong]

Not sure what to say about signaling other than handling all the edge cases takes a non-trivial amount of effort and testing (which is true of most things in software).

Chat is only possible peer-to-peer if you don't care about histories. Since losing your history every time you reload a page or close a tab isn't a great experience, it's helpful to have a server in the middle keeping the history, unread counts, etc (which we do support today). Presence will always require a server.

We do run relay and STUN servers in locations around the world. Our STUN server is based on an open source implementation, but it is substantially customized. The relay server is our own.