Thanks! Talk about the stack? But that’ll reveal all my unpopular opinions and questionable choices. 
It’s running on nodejs, behind nginx, serving http2. The CMS is custom made (also Haxe.)
The frontend Haxe is being compiled with modular-js into small, single-class AMD modules (I think HTTP2 makes this a reasonable strategy.) It’s vanillaJS and some Riot v2 (ages old, but I like it and have tooling around it.) I have no appetite for “modern js”.
On the backend, I’m quite enjoying the jsasync macro to take advantage of native async / await. Thanks @basro !
I started the project playing with lix… But I still prefer just switching my haxe versions manually and storing 3rd party lib source directly into my repo.
My servers’ setups are all scripted, some services are dockerized. I have RTMP ingest servers in 6 countries with DNS-based location resolution:
(I should look for a host in South America, not available from my current hosts. 
)
Run ping live.polystreamer.com to see where it resolves for you:
>ping live.polystreamer.com
PING us-east.live.polystreamer.com ...
My legal docs are based on Automattic’s legalmattic repo - thanks for that. 
And the parrot icon truly came before all of the above - I thought @RobDangerous would appreciate that 
That’s about it - fun, fun! 
Best,
-Jeff