Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Applies to: (tick) Kyvos Enterprise  (tick) Kyvos Cloud (SaaS on AWS) (tick) Kyvos AWS Marketplace

(tick) Kyvos Azure Marketplace   (tick) Kyvos GCP Marketplace (tick) Kyvos Single Node Installation (Kyvos SNI)

...

Kyvos supports credit-based and non-credit-based licensing models. Kyvos monitors the Master Service and the Query Service computation layers to determine usage/credit consumption.

...

  • On-premise (non-credit based) 

  • In your cloud account (credit or non-credit based) 

  • Managed Services (credit-based) 

...

Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

Note

  • The Kyvos 2022.3.1 release supports credit-based licensing only for AWS.

  • The license dates must be valid to use Kyvos servers and resources. 

  • For details on your specific plan or rates, refer to your license contract or contact your Kyvos representative. 

  • When Kyvos credits are exhausted, contact Kyvos Support to update the license and add more credits. 

  • In the case of Kyvos credits recharge,

    • If your license contract has a provision for carrying forward the remaining credits, a new license is created with a total value of Kyvos credits as a sum of the remaining credits and recharge value. 

    • If your license contract does not have a provision for carrying forward the remaining credits, a new license is created with a total value of Kyvos credits as a sum of the recharge value. 

...

Note

From Kyvos 2024.3 onwards, you can use a prepaid Query Engine and Cache Storage license model. If you exceed the prepaid limits and add more Query Engines or cache storage, you will be charged based on your usage. This specifically applies to AWS Managed Service

.

The olapengine.lic license file is used for non-credit based licensing.

Aura tab collection
paramsJTdCJTIyZ2VuZXJhbCUyMiUzQSU3QiUyMnRhYlNwYWNpbmclMjIlM0EwJTJDJTIydGFiV2lkdGglMjIlM0ExMDAlMkMlMjJ0YWJIZWlnaHQlMjIlM0E1MCUyQyUyMmRpcmVjdGlvbiUyMiUzQSUyMmhvcml6b250YWwlMjIlN0QlMkMlMjJjb250ZW50JTIyJTNBJTdCJTIyYmFja2dyb3VuZENvbG9yJTIyJTNBJTdCJTIyY29sb3IlMjIlM0ElMjIlMjNmZmYlMjIlN0QlMkMlMjJib3JkZXIlMjIlM0ElN0IlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyd2lkdGglMjIlM0ExJTJDJTIydG9wJTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmNvbG9yJTIyJTNBJTdCJTIybGlnaHQlMjIlM0ElMjIlMjNjY2NlY2YlMjIlN0QlN0QlMkMlMjJwYWRkaW5nJTIyJTNBJTdCJTIydG9wJTIyJTNBMTAlMkMlMjJyaWdodCUyMiUzQTEwJTJDJTIyYm90dG9tJTIyJTNBMTAlMkMlMjJsZWZ0JTIyJTNBMTAlN0QlN0QlMkMlMjJhY3RpdmUlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzZjU4MjI3JTIyJTdEJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSU3QiUyMmxpZ2h0JTIyJTNBJTIyJTIzMDAwMDAwJTIyJTdEJTJDJTIydGV4dEFsaWduJTIyJTNBJTIybGVmdCUyMiUyQyUyMmZvbnRXZWlnaHQlMjIlM0ElMjJib2xkJTIyJTdEJTdEJTJDJTIyaG92ZXIlMjIlM0ElN0IlMjJiYWNrZ3JvdW5kQ29sb3IlMjIlM0ElN0IlMjJjb2xvciUyMiUzQSUyMiUyM2RmZTFlNiUyMiU3RCUyQyUyMnRleHQlMjIlM0ElN0IlMjJmb250U2l6ZSUyMiUzQTE4JTJDJTIyY29sb3IlMjIlM0ElMjIlMjM1ZTZjODQlMjIlMkMlMjJ0ZXh0QWxpZ24lMjIlM0ElMjJsZWZ0JTIyJTJDJTIyZm9udFdlaWdodCUyMiUzQSUyMmxpZ2h0ZXIlMjIlN0QlN0QlMkMlMjJpbmFjdGl2ZSUyMiUzQSU3QiUyMmJhY2tncm91bmRDb2xvciUyMiUzQSU3QiUyMmNvbG9yJTIyJTNBJTIyJTIzZjRmNWY3JTIyJTdEJTJDJTIydGV4dCUyMiUzQSU3QiUyMmZvbnRTaXplJTIyJTNBMTYlMkMlMjJjb2xvciUyMiUzQSUyMiUyMzVlNmM4NCUyMiUyQyUyMnRleHRBbGlnbiUyMiUzQSUyMmxlZnQlMjIlMkMlMjJmb250V2VpZ2h0JTIyJTNBJTIybGlnaHRlciUyMiU3RCUyQyUyMmJvcmRlciUyMiUzQSU3QiUyMnRvcCUyMiUzQXRydWUlMkMlMjJsZWZ0JTIyJTNBdHJ1ZSUyQyUyMnJpZ2h0JTIyJTNBdHJ1ZSUyQyUyMmJvdHRvbSUyMiUzQXRydWUlMkMlMjJ3aWR0aCUyMiUzQTElMkMlMjJzdHlsZSUyMiUzQSUyMnNvbGlkJTIyJTJDJTIyY29sb3IlMjIlM0ElN0IlMjJsaWdodCUyMiUzQSUyMiUyM2NjY2VjZiUyMiU3RCU3RCU3RCU3RA==
Aura tab
summaryCredit-based license
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJDcmVkaXQtYmFzZWQlMjBsaWNlbnNlJTIyJTdE

