Syncrosoft’s DRM system implements a flexible license model.

Flexible License Model
In general, a protected application or content is linked to a license stored in the Syncrosoft’s hard- or software-based eLicensers. A license is actually a binary property storage that defines license types, license limitations and a set of eLicenser crypto-services. A license model, which is implemented in DRM services of the Syncrosoft eLicenser, defines the different license types and limitations. The license model can easily be extended or changed by issuing new DRM services.

License Types
Syncrosoft currently offers the following license types:

• Demo License ("Try before you buy"). The "Demo" license type defines a fully functional, but time-limited product version. The expiration date of the license is tamper-proof. This license version is used to offer a product to potential customers for evaluation in real world conditions.
• Full Version License. The "Full Version" license type is used for fully featured, not limited full versions of a product. Usually this is what the customers get when they purchase a product.
• Rental / Pay per Use License. The "Rental / Pay per Use" license type is used for fully functional, fully featured versions of a product, but limited in time or number of usages.
• Collections. The "Collections" license type is a combination of at least two single licenses which are combined inseparably. One example, where the use of this license type makes sense, is a special offer of a protected core application bundled with a protected accessory.
• Upgrade. The "Upgrade" license type is used to replace one license with another license.  For instance, a customer owns  "License Product 1". This license is the precondition for downloading "License Product 2".  During the download process the "License Product 1" is replaced by "License Product 2".
• Crossgrade / Downgrade. Similar concept as for the "Upgrade" license type.

Change of Properties
Syncrosoft’s DRM system allows the software vendor to change license properties as well as available license types for an existing product whenever a new or extended license is required, even long time after the product has been released to the market. Multiple MCFACT protected applications can be supported by a single license, and a single MCFACT protected application can be supported by multiple licenses.

No Need for different Builds
New and different license types can be created and linked to a protected application at any time of the product life cycle. This flexibility allows the software vendor to develop protected products as full versions only. There is no need to create different builds of the same software product for different applications, like demo or trial versions, update / upgrade versions or versions for rent. Depending on the vendors’ development process, this feature might be a tremendous timesaver for the engineering and QA teams.