> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/licensing/licensing-consumption/license-usage.md).
# Runtime Compute
Learn more about your consumption works on the Digibee Integration Platform.
On the **Runtime Compute** page, you can better manage and track your deployed pipelines and consumption. This applies to all Digibee licensing models: **Subscription-based, Pipeline-based and Consumption-based**.
{% hint style="info" %}
To view license information, the user must have the `LICENSE:READ` permission. For more information about permissions, see the [documentation](/documentation/platform-administration/administration/new-access-control/access-control-roles/list-of-permissions-by-service.md).
{% endhint %}
## Licensing on Digibee Integration Platform
To access the **Runtime Compute** page:
1. Click **Administration** in the upper right corner of the Platform home page
2. Click **Runtime Compute** under Licensing on the left side menu.
The information on this page varies according to your licensing model. If you have any doubts or questions about the information on your screen, feel free to contact your CSM.
Below you can see how the pages for each of the license models are displayed in the Digibee Integration Platform:
### Pipeline-based model
In the Pipeline-based model, you can see a chart showing the number of pipelines deployed in Prod and Test and the Licenses consumed in both environments.
### Subscription-based model
In the Subscription-based model, you can see a chart showing the number of pipelines deployed in Prod and the RTUs consumed in Prod, as well as the number of pipelines deployed in Test and the number of RTUs consumed in Test.
### Consumption-based model
In the Consumption-based model, the charts show the amount spent per month on the individual metrics in relation to the total credits purchased. These charts are updated frequently so you can have full control over your credit’s usage.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.digibee.com/documentation/licensing/licensing-consumption/license-usage.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
