OpenVidu Editions
OpenVidu
CE |
OpenVidu
PRO |
OpenVidu
ENTERPRISE |
||
---|---|---|---|---|
WebRTC media streams | ||||
Recording | ||||
Screen sharing | ||||
Audio and video filters | ||||
IP cameras | ||||
Clients: JS, Angular, React, Vue, Ionic, Electron, React Native, Android | ||||
Deployment on Premises | ||||
Deployment on Cloud | ||||
OpenVidu Inspector | ||||
Advanced session monitoring | ||||
Manual scalability | ||||
Elasticity | ||||
S3 recording storage | ||||
Network quality API | ||||
Virtual Background | ||||
Speech To Text | ||||
Broadcasting | ||||
Fault Tolerance | ||||
Media Server | Kurento | Kurento | Kurento / mediasoup | |
Streams per core | 100 | 100 | 500 | |
High Availability | ||||
Simulcast | ||||
VP9 | ||||
E2E encryption | ||||
Large scale sessions | ||||
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 |
0.0018$ core/minute |
|
Docs | Docs | Docs |
OpenVidu
OpenVidu
OpenVidu
OpenVidu
Every minute of an OpenVidu cluster is charged based on how many CPU cores are available for your cluster in total. Therefore, the unit to charge is cores per minute, and the unit price is:
Taking into account the following information:
As explained above, every minute of an OpenVidu Pro / Enterprise cluster is charged according to the number of cores
available for the cluster. So let's see some actual examples, first noting the following points:
We are fine running this cluster configuration during 8 hours. But suddenly we see a peak in the demand, so we add 2 new Media Nodes to the cluster in 8-core servers to attend the demand (see Scalability).
This high usage level lasts for 8 hours, and then we are fine reducing the cluster size to its initial state. So the last 8 hours of the day we would be running again just a single Media Node in a 4-core server. The price for the full day would be:
This table summarizes all of the examples above. It shows:
(*) See the scenario here
That being said, there is no single answer to this question. The load each Media Node can handle depends on many factors:
You will need to perform some tests for your specific use case, and adapt the size of your cluster accordingly. OpenVidu team can perform these tests for you as part of their commercial services (contact us through Commercial page to ask for an estimate). For a quick reference, you can explore the pricing examples above and calculate the expected number of users your cluster will be able to handle. Simply divide the number of simultaneous media streams supported by each cluster between the number of media streams each one of your users will require in your application. For example:
To overcome this bottleneck in the Master Node, OpenVidu Enterprise offers a High Availability deployment option with replication of Master Nodes. You can check it out here: High Availability.
When purchasing an OpenVidu License, you will have to indicate your billing address and a credit card. You will receive a 15-day free trial period during which you will not be charged at all.
After the free trial period, a monthly billing cycle will charge all your expenses to your credit card. Therefore, you will receive an invoice each month. You can review your upcoming expenses and your past invoices in your OpenVidu account page. And don't worry: we don't store any credit card data. The entire billing process is securely done via Stripe.
OpenVidu Pro/Enterprise clusters will automatically report their usage on a recurring basis. That's why they need Internet access at all times. You won't be able to run your OpenVidu Pro/Enterprise cluster unless your Master Node has Internet access (see OpenVidu Pro architecture). If your specific use case doesn't allow your cluster to have Internet access, please contact us through Commercial page.
In OpenVidu Pro/Enterprise the price per minute only counts the Media Nodes actually connected to the cluster. Your OpenVidu License won't be charged for Media Nodes that are disconnected from the cluster even if they are turned on. Media Nodes are always disconnected from the cluster when dropped. If you then want to actually shut down the physical machine, you will have to listen to mediaNodeStatusChanged event until the Media Node reaches
CE
has an unrestricted Apache 2 open source license. You can deploy it anywhere (in a cloud
provider or on premises) and make modifications on your own to adapt the software to your
needs. It is COMPLETELY FREE.OpenVidu
PRO
is the middle-range commercial version of
OpenVidu with advanced features like scalability, elasticity, monitoring and
much more. Take a look to the table of features above to compare with other OpenVidu editions.
You can build an application using OpenVidu CE and, if you need it, you can purchase an OpenVidu
Pro license and start using it without any change in your code.OpenVidu
ENTERPRISE
is the higher-end commercial version of
OpenVidu, bringing the best performance, improved media quality, better scalability and high availability for enterprise environments.
Take a look to the table of features above to compare with other OpenVidu editions.
Any application built for OpenVidu CE or OpenVidu Pro is compatible with OpenVidu Enterprise.
Any application built for OpenVidu CE is compatible with
OpenVidu Pro and OpenVidu Enterprise.
Any application built for OpenVidu Pro is compatible with OpenVidu Enterprise.
Any application built for OpenVidu Pro is compatible with OpenVidu Enterprise.
OpenVidu Pricing
PRO
and OpenVidu
ENTERPRISE
are deployed as a cluster following a Master-Worker model or as unique nodes.
Below are some examples of OpenVidu clusters.
OpenVidu Pro cluster with 1 Master Node and 3 Media Nodes
OpenVidu Enterprise cluster with 1 Master Node and 3 Media Nodes
OpenVidu Enterprise cluster with 2 Master Nodes and 3 Media Nodes
Openvidu Enterprise cluster with 3 Nodes
$0.0006
per core per minute available for your OpenVidu
PRO
cluster$0.0018
per core per minute available for your OpenVidu
ENTERPRISE
cluster- You only pay for your OpenVidu cluster(s) for the time they are running. Usage will be registered the moment you start your cluster and will stop as soon as you shut your cluster down. When turned on, your cluster will be charged even in idle state (without active OpenVidu sessions).
- You pay for every available core at any given time: if you cluster grows for one hour, that hour you will pay more. If your cluster decreases the next hour, next hour will be cheaper. Master Nodes and Media Nodes have the same core per minute price.
- Your cluster (specifically your Master Nodes) needs Internet access at all times. If your specific use case doesn't allow your cluster to have Internet access, please contact us through Commercial page.
These prices only include the cost of an OpenVidu commercial license. If you are deploying your
OpenVidu Pro/Enterprise cluster in a cloud provider, you must take into account the
cost of the cloud resources you will be consuming (basically servers and bandwidth)
There is a 15-day free trial period waiting for you!
Pricing Examples
- The examples represent a continuous usage of the cluster, but remember that you can shut it down whenever you are not using it and that you can drop nodes to save resources.
- Each example shows in a table the price for 8 hours, 1 day and 1 month of continuous usage, as well as the approximated amount of media streams and sessions of 5 participants the cluster would support. This is done to provide a basic insight into the capacity of each cluster. These 5:5 sessions assume 25 media streams in total for each one of them (1 publisher and 4 subscribers per participant), with no recording and no screen-sharing.
- In every example mediasoup is assumed for Enterprise edition.
Cluster with 6 cores in total
Let's suppose we have our Master Node running in a 2-core server and a single Media Node running in a 4-core server. This topology should be enough for many use cases that do not expect tons of media streams established at the same time.
PRO |
ENTERPRISE |
|
---|---|---|
Number of media streams | 400 | 2000 |
Number of sessions with 5 participants | 16 | 80 |
8 hours | $1.73 | $5.18 |
24 hours (1 day of uninterrupted use) | $5.18 | $15.55 |
720 hours (1 month of uninterrupted use) | $155.52 | $466.56 |
Cluster with 10 cores in total
If we have our Master Node running in a 2-core server and 2 Media Nodes running in 4-core servers, prices will be the following ones.
PRO |
ENTERPRISE |
|
---|---|---|
Number of media streams | 800 | 4000 |
Number of sessions with 5 participants | 32 | 160 |
8 hours | $2.88 | $8.64 |
24 hours (1 day of uninterrupted use) | $8.64 | $25.92 |
720 hours (1 month of uninterrupted use) | $259.2 | $777.6 |
Cluster with 18 cores in total
Let's suppose we have our Master Node running in a 2-core server and 2 Media Nodes running in 8-core servers. This cluster is pretty powerful and should be able to handle a considerable amount of users.
PRO |
ENTERPRISE |
|
---|---|---|
Number of media streams | 1600 | 8000 |
Number of sessions with 5 participants | 64 | 320 |
8 hours | $5.18 | $15.55 |
24 hours (1 day of uninterrupted use) | $15.55 | $46.66 |
720 hours (1 month of uninterrupted use) | $466.56 | $1399.68 |
OpenVidu Enterprise HA cluster (AWS) with 12 cores in total
OpenVidu Enterprise HA (High Availability) provides Master Node replication. This ensures load balancing for clients and advanced fault tolerance, getting rid of any single point of failure.
ENTERPRISE |
|
---|---|
Number of media streams | 4000 |
Number of sessions with 5 participants | 160 |
8 hours | $10.37 |
24 hours (1 day of uninterrupted use) | $31.10 |
720 hours (1 month of uninterrupted use) | $933.12 |
OpenVidu Enterprise HA cluster (On premises) with 16 cores in total
OpenVidu Enterprise HA On-Premises offers a robust solution for deploying the High Availability version of OpenVidu on your own infrastructure. The architecture of the system is simplified by merging Master Nodes and Media Nodes into one, facilitating an easier setup and scaling process. This single node setup ensures load balancing, advanced fault tolerance, and eliminates any single points of failure, enhancing system reliability and uptime.
ENTERPRISE |
|
---|---|
Number of media streams | 8000 |
Number of sessions with 5 participants | 320 |
8 hours | $13.82 |
24 hours (1 day of uninterrupted use) | $41.47 |
720 hours (1 month of uninterrupted use) | $1244.16 |
Cluster with a variable number of cores
This use case takes advantage of OpenVidu scalability features. Let's suppose we deploy a cluster with the Master Node running in a 2-core server and a single Media Node running in a 4-core server.We are fine running this cluster configuration during 8 hours. But suddenly we see a peak in the demand, so we add 2 new Media Nodes to the cluster in 8-core servers to attend the demand (see Scalability).
This high usage level lasts for 8 hours, and then we are fine reducing the cluster size to its initial state. So the last 8 hours of the day we would be running again just a single Media Node in a 4-core server. The price for the full day would be:
PRO |
ENTERPRISE |
||
---|---|---|---|
First 8 hours wit low demand (6 cores) | Price | $1.73 | $5.18 |
Media streams | 400 | 2000 | |
Sessions with 5 participants | 16 | 80 | |
Next 8 hours with high demand (22 cores) | Price | $6.33 | $19.00 |
Media streams | 2000 | 10000 | |
Sessions with 5 participants | 80 | 400 | |
Last 8 hours with low demand (6 cores) | Price | $1.73 | $5.18 |
Media streams | 400 | 2000 | |
Sessions with 5 participants | 16 | 80 | |
Total at the end of the day | $9.79 | $29.36 | |
Total after a month | $293.7 | $881.1 |
This table summarizes all of the examples above. It shows:
- The approximated maximum number of simultaneous media streams and 5:5 sessions supported by the cluster, based on the number of Media Node cores. This numbers assume no recording, no screen-sharing and using mediasoup for Enterprise edition.
- The price for each configuration, based on the total number of cores and the running time.
6 cores | 10 cores | 18 cores | 12 cores HA AWS | 16 cores HA On premises | Variable number of cores * | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
PRO |
ENTERPRISE |
PRO |
ENTERPRISE |
PRO |
ENTERPRISE |
ENTERPRISE |
ENTERPRISE |
PRO |
ENTERPRISE |
|||
Media streams | 400 | 2000 | 800 | 4000 | 1600 | 8000 | 4000 | 8000 | 400 - 2000 | 2000 - 10000 | ||
Sessions with 5 participants | 16 | 80 | 32 | 160 | 64 | 320 | 160 | 320 | 16 - 80 | 80 - 400 | ||
8 hours | $1.73 | $5.18 | $2.88 | $8.64 | $5.18 | $15.55 | $10.37 | $13.82 | $1.73 - $6.33 | $5.18 - $29.36 | ||
24 hours | $5.18 | $15.55 | $8.64 | $25.92 | $15.55 | $46.66 | $31.10 | $41.47 | $9.79 | $29.36 | ||
720 hours | $155.52 | $466.56 | $259.2 | $777.6 | $466.56 | $1399.68 | $933.12 | $1244.16 | $293.7 | $881.1 |
These prices only include the cost of an OpenVidu commercial license. If you are deploying your
OpenVidu Pro/Enterprise cluster in a cloud provider, you must take into account the
cost of the cloud resources you will be consuming (basically servers and bandwidth)
Pricing FAQs
1. How many users can my OpenVidu Pro/Enterprise cluster handle?
This is probably one of the most important questions when using OpenVidu Pro/Enterprise. The number of Media Nodes you need and the size of each Media Node depends on the answer. Therefore, the price of your OpenVidu cluster also depends on the answer.That being said, there is no single answer to this question. The load each Media Node can handle depends on many factors:
- The topology of each OpenVidu Session (1:1, 1:N, N:M)
- The type of media streams being published to the Session (only audio, only video, audio + video, HD video, screen sharing)
- Whether your Sessions are using advanced features such as recording or audio/video filters. The use of this features will greatly reduce the total number of users, as they bring along a high CPU consumption
- For OpenVidu Enterprise, using mediasoup instead of Kurento as media server will provide a 5x performance boost
You will need to perform some tests for your specific use case, and adapt the size of your cluster accordingly. OpenVidu team can perform these tests for you as part of their commercial services (contact us through Commercial page to ask for an estimate). For a quick reference, you can explore the pricing examples above and calculate the expected number of users your cluster will be able to handle. Simply divide the number of simultaneous media streams supported by each cluster between the number of media streams each one of your users will require in your application. For example:
- In a 1:1 application, each user will own 2 media streams: one for sending its own camera, and one for receiving the other user's camera. For this use case, a cluster that supports 800 simultaneous media streams will be able to host 400 users in 200 different OpenVidu sessions.
- In a 1:20 application (a virtual classroom, for example), the publisher will own 1 media stream for sending the camera feed. Each one of the 20 subscribers will also own a single media stream, just to receive the publisher's camera feed. For this use case, a cluster that supports 800 simultaneous media streams will be able to host 800 users in 38 different OpenVidu sessions.
- In general, in a N:N application, the total number of expected streams will be N*N. As N gets bigger, the number of media streams per session will grow exponentially. A 2:2 session has a total of 4 media streams. A 5:5 session, 25 media streams. A 10:10 session, 100 media streams. For this use case, the amount of users supported by an OpenVidu cluster will directly depend on the number of users per session (N). The bigger the sessions, more media streams per user will be required and less total users will be supported.
- If lots of users are connecting/disconnecting to/from OpenVidu sessions in a very small time interval, the load on the signaling plane (and therefore on the Master Node) will be increased.
- If your application has OpenVidu sessions with a high number of participants per session, the load of the signaling plane (and therefore on the Master Node) will be higher than for sessions with less participants per session (even with the same number of total participants).
- If your application makes heavy use of OpenVidu SDK methods that involve sending and receiving signals and events in your clients, the load on the signaling plane (and therefore on the Master Node) will be increased.
To overcome this bottleneck in the Master Node, OpenVidu Enterprise offers a High Availability deployment option with replication of Master Nodes. You can check it out here: High Availability.
2. How do I get charged when using OpenVidu Pro/Enterprise?
Users must create an OpenVidu account and get an OpenVidu License that can be used to deploy your OpenVidu Pro/Enterprise cluster.When purchasing an OpenVidu License, you will have to indicate your billing address and a credit card. You will receive a 15-day free trial period during which you will not be charged at all.
After the free trial period, a monthly billing cycle will charge all your expenses to your credit card. Therefore, you will receive an invoice each month. You can review your upcoming expenses and your past invoices in your OpenVidu account page. And don't worry: we don't store any credit card data. The entire billing process is securely done via Stripe.
OpenVidu Pro/Enterprise clusters will automatically report their usage on a recurring basis. That's why they need Internet access at all times. You won't be able to run your OpenVidu Pro/Enterprise cluster unless your Master Node has Internet access (see OpenVidu Pro architecture). If your specific use case doesn't allow your cluster to have Internet access, please contact us through Commercial page.
3. If I don't have any ongoing video session in my OpenVidu Pro/Enterprise cluster, do I have to pay?
Yes, OpenVidu License is charged for any running OpenVidu Pro/Enterprise cluster, even when there are no active sessions. If your cluster is on, you will at least have to pay for the Master Node(s). But remember you can drop Media Nodes to reduce the cluster size and reduce your bill according to user load. And as a definite measure you can always turn off the cluster so you don't even pay for the Master Node(s).4. What is the price per minute of each OpenVidu session?
The cost per minute of video call depends very much on the utilization ratio of your OpenVidu Pro/Enterprise cluster. That is, the number of calls you are able to maintain at the same time. If you use a cluster for an average of only 2 calls per hour, the cost per call will be rather high. If you manage to keep a number of calls adjusted to the size of the cluster, the cost will be lower.5. If I deploy an OpenVidu Pro/Enterprise cluster in a cloud provider, does its size automatically adapt to the user load?
Yes! You can adapt its size manually from OpenVidu Inspector or by consuming OpenVidu REST API (more info here). Or you can use the Autoscaling feature to let the cluster automatically decide when to increase or decrease the number of nodes.6. If I deploy OpenVidu Pro/Enterprise on premises, can I change the size of my cluster?
Of course. It is important to understand two different concepts when using on premises deployments of OpenVidu Pro/Enterprise: it's one thing the number of physical machines you have available in your cluster, and it's another thing the number of Media Nodes that are actually connected to your cluster.In OpenVidu Pro/Enterprise the price per minute only counts the Media Nodes actually connected to the cluster. Your OpenVidu License won't be charged for Media Nodes that are disconnected from the cluster even if they are turned on. Media Nodes are always disconnected from the cluster when dropped. If you then want to actually shut down the physical machine, you will have to listen to mediaNodeStatusChanged event until the Media Node reaches
terminated
status,
and then you can safely terminate your server. When deploying OpenVidu Pro/Enterprise in a supported cloud
provider, the cluster can automatically handle the launch and termination of the physical machines on
its own.
7. Which is the ideal size of an OpenVidu Pro/Enterprise cluster for my specific use case?
As explained here, the answer can vary greatly depending on multiple factors. You can use OpenVidu Load Test tool to perform a load test as similar as possible to your use case. OpenVidu team can perform these tests for you as part of their commercial services (contact us through Commercial page to ask for an estimate).8. I have built my application using OpenVidu CE. Is it compatible with OpenVidu Pro and OpenVidu Enterprise?
Yes. You don't have to change a thing in your application when upgrading your tier: it will work out-of-the-box with OpenVidu Pro and with OpenVidu Enterprise.There is a 15-day free trial period waiting for you!