> 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-models/pipeline-based-model.md).
# Pipeline-Based Model
Learn more about how the pipeline-based licensing model works on Digibee Integration Platform
The **Pipeline-Based Model** was the first licensing model offered by Digibee to its customers. It is still used by some customers, but is no longer commercially available. This model is ideal for organizations that need cost predictability based on the number of pipelines, rather than the volume of usage.
## License structure
In the Pipeline-Based Model, resource consumption is measured in **licenses**. Each pipeline deployment — whether in a Production or Test environment — consumes the same license, with no distinction between environments.
In this model, a minimum of **10 licenses** must be acquired. Each license includes 1 Pipeline and 1 RTU (Runtime Unit). A license is consumed with each deployment, and only deployed pipelines consume licenses.
## Hosting and infrastructure
The Pipeline-Based Model uses a multi-tenant platform, where all customers share the same infrastructure and all available resources. However, each user account is assigned to a specific realm. Data is not shared across realms, and all information is protected by Digibee's security system.
## License consumption
In the **Runtime Compute** page, you can track your usage and manage the pipelines and licenses available in your realm.
The billing is directly related to the number of licensed pipelines, regardless of the execution load or volume of data processed. The consumption chart shows the number of pipelines deployed in Prod and Test and the Licenses consumed in both environments.
{% hint style="info" %}
Any environment that is not Production (such as Homolog) will be counted as a Test environment for license calculation purposes, regardless of the license model.
{% endhint %}
When deploying a pipeline on the Run page, a modal will be displayed showing how much will be consumed and how many licenses will remain available after the deployment.
## Usage examples
It’s important to adapt the license usage to your company's infrastructure and business needs. In this model, each pipeline corresponds to one license, which is equivalent to a Small Runtime slot.
The deployment sizes offered by the Digibee Integration Platform are:
* Small: 1 RTU (1 license)
* Medium: 2 RTUs(2 licenses)
* Large: 4 RTUs (4 licenses)
For example, if you have to deploy 10 pipelines and decide to deploy one in the Large size (4 RTUs), only 7 pipelines will be covered in 10 RTUs, assuming all are running the same environment. See the example below:
In this case, you would need to purchase additional licenses to deploy the remaining pipelines.
---
# 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-models/pipeline-based-model.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.
