Concurrent streams per account

Depending on your business case and licence rights you might want or need to restrict how many streams your customers can watch simultaneously with the same account.

Our platform gives you the ability to define concurrent sessions per user account:

• All streams: The general number of concurrent streams per user account (how many users can watch at the same time with the same user account)
• Streams per asset: The number of concurrent streams of the same asset (how many users can watch the same asset with the same user account at the same time)

The restrictions will be applied for all assets in your service. You can configure the settings here.

Concurrent streams per channel

In addition of the previous mentioned settings, there's also the possibility to add an override to Linear channels.
I.e. you can configure concurrent streams per channel.

This setting will override the streams per asset setting (independent if it's set higher or lower), but it will not be able to exceed the all streams setting.

Good to know

When testing these settings, you might find it hard to trigger the limits consistently if your using the WEB. Here's som good things to know about how our limits work together with Web browsers.

What counts as "concurrent stream" in browsers?

- Two different browsers will count as different streams

- Inkognito window and normal window in the same browser will count as two streams

- Two windows in the same browser will only count as one stream

- Two tabs in one browser will only count as one stream

- Two incognito windows for one browser will still only count as one stream

I can still start the stream again in my browser after changing the settings?

- If you stop the stream and then try to start it again, it might still be the old play-session that is resumed and the new settings don't apply to it