OpenVidu Enterprise



OpenVidu Enterprise is currently in beta. As long as it remains in beta:
  • It is completely free of charge. You can try it for free.
  • There are some known limitations.
  • There may be unexpected bugs.
NOTE: When the beta period officially ends, you will no longer be able to use your OpenVidu Enterprise beta deployment. Any deployment of OpenVidu Enterprise beta (releases 2.19.0 and 2.20.0 for now) will automatically stop working. A final release version of OpenVidu Enterprise edition will be available for you to deploy before this happens. We will notify through all our official channels when the moment comes.
OpenVidu
CE
OpenVidu
PRO
OpenVidu
ENTERPRISE
WebRTC media streams
Recording
Screen sharing
Audio and video filters
IP cameras
Clients: JS, Angular, React, Vue.js, Ionic, Electron
Deployment on Premises
Deployment on Cloud
OpenVidu Inspector
Advanced session monitoring
Manual scalability
Elasticity
S3 recording storage
Network quality API
Fault Tolerance
Media Server Kurento Kurento Kurento / mediasoup
Simulcast and SVC
High Availability
VP9
Large scale sessions
E2E encryption
License Apache 2.0 Commercial Commercial
Support Community support on forums Email support in business hours Email support in business hours
Price Free 0.0006$ core/minute
Free while in beta
0.0012$ core/minute
Docs Docs Docs

OpenVidu Enterprise features 🔗

OpenVidu Enterprise offers the best performance, improved media quality and better scalability for high-demand environments.

The key feature of OpenVidu Enterprise is that it supports using mediasoup as Media Server instead of Kurento. mediasoup brings a lot of benefits for videoconferencing apps built with OpenVidu:

6x more media streams 🔗

Using the same hardware, OpenVidu Enterprise with mediasoup supports up to 6 times more media streams than with Kurento.

5x quicker connections 🔗

Media connections are established 80% quicker using OpenVidu Enterprise with mediasoup. This means that with Kurento the average time between a customer calling the subscription operation and the video being actually played on their device, it could average around 1.25 seconds. With mediasoup it averages 0.25 seconds.

Media quality improvements 🔗

OpenVidu Enterprise with mediasoup raises the bar of what is possible with adaptive video quality for WebRTC, compared to what was possible with Kurento:

  • Simulcast

    Simulcast is a technique that allows optimizing the quality of routed video, in accordance with the needs of each individual Subscriber. Depending on aspects such as device form-factor or network link quality, the video that gets delivered to each participant in a session can be adjusted to be the perfect match for each circumstance.

    This comes in contrast with the more traditional method of adaptive video bitrate in Kurento, which was all-or-nothing and affected all participants equally, so it wasn't possible to adjust the quality individually for each one of them.

    For more technical details about how simulcast works, check the Simulcast technical details page.

  • VP9 (not available yet, work in progress)

    An advanced video codec that brings better quality features when compared to VP8 and H264.

    VP9 achieves better compression rates and better quality with lower bandwidth usage. It also supports SVC, which is in itself an improvement over the benefits provided by Simulcast.

    Popular web browsers such as Google Chrome have integrated VP9 support for a while now, other browsers are slowly getting onboard, and OpenVidu will allow you to benefit from it too.

100% compatible with your current OpenVidu applications 🔗

OpenVidu hides all complexity that lies behind swapping Media Server technologies: New SDKs, architecture changes, etc...

With OpenVidu, there's no need to change a single line of your application: what used to work with OpenVidu Pro will work as-is with OpenVidu Enterprise.

High Availability deployment option 🔗

OpenVidu Enterprise offers a High Availability deployment option in AWS, with replication of all nodes and load balancing for clients. Visit the High Availability documentation for further information.



OpenVidu Enterprise roadmap 🔗

Large scale sessions 🔗

OpenVidu Enterprise will support much larger sessions in terms of users and streams. This is a statement based on 3 points:

  • The better performance of mediasoup allows processing more media streams in the same hardware.
  • Sessions will be able to be replicated in different Media Nodes, sharing the load of the same session in different machines. This will provide horizontal scaling in OpenVidu for the first time.
  • Selection of dominant speaker(s) will add the possibility of sessions with hundreds or thousands of publishers without crashing client devices. Only the latest active speakers in a session will be sent to the client side, theoretically allowing for an unlimited number of publishers in the same session.

E2E encryption 🔗

Thanks to mediasoup, OpenVidu Enterprise will offer E2E encryption using WebRTC Insertable Streams. With Kurento, media streams are encrypted in the client-to-server and server-to-client channels, protecting them from man-in-the-middle attacks. But media streams have to be individually decoded and processed in the server side, so data must be decrypted by Kurento, which breaks the client-to-client encryption. But with mediasoup, media streams can remain protected client-to-client, without the server needing to decrypt it.



OpenVidu Enterprise beta limitations 🔗

As a beta feature, mediasoup support in OpenVidu and High Availability deployments comes with a handful of limitations that will be solved in the near future, when it finally reaches the General Availability stage. These are:



Enable OpenVidu Enterprise 🔗

OpenVidu Enterprise is very easy to enable. While in beta, you just need an OpenVidu Pro cluster up and running.

Configure the following property in the .env file at Master Node installation path (default to /opt/openvidu/)

OPENVIDU_EDITION=enterprise

Then restart the services running command ./openvidu restart in the same installation path.

NOTE: When the beta period officially ends, you will no longer be able to use your OpenVidu Enterprise beta deployment. Any deployment of OpenVidu Enterprise beta (releases 2.19.0 and 2.20.0 for now) will automatically stop working. A final release version of OpenVidu Enterprise edition will be available for you to deploy before this happens. We will notify through all our official channels when the moment comes.