Kyvos provides a provision to use Kyvos credits for multiple deployments, such as Production, non-production, Dev, Active HA , and so on. When this license model is used, the usage is shown in terms of Kyvos credits. The credits consumption for all deployments is deducted from the total of Kyvos credits you have purchased. In this licensing model, there is no provision to purchase separate credits for different layers, such as Compute, storage, and build Services.

Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

  • This license type is applicable for both managed services and non-managed services.

  • From Kyvos 2024.3 onwards, a prepaid Query Engine and Cache Storage can be utilized through licensing. If you exceed the prepaid limits and add more Query Engines or cache storage, you will be charged based on your usage. This specifically applies to AWS Managed Service.

There are two payment models in the credit-based license type:

  • Pay-as-you-go (PAYU): In this payment model, you per as per your usage. The usage is deducted from the total of the purchased Kyvos credits. In your Kyvos license, the rates (defined in credits) for each Kyvos layer are explicitly specified for each deployment. Therefore, the credits consumed by each deployment are deducted from the total credits you purchased. If your PAYU credits are exhausted, contact Kyvos Support to update the license and increase the credits.

  • Reserved credits: In this payment method, you pay in advance to reserve the Kyvos Query layer and/or the service layer. Hence, credits consumed by these layers are not deducted from the total of the purchased Kyvos credits.

Depending on your license credits contract and deployment requirements, your license can have PAYU credits, Reserved credits or both.

Aura tab
summaryNon-credit-based license
paramsJTdCJTIydGl0bGUlMjIlM0ElMjJOb24tY3JlZGl0LWJhc2VkJTIwbGljZW5zZSUyMiU3RA==

This license type applies only to the non-managed services (on -premises) deployment.

This license type is created based on the requirement of computing resources, BI Server instances and Query Engines. Your license contract contains the count of BI Server instances and Query Engines and the maximum node capacity where these services can run. It also includes the validity period to use the Kyvos resources.

When the validity period of your license contract is completed, the Kyvos cluster does not stop, but processing or querying is not allowed. In this case, you need to update the license and increase the limits. To do this, you must contact Kyvos Support Team.

Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

...

  • The grace period is applicable only for credit-based licensing. 

  • The grace period and the license expiry date are decided as per your license contract with Kyvos. 

  • When your Kyvos credits are exhausted, the Kyvos cluster runs in the grace period. You get the following notification on Kyvos. 

  • To avail of Kyvos services, you must contact Kyvos Support to update your license and increase the usage limits. 

How the Kyvos credits licensing work 

...

  • A shared Credits Database must be created and configured during the first (primary) cluster deployment. This database manages credit consumption transactions for multiple cluster deployments. 

  • In case of multi-cluster deployment (secondary or tertiary), you must do the following: 

  • If Kyvos credits are exhausted or your validity period is completed, the Kyvos cluster runs in the available grace period.

  • If your Kyvos credits are exhausted, the build jobs run in the grace period. If this period elapses while a build job is running, Kyvos will complete the job and then stop the cluster

...

Related topics

...