Pipeline Based model

Learn more about how the pipeline-based licensing model works on Digibee Integration Platform

The Pipeline-based licensing model was the first licensing model offered by Digibee to its customers. This licensing model 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, at least 10 licenses are offered per customer, with each license including 1 Pipeline and 1 RTU (Runtime Unit). Each deployment consumes 1 license. You can create as many pipelines as you want, but you only consume them when you deploy.

Hosting and infrastructure

The Pipeline-based model uses a shared platform (shared hosting), in which all customers share the same infrastructure and all available resources. However, each user account belongs to a single realm. Data cannot be shared between realms and all information is controlled by Digibee's security system.

License consumption

In the pipeline-based model 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. In the Pipeline-based model, you can see a graph showing the number of pipelines deployed in Prod and Test and the Licenses consumed in both environments.

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.

On the Run screen during deployment, a modal is displayed showing how much will be consumed and how many licenses will remain available after the deployment.

Usage examples

It is important to adapt the usage to the company's infrastructure and business needs. One pipeline entitles you to one license, which corresponds to a Small Runtime slot. The deployment sizes offered by the Digibee Integration Platform are, in this case:

• Small (1 RTU or 1 license)

• Medium (2 RTUs or 2 licenses)

• Large (4 RTUs or 4 licenses).

For example, in this model, if out of 10 Pipelines, one has to be used in the Large size (4 RTUs), only 7 flows will be covered in 10 RTUs, assuming always the same environment, as we can see below:

In this case, you would need to buy more licenses to continue using the remaining flows.