What Is a Single Application?

Revision as of 14:33, 3 July 2009

What is a single application?

The standard definition for a single application is a single executable name - such as "myplayout.exe". However, there are a few cases when this rule can be altered. The following scenarios may help you understand how many Single Application licenses you require.

Several Editions or Versions of One Product

If you have, for example, a "Pro" and "Basic" version of your application, meaning that a single customer has always to make a choice between the two, and would never buy them both, we will treat the two editions as a single application.

The same rule applies to evaluation version or custom builds for specific customers.

Suits or Packages

An example here is a playout and capture application that you can build with our Multimedia SDK. Naturally, you can combine both applications into a suite and state that this is a single product. This would not be entirely fair, since this product includes two completely different applications, that can be combined into a suite for either marketing purposes, or for the purpose of "fitting" into our licensing scheme. In this particular example you will require two Single Application licenses.

On the other hand, if your application consists of several modules, and none of these modules is ever sold or used separately to the customer, we will consider this as one application.

This logic applies regardless of whether you are building software for sale or for internal use.

Same Engine, Different Products

No matter how similar the applications are, they shall be considered separate, if they target different markets (such as TV automation and digital signage) or customer groups. In such case, using a single executable name for the engine shall be considered a violation of our License Agreement.

Licensing