JCAPI - Unlimited Runtime License Agreement
THE LICENSE IS A NON-TRANSFERABLE NON-EXCLUSIVE COMPANY LICENSE.
THE LICENSED COMPANY MUST ADHERE TO AND RESPECT THE TERMS GIVEN
BY THIS AGREEMENT, OTHERWISE WILL THE LICENSE EXPIRE WITHOUT ANY
PRIOR NOTICE FOR THE LICENSED COMPANY. THE LICENSE WILL ALSO EXPIRE
IF THE LICENSED COMPANY IS CLOSED DOWN.
A COMPANY IS WITHIN THIS AGREEMENT DEFINED TO BE A SUBJECT THAT IS
REGISTERED AND GRANTED BUSINESS ACTIVITIES BY THE AUTHORITIES IN
THE COUNTRY IN WHICH THE SUBJECT OPERATES.
THE LICENSED COMPANY IS GRANTED THE RIGHTS TO:
INSTALL AN UNLIMITED NUMBER OF JCAPI INSTANCES WITHIN THE LICENSED
USE JCAPI FOR ANY NUMBER OF DEVELOPERS DURING DEVELOPMENT OF A
PRODUCT THAT IS DEVELOPED BY THE LICENSED COMPANY.
USE AND LINK JCAPI INTO AN UNLIMITED NUMBER OF PRODUCTS, AND
COPIES OF THE PRODUCTS, THAT IS DEVELOPED BY THE LICENSED COMPANY
AS LONG AS THE JCAPI INTERFACE IS NOT DIRECTLY OR INDIRECTLY EXPOSED
BY THE PRODUCTS.
USE AND LINK JCAPI INTO AN UNLIMITED NUMBER OF PRODUCTS, AND
COPIES OF THE PRODUCTS, THAT IS OWNED BY THE LICENSED COMPANY AS
LONG AS THE JCAPI INTERFACE IS NOT DIRECTLY OR INDIRECTLY EXPOSED
BY THE PRODUCTS.
THE LICENSED COMPANY MAY NOT IN ANY WAY SELL OR TRANSFER THE JCAPI
LICENSE OR JCAPI PRODUCT ITSELF TO ANOTHER PARTY. THE LICENSED
COMPANY MAY NOT USE REVERSE ENGINEERING OR ANY OTHER METHODS/TOOLS/
WAYS TO EXAMINE/DISCOVER THE JCAPI CODE. THE LICENSED COMPANY MAY
NOT LINK JCAPI INTO A PRODUCT THAT IS SOLD OR TRANSFERRED TO
ANOTHER PARTY AS A SOFTWARE DEVELOPMENT KIT (SDK).
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL PHEOX AB BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT
OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
THE JCAPI PRODUCT IS SUBJECT TO EXPORT CONTROL IF EXPORTED OUT
OF THE EUROPEAN UNION.
THE JCAPI PRODUCT IS OWNED BY PHEOX AB, SWEDEN.
JCAPI License Frequently Asked Questions
- How is JCAPI licensed?
- Will the JCAPI license allow me to include JCAPI in my Java application that is to be sold to several customers, or do I have to pay per customer, installation, site etc?
- Will the JCAPI license allow me to include JCAPI in my development library (or SDK) that is to be sold to several customers, or do I have to pay per customer, installation, site etc?
- How is the evaluation version of JCAPI licensed, and are all functions available?
- My evaluation version has expired. Is there any chance to ge another trial period?
- Are there any other types of license agreements available e.g. for non-profitable organisations?
- Are there any free upgrades included when buying JCAPI?
1. How is JCAPI licensed?
Basically, JCAPI is licensed under the terms of a non-transferable non-exclusive company license.
By acquiring a JCAPI license, the licensed company has bought the rights to use JCAPI according to the terms stated by the license agreement. It does not mean that the licensed company owns the JCAPI product itself.
It is important to know that the license is bound to a single company only. For example, if a subsidiary company develops a JCAPI based product that is owned by its parent company, then two licenses must be acquired even though the companies are members of the same company group.
Shortly, the license agreement is as follows:
A licensed company is granted to:
- Install an unlimited number of JCAPI instances within the licensed company.
- Use JCAPI for any number of developers during development of a product that is developed by the licensed company.
- Link JCAPI into an unlimited number of products that is developed by the licensed company.
- Link JCAPI into an unlimited number of products that is owned by the licensed company.
A licensed company is NOT granted to:
- Sell or transfer the license to another party in any way.
- Sell or transfer JCAPI as a single product to another party in any way.
- Link JCAPI into a product that is sold or transferred to another party as a software library (SDK).
- Use reverse engineering or any other methods/tools/ways to examine/discover the JCAPI code.
The rights to use JCAPI for a licensed company will expire when:
- The license agreement is not adhered to or in any other way misused by the licensed company.
- The licensed company's business has closed down.
Pheox is not liable for any damages caused by the use of the JCAPI product.
2. Will the JCAPI license allow me to include JCAPI in my Java application that is to be sold to several customers, or do I have to pay per customer, installation, site etc?
Yes, you are allowed by the license to use JCAPI in an unlimited number of copies of your application, and better up, you are allowed to use it in an unlimited number of applications that is owned/manufactured by your company.
This kind of usage of JCAPI is known as a runtime license. It will however require that the functions/interface of JCAPI will only be accessed and used by your application(s) and not by the user(s) of your application(s). Simply meaning that you cannot directly, or indirectly, expose the JCAPI interface to any other parties than your company.
3. Will the JCAPI license allow me to include JCAPI in my development library (or SDK) that is to be sold to several customers, or do I have to pay per customer, installation, site etc?
No, you are not allowed to include JCAPI in a product that is sold or transferred as a development library (or SDK). You are not allowed to expose the interface of JCAPI, and you cannot circumvent this by adding wrapper-classes around the JCAPI functionality.
You are of course allowed to use JCAPI in your own proprietary software libraries that are used for building your applications though.
4. How is the evaluation version of JCAPI licensed, and are all functions available?
It can only be used for internal evaluation purposes. All other usage is prohibited.
All JCAPI functions are available in the evaluation version. However, the evaluation version can only be used during a limited period of time (60 days) until it will stop functioning.
5. My evaluation version has expired. Is there any chance to ge another trial period?
You will be able to evaluate JCAPI again when a new version of the product is released e.g. if JCAPI is upgraded from v1.2.0 to v1.2.1, you will be able to install and use the new version for another 60 days.
6. Are there any other types of license agreements available e.g. for non-profitable organisations?
Currently, there are no such license agreements available.
We've been thinking of introducing a special developers license for companies that would want to adapt, extend or brand the JCAPI source code with their own products.
7. Are there any free upgrades included when buying JCAPI?
Yes, you are entitled to get free updates of bug fixes and minor enhancements in functionality. To understand this better, it is good to know how version numbers applies to JCAPI. A version in JCAPI is defined as four numbers with dots in between e.g. 184.108.40.206
A version can thus be declared as:
a = Major release. New functionality and new classes are introduced. The interface of a previous version might also have been changed or removed. Example: adding major functionality, new concepts or new technologies into JCAPI.
b = Minor release. Extends the current functionality with new classes or methods that do not affect the underlying design/architecture. The interface of a previous version is kept intact, but may be noted as deprecated. Example: new PKCS#11 providers are supported, or more functionality is added to existing classes/interfaces.
c = Bug fixes (patches) available for public. This number will also get incremented when JCAPI is re-signed with a new code signing certificate when the old is about to expire.
d = Used for internal use during system test of JCAPI.
To conclude, you are entitled free upgrades of JCAPI when b and c are incremented.