How do we move forward with an Acropolis evaluation and purchase?

Prospective Orion and Acropolis customers

When you evaluate Orion as a prospective customer, we set up an Acropolis service for you as part of the evaluation process. Therefore you are able to evaluate Acropolis at the same time that you are evaluating Orion. After the evaluation period, should you decide to move forward, you will have the option to purchase either an Orion OEM license or Acropolis subscription. If the latter, you will have the option to select the Acropolis hosting service tier at that time. Should you choose instead to purchase just an Orion OEM license and host Orion yourselves, you will have the option to download from your Acropolis subscription a backup of your database that you may have populated during the evaluation before we disconnect your Acropolis service.

Existing Orion OEM customers

If you are an existing Orion OEM customer and you wish to upgrade to Acropolis, we can set up an Acropolis service for you for a quick sanity-check evaluation prior to purchase, both to verify that your application can in fact communicate with a license server and service other than your hosted server, and to satisfy you that the Acropolis service does what it’s supposed to.

At the time of purchase, we will assign you an Acropolis service level and quote you an incremental annual subscription fee and one-time setup fee that depends on the state of your current hosted system, and we will prorate the annual subscription fee so that the renewal date coincides with the Orion OEM license subscription renewal date.

There are a few technical prerequisites for your existing application to be able to connect to the Acropolis-hosted service:

1. The license server URL specification needs to be parameterizable – you would provide the Acropolis URL parameter value to your existing customer installations.
2. Especially if you are subscribing to the core or premium hosting service tier, the Orion service name needs to be parameterizable – you would supply the service name assigned to your account to your existing customer installations. This could be an issue since many applications hard-code the default service name – if so, you will need to issue an update to your software product and incorporate the parameterization / new hard coding of the service name in your application.

Hard coding of the new service name will not lock you into the Acropolis, but hard-coding of the Acropolis URL will.