Licensing & Support FAQs
- How has the licensing model changed for Valence 2.1?
- Why was the licensing model changed with the release of Valence 2.1?
- What is a typical licensing scenario for Valence?
- Is there a difference between the Valence software obtained with the Community, Professional and OEM licenses?
- How can I get updates for Valence?
- I have a free Community Developer license, can I still get updates to Valence?
- Does CNX provide support for the Valence framework or my Valence applications?
- How can I make sure I have everything I need in terms of licensing, updates and support?
- How do I make the applications developed with the Valence Community Developer License available to the Valence Community?
- If I can obtain the Valence Community Developer License for free, why should I upgrade to the Valence Professional Developer License?
- I downloaded the Valence Community Developer License and am creating some prototype applications to show my existing or potential customers. Do I need to post this work on the Valence Community Developer forum?
- I am an independent developer with several clients. Do my customers need to license Valence?
- Can I use Valence as the basis for creating an application framework with even more or different features?
- Do I need a license key to use Valence?
- Is source code included with Valence?
How has the licensing model changed for Valence 2.1?
Prior to version 2.1, Valence was licensed by IBM i serial number and once unlocked, the software functioned for an unlimited number of developers and users on that machine only. With the release of Valence 2.1 the licensing model has changed such that each developer needs a license to develop Valence applications. Starting with Valence 2.1, companies now need to make sure they have the proper number of licenses for developers creating applications with Valence. Licensing for run-time use of Valence has been made completely free so that a developer can deploy applications on any number of systems (with certain restrictions).
Why was the licensing model changed with the release of Valence 2.1?
The one-size-fits-all approach in early versions of Valence, while simple to administer, did not take into consideration the wide variety of use cases of the product. Licensing by developer, along with the new Community Developer License, dramatically reduces the barrier to entry for a single developer wanting to use Valence, and allows larger shops the ability to start small and gradually add licenses as Valence development expands. Furthermore, allowing unlimited run-time use of Valence applications on any number of systems makes application deployment much more simple.
What is a typical licensing scenario for Valence?
The most typical Valence licensing scenario would be to start with the free Community Developer License. Use the full features of Valence at no cost to prototype your applications and learn. When you're ready to deploy your first application to your end users, you can then either continue under the Community Developer License and contribute your apps to the Valence community or upgrade to a Professional Developer License to keep your apps private.
Is there a difference between the Valence software obtained with the Community, Professional and OEM licenses?
The Valence software downloaded with each license is identical (this may change in the future). The only difference is the terms of license. The Community Developer License is free, but requires you to make your code available to the Valence community when deploying it to end users under the "quid pro quo" principle. Under the terms of the Professional Developer License, you can create and deploy your custom applications and keep them private. The OEM Developer License further grants the right to deploy your applications in commercial software for resale or to host your applications as a service to outside customers. You should read each of the licenses to understand the full differences between each version.
How can I get updates for Valence?
Updates are any bug fixes, enhancements and new versions of Valence that are released. When purchasing a Support pack or Professional Developer license (or higher) you will create an account on CNX's management website. It is through this account that you will obtain updates online. If you obtain a Professional Developer license or higher you will automatically have access to updates within your account for a period of one year from date of license purchase. After the first year you will need to purchase a minimum 4-hour support pack to obtain updates. If you obtain a Community Developer license you will not have access to updates unless you purchase a minimum 4-hour support pack each year.
I have a free Community Developer license, can I still get updates to Valence?
You can only obtain updates for Valence through your online account at www.cnxcorp.com. In order to create an account with access to updates you must purchase a minimum 4-hour Support pack each year.
Does CNX provide support for the Valence framework or my Valence applications?
Yes, support is sold by CNX in packs of 4, 16 and 100 hours either separately or as part of a Value Bundle. The number of support hours remaining will always be shown in your online account. You use time from your account in minimum half hour increments when posting in the online Professional forum, emailing support@cnxcorp.com or calling the support line. Standard support terms are the same regardless of whether you have a Community, Professional or OEM Developer License, unless you have made special support arrangements with CNX. You should review your Valence Developer License agreement for additional support terms.
How can I make sure I have everything I need in terms of licensing, updates and support?
CNX recommends that you consider one of the Value Bundles from the Valence Store. The Value Bundles combine licensing, updates and support in one easy to understand package.
How do I make the applications developed with the Valence Community Developer License available to the Valence Community?
Once you deploy an application to your end users under the Community Developer License, go to www.cnxforum.com and post your code in the Valence Community Developer forum. If you would like to keep your code private, please visit the Valence Store to obtain a Valence Professional Developer License.
If I can obtain the Valence Community Developer License for free, why should I upgrade to the Valence Professional Developer License?
The Valence Community Developer License is primarily intended to allow developers an opportunity to prototype applications and learn Valence at no cost. If you are able to contribute your application back to the Valence community then no license fees are due to CNX and you can continue to develop application with Valence under the Community Developer License. Purchasing a Professional Developer License gives you the right to keep your code private, which is more appropriate in many scenarios. The purchase of a Professional Developer License also gives you automatic access to a year of Valence updates.
I downloaded the Valence Community Developer License and am creating some prototype applications to show my existing or potential customers. Do I need to post this work on the Valence Community Developer forum?
When working under the Valence Community Developer License, you only need to post code that has actually been deployed to end users in a "live" production scenario. You may create any prototype applications you need under the Community Developer License without the need to post the code until such time as the code is deployed for use by end users. You may also continue to keep the code private even after being deployed to end users if you purchase a Valence Professional Developer License from the Valence Store prior to your application being deployed.
I am an independent developer with several clients. Do my customers need to license Valence?
Your customers only need to obtain Valence Developer Licenses if they have internal developers also developing with Valence. When installing Valence at your customer sites the customer will need to agree to the Valence Run-Time License, which is free. If a customer does not have any internal programmers developing or maintaining Valence applications then the customer does not need to obtain Valence Developer Licenses. It is important to note that this scenario only applies if you are an independent software developer creating custom applications to the specifications of your customer. If you are creating a software package that will be sold to multiple customers as a canned package or provided as a service running from your systems, you must obtain a Valence OEM Developer License.
Can I use Valence as the basis for creating an application framework with even more or different features?
You may extend and alter the framework however you like for your own internal purposes, but you may not create a competing framework or alternate "flavor" of Valence and market it as a competing product to Valence. This scenario is expressly prohibited by all Valence licenses.
Do I need a license key to use Valence?
As of Valence 2.1 all license key mechanisms have been removed. You do not need to obtain a license key for Valence to function for development or run-time. However, when you use Valence, it is your responsibility to ensure that you are complying with the terms of the appropriate development and run-time licenses.
Is source code included with Valence?
As of Valence 2.1, all Valence downloads are distributed with source code.