What Is a Single Application?
| (12 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{This|sales/licensing_faq/what_is_a_single_application.html}} | ||
| + | |||
| + | This article explains in detail what our Single Application licensing option stands for. | ||
| + | |||
==What is a single application?== | ==What is a single application?== | ||
| Line 7: | Line 11: | ||
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. | 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 | + | The same rule applies to evaluation versions or custom builds for specific customers (with the exception of OEM). |
===Suits or Packages=== | ===Suits or Packages=== | ||
| − | An example here is a playout and capture | + | An example here is a playout and capture applications. 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 | + | On the other hand, if your application consists of several modules, and none of these modules is ever sold 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. | This logic applies regardless of whether you are building software for sale or for internal use. | ||
| Line 19: | Line 23: | ||
===Same Engine, Different Products=== | ===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]]. | + | 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 [[AVObjects License Agreement|License Agreement]]. |
| + | |||
| + | ===OEM=== | ||
| + | |||
| + | If you are acting as an OEM, meaning that your application is being redistributed by other companies, every such redistribution contract shall require a separate Single Application license. | ||
===Platforms & Enterprise Class Deployment=== | ===Platforms & Enterprise Class Deployment=== | ||
| Line 27: | Line 35: | ||
==See Also== | ==See Also== | ||
| − | * [[ | + | * [[AVObjects License Agreement]] |
__NOTOC__ | __NOTOC__ | ||
[[Category:Licensing FAQ]] | [[Category:Licensing FAQ]] | ||
Latest revision as of 18:31, 27 June 2022
This page is a copy of the original page on the AVObjects' web site and can also be viewed here.
This article explains in detail what our Single Application licensing option stands for.
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 versions or custom builds for specific customers (with the exception of OEM).
Suits or Packages
An example here is a playout and capture applications. 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 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.
OEM
If you are acting as an OEM, meaning that your application is being redistributed by other companies, every such redistribution contract shall require a separate Single Application license.
Platforms & Enterprise Class Deployment
If your product is a platform, and every deployment involves a considerable amount of customization, every such deployment shall require a separate Single Application license.
