Introduction
The contracting and pricing model of Cumulocity is referred to as Commit-to-Consume (CTC). In the CTC model, customers do not have an explicit bill of materials for all their purchased Cumulocity components. Instead, customers commit to a certain spend amount, and their actual consumption of Cumulocity components draws down this commitment over the duration of the contract. The CTC model gives customers flexibility with Cumulocity’s offerings, allowing them to optimize consumption, try new features, and understand usage.
Given that the spend amount is drawn down by usage each month, it is important for customers to have transparency with their usage and consumption details. The Console application is a new application within Cumulocity where customers on the CTC model can view their usage and consumption.
The Console application is in Private Preview, that is, it is not enabled by default and may be subject to change in the future. This application is subscribed to your tenant if you are on the new CTC model. If you are unable to access this application, please contact product support to request the application subscription for your tenant.
At this time, the Console application is not supported on Dedicated environments. This will be enabled soon.
To use the Console application, you need:
- The Console application and stratos-client microservice subscribed to your tenant.
- READ permission for the permission type “Console”.
Glossary
This glossary provides definitions for key terms and concepts used throughout this documentation.
Add-ons
A part of the new pricing model comprising any additional features, functionality, or components used within Cumulocity. Includes components such as Cumulocity DataHub, additional tenants, custom domains, and more. A complete list of add-ons is found in the product catalog addendum of the contract.
Commit-to-Consume (CTC)
The new contract type enacted by Cumulocity in 2025 where customers commit to a spend amount (commitment), and monthly usage draws down against this spend amount. If the spend amount runs out before the contract expiry date, the customer enters overage scenarios.
Commitment
The total pre-tax spend credit for Cumulocity products and services that the customer has contractually agreed to pay. This balance is drawn down each month based on the customer’s consumption.
Console application
A Cumulocity-built solution that sits within the product and acts as a one-stop shop solution for customers interacting with their subscription and usage data. The Console application provides transparency with usage and billing to customers on a CTC contract.
Consumption
The details relating to the drawdown amounts and how much of the commitment remains after each month. The monthly consumption report available in the Console application gives a breakdown of all components used, their associated prices and quantities, and statistics on the remaining balance.
Drawdown
The process of calculating a customer’s monthly consumption of services (at pre-tax rates) and deducting that from their remaining commitment balance.
Environment
An individual instance of Cumulocity. Customers can have multiple environments for their account, including both Dedicated (Private) SaaS environments and Public SaaS environments. For drawdown purposes, usage is aggregated across all the environments.
Overage
The status a customer enters when their commitment has been fully depleted before their contract term has ended. The exact specifics of the overage scenario are determined by the clauses listed in the respective contracts, and are different from customer to customer.
Product catalog
The customer-specific price list appended to a CTC contract that defines the pre-tax rates for all available Cumulocity products and services.
Stratos
The Cumulocity internal project name for the Console application and any of the associated backend services.
Usage
Statistics and other data points on the usage of Cumulocity. Usage is collected per tenant on a monthly basis and is available within the Console application for analysis. Usage data is also available via the Usage Statistics APIs.