Skip to content

Configure Your Swarm

Allowed Domain Patterns

Swarms are designed to optimize one or more live video streams via a WebRTC Peer-To-Peer network. To specify which content should be optimized by a single swarm, you can define URL patterns to your content. To define patterns, you can use globbing 🔗.


* matches,,
us-0? matches,
* matches every existing domain matches

Token Authentication

To protect content from piracy, video URLs are often secured with server-side generated tokens. There are several schemes of how to apply those tokens to a URL.

Query Parameter Based Authentication is fully supported by Flink OTT. This means an authentication scheme of<YOUR_ID>.

Please Note: If you use another authentication scheme than Query Parameter Based Authentication, please contact us for an advanced configuration.

Tracker Access

Trackers need additional access to your content to optimize a stream. This means, our servers must be able to access your content. If you use security tools like geo-blocking, please contact us for advanced configuration. We host tracker servers in almost all countries and are happy to configure your tracker server appropriately.

When requesting data from your origin / CDN, the tracker server will send a X-Strive-Fetch header with a randomly generated string. For example X-Strive-Fetch: d00938a11d86715a92f4ce07bcf52e51. If possible, you can use this header an authorization method to whitelist all requests from our tracker to your origin / CDN.

Matching Policy

Determines how a tracker will match peers to clusters. There are three policies available:

  • Random maps peers randomly without a specific scheme. Although it seems counter-intuitive, this policy works very well for 10.000+ concurrent users.
  • Geo /ISP clusters peers based on network topological information and geoinformation.
  • ECDN / Intranet maps peers based on their public IPs and/or a given set of subnet masks.

(Optional) Web Media Selector

The Flink OTT Client SDK can track business-relevant data like traffic consumption without any further specification of a video player or similar. However, you can specify a CSS selector that points to your HTML5 player's video tag to collect even more data like buffering events, video quality and much more.

Next Steps

The next step is to verify your configuration 🔗.