few questions regarding evostream capabilities

i’d like to ask you if evostream is capable of supporting a custom broadcasting system like this: 1. there can be multiple concurrent presenters each with their own audience. 2. the presenter uses a WebRTC-compatible browser to create a WebRTC session to the evostream server as a stream source. the stream is supposed to be 720p@25fps, VP8/VP9 WebM. 3. evostream server should create a H.264 version of this stream and serve it via HLS (or any other way that allows embedding via a tag). if possible, the original stream should be transcoded to a 720p@25fps H264 and a 480p/320p@25fps H264 stream and then serve these as the basis for the HLS/other method. 4. access to the HLS/other method streams should be restricted via a dynamic user base. 5. source streams may come and go dynamically, so there is no set source/destination matrix; everything is done on the fly. 6. the original or the 720p H264 transcoded stream should be recorded. 7. occasionally, two-way streaming (from audience to presenter, via WebRTC) should be necessary, if possible. questions: – can evostream support this scenario? – are there any caveats? – is WebRTC routing (see point 7) supported or would it be better handled by a Kurento instance? if so, can Kurento act as a stream source for evostream (via a mediapipeline that has a WebRTC endpoint as source and an RTPEndpoint as a sink)? – are there any limitations regarding CPU core count, number of incoming and outgoing streams?