Applies to: Kyvos Enterprise Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace
Kyvos Azure Marketplace Kyvos GCP Marketplace 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 | ||||||
---|---|---|---|---|---|---|
| ||||||
Note
|
...
Aura tab collection | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
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.
There are two payment models in the credit-based license type:
Depending on your license credits contract and deployment requirements, your license can have PAYU credits, Reserved credits or both.
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 | | |||||||||||||||||||||
|
...
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:
Connect the BI Server to the shared Credits Database.
See the Connecting shared Credits Database for cluster deployment section for more details.Provide the database details and its Secrets Manager details in the AWS Cloud Formation Template (CFT).
See the Creating Kyvos resources for AWS automated deployment with EMR section for more details.
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
...