Playback access

Open or tokenised. You choose for every channel.

Some channels are meant for everyone. Others need to be locked down. Each channel on Tamil Streams can serve an open URL or a tokenised URL, and in both cases the number of concurrent viewers follows the package you picked.

Option 1

Open URL

A plain playback address. Anyone who has the link can play it, with nothing to add or manage.

rtmp://cdn.tamilstreams.com/acme/news

Best for

  • Public channels and free-to-air style streams
  • Embedding on your own website or app
  • Creators who want the simplest setup

The viewer limit of your package still applies.

Option 2

Tokenised URL

The same address with a secret token. Only people holding an active token can play, and you can switch any token off at any time.

rtmp://cdn.tamilstreams.com/acme/news?token=7f3a9c1e4b82d05f

Best for

  • Paid, private or reseller channels
  • Giving each area or customer group its own key
  • Shutting off a leaked link without touching the others

Each token can have its own viewer limit, inside your package pool.

Your plan sets the limit

Concurrent viewers come from your package.

A package gives you a pool of concurrent viewers, meaning devices watching at the same moment. That pool applies whether the channel is open or tokenised.

  • Choose a package size that covers your peak audience, or choose Unlimited.
  • With tokenised access you can split the pool across keys, for example 20 viewers for one reseller and 30 for another.
  • Viewers beyond the limit cannot start playing until a slot frees up.
  • Switch a channel between open and tokenised from the customer portal.
Work out the right size

Controls

What you can control

Concurrent viewers

Set by your package. The same limit protects open and tokenised channels from a surprise audience.

Tokens per link

On tokenised channels, create as many access keys as you need and label each one so you know who has it.

Instant revoke

Disable a token and it stops working at once. Nobody else's link changes.

Protocol-specific keys

A key is bound to one output, such as HLS or DASH, so a link made for one use cannot be used for another.

Separate publish key

The key your encoder uses is never the key viewers use, so sharing a playback link does not expose your ingest.

Rotate when needed

Change your publish key from the portal if an encoder is lost or a team member leaves.

Open, tokenised, or both.

Run public and private channels side by side on the same account. No add-on to buy.