Analyze Software Usage

Demographics and Metrics:

Operating Systems
Track each OS, OS language, and timezone across your user base. No personally identifiable information (PII) is collected.
Know how often and for how long each part of your software is used.
Know how many of each kind of token has been used, and for how long each kind of token was held.

Text Storage

About Notes:

Client software may read/write up to 8 KB notes from/to the encrypted license, useful for a variety of purposes.
The client may read a note set by the software vendor, but not overwrite such a note. Transmit timely messages and promotions to your end users.
License Types
Trial, Single User, Multi User

About License Types:

A single license valid for a short, fixed time period.
Single User
A single license valid for a single user on only one machine at a time.
Multi User
A single license valid for a set number of multiple concurrent users, across one machine or multiple machines. Requires a separate license directory for each user.

A license file supports the collection of analytics, and enables creative pricing via segments and tokens. Single and Multi user licenses can be issued on a permanent or subscription basis.

To prevent a license file from being used on more than one machine at a time, perodic interaction with the license server is necessary, known as a license 'refresh'. It is recommended to refresh the license once at application startup, and periodically at an interval period set in the license template appropriate to the use case, see examples.

Interaction with the license is accomplished by including our library with your application, using an interface for your language generated by SWIG.

Software Partitions

About Segments:

Fractional Pricing
Control access to different portions of your software by breaking it into segments. Control access at any scale, all the way down to individual lines of code. Use with named tokens for even more fine-grained control within segments.

Checkout, Consume or Use, Return

Named Tokens:

Each token is valid for one use, functioning as a counter for custom pricing scenarios. Single-Use tokens are consumed upon use, with a record kept of total number used.
A token typically enables holder access to some privilege, with a record kept of how many times each was used. A token can be held for multiple uses, or returned to the global pool, becoming available to other users of a multi-user license. Choose up to 128 different custom token names total for both token types.