WebRTC: Buyers Beware

12 Aug 2014

If there's anything that should make you sleepless at night when deciding on your WebRTC communications architecture it is the vendors you selected to rely on.

If you look at the acquisitions in the WebRTC ecosystem, you will notice some interesting ones:

Three out of five left customers "happy;" AddLive probably caused vibrations at the management of the customers who decided to use it, and GoInstant made it to the last page of our newspaper.

This creates a buyers beware market, where those in search of an API vendor to use need to think twice (or more) before deciding who to work with.

This becomes even harder if you check the general stability of most WebRTC API Platform vendors - most of them are still startups, with fewer than 50 employees; sometimes a lot less. Each with its own first, second or third round of fund raising activities - some might not make it to 2015 and run dry.

The other side of the story has SnapChat and its ilk - companies that are looking to add real time communications to whatever large service they already have, and then to control and own the technology - they are fine buying it outright and taking it off market. To some extent, this has also been the end result of Crocodile RCS - Acision started as a customer and ended up as a full owner.

WebRTC isn't the only such technology. The space of BaaS and Big Data are also in consolidation:

This transient market state is going to stay with us for a while.

What should a customer do?

  1. Select a suitable platform and hope for the best
  2. Select the elephant in the room (TokBox or Twilio most probably), even if they aren't the best fit for the situation
  3. Invest heavily on its own infrastructure
  4. Buy one of the smaller players and take them off-market

No easy options here.

Comments

There are currently no comments on this article.

You must be a registered user to make comments