Kyvos Licensing

Kyvos Licensing

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

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


To continue using Kyvos resources, you MUST have a valid license file. An expired license file cannot be reused. Contact Kyvos Support to get your renewed license file. 

Important

Please note that once your license has expired, you must only recharge it with a valid license when your cluster runs in the grace period.

To know the license expiry date, refer to your license contract, see the Subscription Plan page, or check validity through Kyvos Manager.

You can also subscribe to notifications to get notified before the license expires. For credit-related notifications, you will receive notifications such as:

  • Your credits are exhausting. Please recharge.

  • Your credits are exhausted; hence the Kyvos cluster will shut down. Please recharge.

  • The validity period has expired. You still have remaining <100> credits. To use the remaining credits, please recharge.

If subscribed, you get credit-related email notifications depending upon the configured thresholds. You can configure the credit limit threshold from Manage Subscription.

Kyvos license management from Web Portal

Viewing Kyvos license

Viewing credit-based license details 

The information about the purchased Kyvos credits is displayed on the Subscription Plan page (explained below) on the Kyvos Web portal. Depending on the details of your credit-based license, the rates for different Kyvos layers, such as Compute, Storage, and query engine, are displayed. 

Based on the type of credit file (PAYU credits, Reserved credits, or containing both the credit types) you upload, the Kyvos Usage Dashboard displays the credit purchased details.
See the Monitoring Kyvos credits usage section for more details. 

The details include: 

  • The number of purchased credits for each Kyvos layer 

  • The expiry date of Kyvos credits. It also displays the number of days remaining in the expiry date

  • The usage rates for different Kyvos layers 

  • The usage rates for the Storage layers  

  • Carry forward details of remaining credits 

  • Deployment ID 

  • Grace period

  • Kyvos credit model as PAYU/reserved

To view the credit details, perform the following steps. 

  1. From the Toolbox, click Setup > Subscription Plan. 
    The Subscription Plan page shows details of the purchased credits, validity period, and computation costs of different Kyvos layers. Depending on your license contract and deployment requirements, your license file can contain PAYU credits, Reserved credits, or both. 

  2. For computation resources, you can view the hourly cost for BI Servers and Query Engines. Query layer rates are displayed per query engine. You can view the hourly cost of query engines according to the running capacity, such as zero, moderate, and full.

  3. For storage resources, the per-month GB cost is displayed.

  4. Click View Usage to view the details of consumed credits. 

Viewing non-credit based license details 

You can view the license details, including information on the available and maximum BI Servers and Query Engines.

To view BI Server and Query Engine information, perform the following steps.  

  1. From the Toolbox, click Setup, then click License.

  2. You will see the maximum capacity supported by your license in the table headers—for example, 5 BI Servers. 

  3. The graph shows the number of used and unused portions up to the total capacity. Hover the cursor over the bars in the graphs to see additional details.

Uploading a new license

To upload a license while using Kyvos, perform the following steps. 

  1. From the Toolbox, click Setup, and then click License.

  2. View the current license details, including the expiration date and the remaining days.

  3. To upload a new license, click Browse, navigate to the license file and select it.

  4. Click Upload.

Upon uploading the new license file, the credit details will be displayed on the Subscription Plan page. See the Monitoring Kyvos Usage section for more details. 

For credits-based Kyvos license file 

For a credit-based license, evaluation license files (Kyvos credits license file and Kyvos license file) are used to create the primary cluster, secondary, or tertiary for deployment. These license files do not contain a shared database name or deployment ID.

For the secondary or tertiary cluster deployment, you must use the evaluation license file (Kyvos license file). 

Post-deployment of this primary or secondary cluster, you must replace the evaluation license files with valid Kyvos licenses.
Points to remember 

  • If your license contract contains PAYU credits for the primary cluster deployment, do the following:

    1. Upload the Kyvos credits license file containing the purchased Kyvos credits, as explained below.
      NOTE: This credits license file must be uploaded only when you deploy a primary cluster, as it contains credit consumption rate details for Kyvos resources shared across all deployments. And hence, do NOT upload this license file for further deployments, such as secondary or tertiary cluster deployment.

    2. After uploading the Kyvos credits license file, you must upload the Kyvos license file. It contains deployment-specific details; hence while deploying a secondary or tertiary cluster, you MUST upload this license file on each deployment.

  • If your license contract contains Reserved Instances for primary or secondary cluster deployment, you must upload the Kyvos credits license file as it contains a specific deployment ID. 

  • You MUST restart the BI Server after uploading the credit load license file for the credit-based license to come into effect.

To upload the Kyvos credits license file for the primary deployment, refer to the Manage Credits section.

Kyvos license management from Kyvos Manager

  • Updating Kyvos license

    • Generating a license request file

    • Uploading a renewed license

Copyright Kyvos, Inc. 2025. All rights reserved.