## 2.3.3.7 Service Plans and Metering for Kyma Runtime
This page explains the relationship between the service plans of the SAP Discovery Center and the service plans of the SAP BTP cockpit and provides information to help you understand how the service is billed.
## Service
## Overview
The following diagram shows how the service plans listed in the SAP Discovery Center correspond to the plans you choose in the SAP BTP cockpit. For more information about the commercial model, see What is the Consumption-Based Commercial Model?
Note that there's no subscription-based commercial model for SAP BTP, Kyma runtime.
## Consumption-Based Models
<!-- image -->
## Subscription
No Subscription available for SAP BTP , Kyma runtime
## SAP BTP Cockpit: Service Plans
| Name   | Service Plan (Discovery Center)   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
|--------|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| free   | Free                              | Subscribe to the 30-day free plan provided on Amazon Web Services. This plan uses Kyma on a limited-size clus- ter (4 CPU-16 GBRAM). You can use the free plan only once in a global account for up to 30 days. The upgrade to the paid plan is not yet supported. Only best-effort sup- port is available for free tier service plans, and these are not subject to SLAs. The services you plan to use must be available in the same region as the subaccount for the Kyma runtime. |
| aws    | Standard                          | Select Amazon Web Services as the cloud provider where your Kyma cluster is deployed.                                                                                                                                                                                                                                                                                                                                                                                                |
| gcp    | Standard                          | Select Google Cloud as the cloud provider where your Kyma cluster is deployed.                                                                                                                                                                                                                                                                                                                                                                                                       |
| azure  | Standard                          | Select Microsoft Azure as the cloud provider where your Kyma cluster is deployed.                                                                                                                                                                                                                                                                                                                                                                                                    |
## Metrics
The usage metric for SAP BTP, Kyma runtime is a Capacity Unit (CU) per hour.
| Metric        | Definition                                                                                                                                                                                |
|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Capacity Unit | Number of units consumed by the usage of the services as outlined in the solution- specific product supplement. For SAP BTP, Kyma runtime, CUs are calculated for nodes and for storage . |
## Backward Calculation
##  Tip
If you use the Cloud Manager module, also see Calculation with the Cloud Manager Module [page 96].
## Formula
The formula is a mapping between consumed nodes/storage and the respective CUs. The details are provided in the following tables.
However, as Kyma supports flexible scaling, cost per hour may vary because it depends on the size of the nodes that were used.
## Underlying Metrics: Nodes
The nodes calculation takes the number of virtual CPUs (vCPUs) and provides the number of CUs per hour. To better understand the relationship between vCPUs and nodes, note that one node is sized with 2 vCPUs.
The Calculation for vCPU table presents data for general-purpose machine types.
Calculation for vCPU
| Number of vCPUs   | Number of CUs per Hour   |
|-------------------|--------------------------|
| 2                 | 0.24 * 1.5               |
| 4                 | 0.24 * 2                 |
| 8                 | 0.24 * 4                 |
| 16                | 0.24 * 8                 |
| 32                | 0.24 * 16                |
| ...               | ...                      |
## Underlying Metrics: Storage
You can calculate CUs for different storage types: PersistentVolume and VolumeSnapshotContent resources. SAP BTP, Kyma runtime is provisioned with 32 GB of storage dedicated to operational data at no additional cost. However, certain Kyma modules may require extra storage. In such cases, they create additional volumes, which incur charges for the extra storage used. Note that for PersistentVolume resources, storage is provided in blocks of 32 GB, so if you use 33 GB, you're charged for 64 GB (2 blocks of 32 GB). For VolumeSnapshotContent resources, you pay based on the actual amount of storage used.
| Amount of Storage   |   Number of CUs per Hour |
|---------------------|--------------------------|
| 32GB                |                     0.02 |
## Examples
- Your consumption report for nodes shows 1800 capacity units charged for 4 vCPU nodes for 30 days. This means that you were running roughly 1800 / (0.24 * 2) = 3750 hours worth of 4 vCPU nodes. Given that 30 days have 720 hours, this means you were running 3750/720 = 5.21 nodes cluster for the 30 days. Due to Kyma's automatic scaling, 5.21 does not mean actual size. It means that during some hours in the 30 days, the cluster size was 4 nodes. At other times, there was more load, so the cluster autoscaled to 5 or 6 nodes, based on your configurations. So your average cluster size for the 30 days was 5.21 nodes.
- Your consumption report for storage shows 200 capacity units charged for storage (32 GB block) for 30 days.
This means that you used 200 / 0.02 = 10000 hours of 32 GB storage blocks. Given that 30 days have 720 hours, this means that you have used 10000/720 = 13.89 blocks of 32 GB over the 30 days. So, you used 13.89 * 32 = 444.44 GB of storage continuously during the 30 days.
This implies that as you started using Kyma, you deployed more applications that used storage of various sizes, such as 4 GB or 8 GB.
## Calculation with the Cloud Manager Module
## Calculation with the Cloud Manager Module
Using the Cloud Manager module and enabling Redis or NFS storage or both, introduces additional costs.
- The cost of NFS storage introduces factor 3 to the calculation. Note that NFS storage is provided in blocks of 32 GB, so if you use 33 GB, you're charged for 64 GB (2 blocks of 32 GB).
Calculation for NFS Storage
| Amount of NFS Storage   | Number of CUs per Hour   |
|-------------------------|--------------------------|
| 32GB                    | 0.06 (= 0.02 * 3)        |
- Using Redis adds costs depending on the tier you choose.
##  Note
Even though the actual available size (GiB) might vary depending on the cloud provider, the tiers for Redis are standardized across cloud providers. Because of that, also the pricing is standardized across all available cloud providers.
Calculation for Redis Tiers
| Tier   |   Approx. Available Size (GiB) |   Cost in Storage Size per Hour |   Number of CUs per Hour |
|--------|--------------------------------|---------------------------------|--------------------------|
| S1     |                              1 |                        0.252778 |                 0.102778 |
| S2     |                              3 |                        0.505556 |                 0.205556 |
| Tier   |   Approx. Available Size (GiB) |   Cost in Storage Size per Hour |   Number of CUs per Hour |
|--------|--------------------------------|---------------------------------|--------------------------|
| S3     |                              6 |                         1.32361 |                  0.5375  |
| S4     |                             12 |                         2.65972 |                  1.08056 |
| S5     |                             24 |                         5.26806 |                  2.14028 |
| S6     |                             48 |                        10.5431  |                  4.28333 |
| S7     |                            101 |                        21.0833  |                  8.56528 |
| S8     |                            202 |                        42.1569  |                 17.1264  |
| P1     |                              5 |                         2.64306 |                  1.07361 |
| P2     |                             12 |                         5.31667 |                  2.15972 |
| P3     |                             24 |                        10.5361  |                  4.28056 |
| P4     |                             48 |                        21.0833  |                  8.56528 |
| P5     |                            101 |                        42.1708  |                 17.1319  |
| P6     |                            200 |                        84.3111  |                 34.2514  |
## Examples for Cloud Manager
- Your consumption report for the NFS storage shows 200 capacity units charged for storage (32 GB block) for 30 days.
This means that you used 200 / 0.06 = 3333.33 hours of 32 GB storage blocks. Given that 30 days have 720 hours, this means that you have used 3333.33/720 = 4.63 blocks of 32 GB over the 30 days. So, you used 4.63 * 32 = 148.15 GB of NFS storage continuously during the 30 days.
- Your consumption report for Redis shows 200 capacity units for storage for 30 days. This means that you used 200 / 0.1027777778 = 1945.946 hours of the Redis S1 tier. Given that 30 days have 720 hours, this means that you have used 1945.946/720 = 2.703 tier S1 Redis instances continuously during the 30 days.
## Calculator
Find the Kyma price calculator at https:/ /kyma-project.github.io/price-calculator/ and use it to estimate the costs for your SAP BTP, Kyma runtime.
1. Choose the base configuration for the size and minimum number virtual machines (VM) you need.
2. Optionally, add more storage to the calculation.
3. If needed, adjust the conversion rate.
Note that the result is an estimate, and the consumption report may vary depending on the actual hours and size of the Kyma cluster (nodes and storage) that was running in 30 days.
## Supplemental Terms And Conditions
For more information, see SAP Business Technology Platform Service Description Guide , section 'SAP BTP, KYMA RUNTIME'.
## Glossary
Commercial Information Glossary
## Service Specifics
As soon as you instantiate a Kyma cluster, the basic cost for the empty cluster incurs.
Cost may then vary depending on the actual nodes and storage you consume.