Licensing
Everything that there is about licensing Video Transport.
Video Transport pricing is based on the concept of channels. One channel allows you to:
  • Output one feed to a device or NDI® from the VT Receiver app. Note the fact that you can publish as many sources as you want, but output count will be restricted by your channels count in your actual license.
  • Preview one feed in the VT Receiver and VT Publisher.
  • Receive one contribution feed from The Web Guest Link. The return feed sent back to the contributor does not count as an extra channel.
  • Watch the two Web Previews of one feed.
Here's what a channel is:
  • One feed being sent from a VT Publisher to a VT Receiver counts as one channel.
  • The same feed received by another VT Receiver counts as another channel.
  • The native preview is...
  • A contribution feed received via VT Receiver from either VT Guest or The Guest Link counts as one channel. The return feed sent back to the contributor does not count as an extra channel.
  • Web previews don't count as additional channels if they are also being received by VT Receiver. If there are no VT Receivers connected to the same feed, number of web viewers counts as doubled channel value .
For example, if you are receiving a stream from one Publisher via 5 Receivers, it will take 5 channels. If you are receiving 5 streams from 5 Publisher instances with 1 Receiver, it will take 5 channels as well. Web previews will not count as extra channels in this case.
There are two ways of licensing Video Transport – a subscription model and an on-premises edition.

Subscription model

The fastest way to start is grab a channel package. We offer quarterly and annual licenses. You will find the prices here.

On-prem edition

If you wish for the server-side software to reside within your own premises, feel free to opt in to an on-prem edition, which also can be white-labeled. For details please reach out to [email protected].
Benefits of on-prem deployment:
  1. 1.
    Full control over the way your traffic is routed. If you choose, all traffic stays within your closed network.
  2. 2.
    You are free to choose your own hardware: self-hosted or in a public cloud (such as AWS). Use hardware that has been specifically certified for your industry or use case.
  3. 3.
    Web-based preview and contribution links can be hosted on your domain. The web-based interfaces can be white-labelled. Our Windows apps are not branded in any way.
  4. 4.
    Scale your server infrastructure depending on the current scenario: add or remove servers based on your current needs. Useful for event-based scenarios, scale up for big events or remove servers for small events to bring costs down.
  5. 5.
    Build custom secure video routes between distant locations by placing gateways in between for optimal latency and reliability.
Here's some details for on-premises hardware requirements.
Last modified 6mo ago