| |
|
| Q. |
How do I purchase Orion? |
| A. |
The Orion SDK is available at no charge for a limited period to qualified prospective users. Our default pricing model under
which most of our customers purchase Orion is a revenue-based periodic license (typically annual, although we also offer
2-year, 3-year, 4-year and 5-year licenses). This gives you the ability to generate sufficient trial and production licenses
to meet your revenue projections for the protected products during the license period on payment of a single fee, with the
fee being determined by the total revenues (license fee, subscription, maintenance and support) in the license period of the
software being protected. The periodic license gives you access to all Orion’s capability for hosted licensing (automated
product activation and Internet-based floating licensing) on all supported platforms, for as many of your products as you
wish to protect. A license to redistribute the Orion server is also available should you also wish to offer floating
licensing over your end-customers’ networks. Orion annual licenses represent a small percentage of the total revenues
protected, and are very competitive with comparable solutions. |
|
|
| Q. |
What other charges are there? |
| A. |
The Orion license fee covers all Orion's capabilities on all supported platforms, and all the tools such as reporting and the Orion Proxy Server (for automated fail-over or for punching through customer firewalls). If you wish to take advantage of the Acropolis On-demand Managed Licensing Service, and the Acropolis Integration Module, then further set-up and subscription fees will apply. |
|
|
| Q. |
What training and consulting is required at startup? |
| A. |
We are happy to provide specific training or consulting services if required, but do not include any such services as part of our standard proposal. Our customers to date have been readily able to integrate Orion and go into production without any dedicated training or consulting (unless they had very complex licenisng needs). Orion is straightforward, and our documentation and headstart code samples, perhaps with one or two questions answered by email, are all that is needed. |
|
|
| Q. |
How much does the Acropolis On-Demand License Hosting Service cost? |
| A. |
For Acropolis you typically subscribe to the service for a year at a time, with the fees depending on the level of services required. Please contact us at sales@agilis-sw.com for further details. |
|
|
| Q. |
How much does the Acropolis Integration Module (AIM) cost? |
| A. |
For AIM you typically subscribe to the service for a year at a time, with the fees depending on the level of services required. Please contact us at sales@agilis-sw.com for further details. |
|
|
| Q. |
We sell outside the US. Is Orion subject to export controls? |
| A. |
Agilis's products are currently not generally subject to US export control laws provided their use is limited to their intended purpose of software license authentication and control. A license is currently required for export to Sudan, Syria and North Korea, and special steps are required for export to Cuba, Iraq and Rwanda. This list may change over time. There are no restrictions, licenses or special procedures required for you to export Agilis's products to any other country. |
|
|
| Q. |
We want to ensure we don't lose revenues to piracy, especially overseas. How secure is Orion? |
| A. |
Security is central to the Orion solution, with a number of defences against piracy attempts. For example, Orion client communication uses public-key cryptography to ensure authentication, confidentiality, integrity and accountability. The Orion client libraries use a digital signature mechanism to protect against attempted spoofing or replacement of the license checking code, and we include recommendations on how you perform your integration to make it hard for would-be hackers to even locate the license checks in your application. For time-limited licenses, such as trial or subscription licenses, Orion automatically performs a clock check and also checks for users who try to cheat by turning back their system clock. By using a secret password known only to your application and your Orion server to authenticate legitimate users you can also ensure hackers cannot become Agilis customers in parallel and generate their own licenses. Re-distributed Orion servers can be automatically locked to their host machines to ensure the license server is not replicated across several machines.
|
| |
|