CrossWorks Licensing Explained
FeaturedNow that we have released CrossWorks 3, it is clear that some customers do not understand how our licensing works and what the associated costs are. This article will try to explain the options available to you as concisely as possible.
Named Developer Commercial License
This is by far the most popular license that we offer. This is for use by a single Named Developer on machines required to run CrossWorks. This is not a license for multiple developers to use a single machine, or for sharing a license between developers by having one developer request activation and distributing activations to colleagues.
Maintenance and Upgrade Costs
CrossWorks customers can elect to defer upgrade costs to a Major Version Upgrade release of CrossWorks or can pay a yearly maintenance fee to receive support and all Major Version Upgrades free of charge. These options are explained here.
It seems that customers are surprised that they need to pay for a Major Version Upgrade when it comes along. Our pricing policy has been the same for the last ten years, and that is that Major Version Upgrades are set at 50% of a new license purchase and there is no fixed interval between major releases. Rather than paying for these updates at irregular intervals, you can elect to pay for maintenance and support yearly which spread the cost of CrossWorks that way. This product is known as Software Update Assurance (SUA) please see our website for current pricing.
Each time you activate CrossWorks, the e-mail that you receive from us with the activation key contains an indication of when your support will expire or when it expired. If you decide you don't want to pay yearly for maintenance, then your support requests will automatically be low priority and "best effort."
If your maintenance has expired and you would like to acquire the latest release of CrossWorks, you can contact us to discuss your options.
If you have any comments, or would like additional explanation added to this article, please drop us a line...
Post is closed for comments.
Comments
0 comments