The WebRTC Landscape Infographic – March 2014

WebRTC Landscape Infographic 2014-03

A month after I had the idea, I am happy to post the first version of the WebRTC Landscape for March, 2014. The idea behind this infographic is to show all the companies currently using or supporting WebRTC technology. I know this can’t be complete, as the companies in this space are entering and expanding faster than I can personally keep track. I hope to add and morph this over time and will try and publish one of these every quarter or sooner if needed. If you see something you think needs fixing, please comment below or send me an email via the contact form on this site. I owe a debt to Scott Brinker at ChiefMartech.com where you can see his 3rd generation marketing technology landscape here.

A few rules and explanations:

  • The most a company can appear is three times. If you send me feedback, please take this into consideration.
  • I am using company names and not product names until the space gets a little more mature.
  • The company has to have a product that is clearly released and for sale to the public (not showing any technical demos, proof of concepts or alpha products)
  • I have visited every company site, and done my best to categorize the companies, but there are a lot of companies with nothing but marketing messages.
  • Here are the descriptions of the categories:
    • WebRTC Platforms: API Hosted platform for communications based on WebRTC and augmentation
    • Comms API Platforms: API Hosted platform for general communications (might have WebRTC, but conceived originally as a general comms platform)
    • General/WebRTC SDK: Software development kit for communications and web enablement.
    • Mobile WebRTC SDK: Software development kit for mobile enablement.
    • Browsers: Browsers that support WebRTC.
    • STUN/TURN/ICE: WebRTC security servers and technologies.
    • Browser Plugins: Plugins that allow WebRTC to work in non-webrtc compliant browsers.
    • Telco Gateway: Software/hardware solutions that allow WebRTC connections to traditional telecommunications protocols (mostly SIP). May break this category further in the future.
    • Media Gateway: Software/hardware solutions that allow media serving in WebRTC context.
    • WebRTC UC: WebRTC services or products focused on Unified Commnuications
    • WebRTC Video: WebRTC services or products focused on video collaboration
    • WebRTC Messaging: WebRTC services or products focused on messaging
    • PBX Support/Emulation: WebRTC enabled solutions that replace PBX functions (like Asterik)
    • Call Center/CRM: Vertical solutions that use WebRTC to help with call center and CRM functions
    • Vertical Applications: Specific Enterprise and Consumer Applications using WebRTC

Appreciate the help I received on this from my good friend Cynthia Artin who did a lot of the research.  Also a big shout out to Dean Bubley who looked at it when we met last week and gave me a few ideas (like including a Browser category – duh!)

EDIT March 10th: I got some great feedback from Dean Bubley and Tsahi Levent-Levi that many companies were missing (Dean says he follows 200 and Tsahi 350+ and this is around 75 companies). Tsahi even put up this post about how he finds companies to follow.  I have edited the criteria above to make it clearer how I picked which companies (ie. they had to have a real current product offering released). I have received smaller feedback on several items and companies to add. Keep it coming! I will endeavor to put out a new version before Enterprise Connect!

Share & Enjoy!

  • iagosoto

    Hi Brad,
    It’s difficult to find the right box for our Sippo WebRTC Application Controller, as it’s not a WebRTC gateway :) . In fact, we always work with third-party WebRTC gateways for signalling and media relay.
    Sippo WAC is the webserver you are going to use to download you WebRTC applications, that could be our Sippo WebCollaborator, Click to Call or any developed using our enhanced orca.js-based API. In addition, it includes an abstraction layer to support different signalling protocols (even use different signaling protocols within the same application) to make applications work with any vendor or architecture. This abstraction layer also hides the complexity behind the different implementation of webRTC by webbrowsers. Finally, it includes a service API and some connectors to manage AAA, user provisioning and contextual information from/to existing telco services (HSS, OSS, BSS, etc)
    Congrats for the infographic. It looks great !!
    Regards,

  • http://www.cio2cmo.com/ Brad Bush

    I will try and find a better place for Sippo. Lots of feedback that I need to incorporate. Will try and have a new version out soon!

  • http://www.telestax.com/ Jean Deruelle

    Hi Brad,

    Great work on infographics of the WebRTC landscape and thanks for mentioning TeleStax !
    To provide a more accurate picture, TeleStax also provides the RestComm platform http://www.telestax.com/restcomm/ which is a Communications API Platform (compatible with Twilio APIs) which does integrate a WebRTC API and Web SDK as well.

    Thanks
    Regards
    Jean Deruelle

  • http://www.scoop.it/t/telecom-apis Luis Borges Quina

    Hi Brad ! Great job putting together this infographic. Apidaze.io belongs to WebRTC APIs but comes originally from the Comms APIs Platforms. Tsahi will agree for sure :-)

    • http://www.cio2cmo.com/ Brad Bush

      I am trying to only have companies in one or the other – see definition above. Should I move you over?

      • http://www.scoop.it/t/telecom-apis Luis Borges Quina

        Hi Brad. I would rather compare us to Plivo (which is both in Comms API and WebRTC SDK). Our WebRTC SDK is probably more evolved than theirs and our Comms API quite comparable. If you can’t put us on both then it’s fin just fine to leave us where you put us :) Thanks

  • Sacha Gera

    nicely done – very informative

  • Lou Chiorazzi

    Hi Brad, nice infographic. I think you may be missing a logo on your infographic. Pexip Infinity Platform is the most powerful webRTC and truly distributable platform, interoperable, easy to use, with powerful APIs. If you are updating at any point, would you consider taking a look. I’m happy to provide some insight.

  • http://www.cio2cmo.com/ Brad Bush

    I have decided not to keep this updated. See this post:
    http://www.cio2cmo.com/webrtc-landscape-passing-baton/