| |
|
| Q. |
Can I issue trial or subscription licenses? |
| A. |
Yes. You can configure a license to be limited to any time period, from days, to years, or perpetual. The time limit can be absolute (e.g. expires 30 days from today) or relative (e.g. expires 30 days from first day of activation). |
|
|
| Q. |
What about users who try and cheat on time-limited licenses? |
| A. |
Orion includes automatic checks to ensure the system clock has not been turned back in an attempt to cheat on a time-limited license. |
|
|
| Q. |
I need to control different modules or options in my application. How can I do this? |
| A. |
With Orion you can set up any number of options or modules, each with an associated parameter which you then configure for each user. For example, you could have Module A with possible values of Off/Standard/Basic/Pro, Module B with allowed values of 0/1/2/3/4/5...., Module C could be Off/On and so forth. |
|
|
| Q. |
We are considering usage-based licensing. How does this work? |
| A. |
Orion includes the concept of quota points. How you consume or track these points is up to you and your application. For example, you could consume points as your application is used (perhaps with a high-value function consuming 5 points each time it is run, and lower values consuming 1 point), and set a quota limit (debiting), or you can track usage for subsequent billing (metering). |
|
|
| Q. |
We have other parameters we want to control via the license. Can I do this? |
| A. |
Orion include custom fields so you can include any other data you require in a license, and transmit it to your application. For example, you could include an XML string to define your custom parameters, or pass in the key for a legacy licensing system. |
| |
|