# Consumption-Based Model {% hint style="info" %} This documentation is **exclusive** to customers using the Consumption-Based Model and may not be applicable to your realm. {% endhint %} The Consumption-Based Model is a licensing model of the Digibee Integration Platform in which pricing is based on the consumption of metrics related to pipeline executions, GB-seconds, and egress traffic. ## How does it work? You purchase credits based on your needs, and each metric consumes a different amount of credits during the contracted period. You can track your credit usage within the Platform to effectively monitor and manage consumption. {% hint style="success" %} Consumption is valid for all environments. {% endhint %} ## Understanding the Consumption metrics * **GB-seconds (gigabytes.seconds or GB-s):** Represents the lifespan of a pipeline instance (replicas) multiplied by its memory size in GB. For example: * **Small:** 0,0625 GB | 64 MB | 10 threads | 20% CPU * **Medium:** 0,125 GB | 128 MB | 20 threads | 40% CPU * **Large**: 0,25 GB | 256 MB | 40 threads | 80% CPU **Number of pipeline executions:** Represents the total number of executions of a pipeline. **Number of Egress Traffic bytes:** Represents all data traffic that leaves the Digibee Integration Platform, whether to the public internet, to another cloud, or to a local network. ## Calculation used in the Consumption-Based Model Refer to the example below to understand how billing calculations work in the Consumption-Based Model. {% hint style="warning" %} The financial values used in the following example are **illustrative only**. They are meant to show how consumption-based pricing is calculated, and **do not reflect the actual rates charged on the platform**. Your specific rates are defined in your contract. {% endhint %} **Example:** 1,000 executions in 1 small pipeline replica running for 1 hour, consuming 1GB of egress traffic. **GB-s:** 0.0625 GB \* 3600s = 225 GB-s \* 0.0008 = $ 0.18 **Executions:** 1,000 \* 0.000008 = $0.008 **Egress Traffic**: 1GB \* 0.50 = $0.50 **Total =** GB-s + Executions + Egress Traffic = $ 0.688 ## Consumption-Based Model on the Platform ### How to access your data 1. Click **Settings** in the upper right corner on the Platform home page. 2. In the **Licensing** menu, click **License consumption**. The Consumption page on the Digibee Platform is divided into two tabs: **Contract Overview** and **Detailed Usage & Costs**. Below, you’ll learn how to interpret the data and make better use of the available resources. {% hint style="warning" %} The screenshots below show a sample environment. The values displayed are illustrative only and **do not reflect actual charges on the platform**. {% endhint %} ### Contract Overview Displays information based on consumption cycles. #### Contract This tab displays information about the contract established with Digibee, including: * **Contract term:** Duration of the contract, including the effective and expiration dates. * **Granted:** Total amount of active credits purchased by the customer available until next unlock. * **Total commitment:** Total amount of credits under the contract. * **Next unlock:** Scheduled date when more credits become available under the contract..
#### Consumption * **Consumed vs. Prepaid Commit:** Amount of purchased credits vs. consumed credits. Consumption is cumulative and also shown as a percentage of usage. * **Incentives utilization:** Credits granted by Digibee and their expiration date. Displayed only if the customer has active incentive credit.
#### Charts and tables * **Credits usage chart:** Displays the evolution of credit consumption over time, including total contracted credits, cumulative net consumption, and monthly consumption. The current month is displayed up to the previous day. * **Credits history table:** Displays the credit type, status (active, expired, or future), granted amount, and spent amount. * **Invoice history table:** Displays the month and the remaining balance to be paid after deducting active credits from the total consumption, calculated at the standard unit price, if applicable. * **Pricing table:** Displays unit pricing for Consumption-Based metrics such as Executions, GBs, and Egress.
### Detailed Usage & Costs #### Analysis Period Select the date range and environment to analyze your usage. The tab shows a 30-day period by default. However, you can analyze a predefined range or a specific date of your choice. Costs are detailed according to the consumption metrics: * **Total cost:** Total amount of credits spent in the selected period. * **Total cost of GB-s:** Total cost and total amount of GB-s used in the selected period. * **Total cost of Executions:** Total cost and total number of executions based on the total volume of pipeline activations in the selected period. Besides the usage information, you can: * Use the **Digibee Docs button** to check more detailed information about the Consumption-Based Model in our Documentation Portal. * Use the **Download CSV button** to export your consumption reports in CSV format directly from the Platform. The exported data reflects the time period selected in the active filter, and no other filters can be applied.
#### Breakdown table After selecting the time period, you can analyze your consumption data by **projects** or by **pipelines** using the **search bar.** The table displays data by the following categories: * **Name** * **Usage in GB-s and its corresponding value** * **Executions and their corresponding value** * **Total cost.**
--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.digibee.com/documentation/licensing/licensing-models/consumption-based-model.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.