Steven – you could, but there are other ways. Jitsi also takes care of part of the challenges and not all of them, so there’s additional work to be done on top of it.

Also remember that Twilio needs to work at scales that others can ignore at their initial launch.

Couldn’t you run it through Jitsi?

Gustavo, thanks.
At the time of writing, they were the first ones.
It was bound to be a temporary differentiator.

Different WebRTC PaaS vendors use different approaches to pricing models. My report covers these aspects: https://bloggeek.me/webrtc-paas-report/

If their service doesn’t delivers, then it isn’t interesting. It probably does though…

As for large scale conferences – they don’t deal with it. They indicate the service scales – not that a single session scales. For now, as far as I understand, multiparty video calls are mesh based.

Do agree with Andy that we can’t overstate the importance of the Twilio developer ecosystem. This means immediate impact for WebRTC, regardless of how the Twilio platform compares to Tokbox and others.

I am most curious on how Twilio handles large scale conference use cases. Those use cases represent a serious investment in media and session management competencies that Twilio doesn’t have much of in house today. Is that use case worth building internal support for? Or perhaps Twilio is better off partnering, offering northbound APIs to providers that can specialize in those competencies?

Andy,

That’s true. Goes without saying, which is probably why I forgot about it…

Twilio has the developers. Devs trust them. That’s their strength.

Andy