Licensing: Main concepts

Learn about the main concepts about licensing on Digibee Integration Platform

Understanding how licensing works is essential for making the most of the Digibee Integration Platform. This document introduces the main licensing concepts, helping you better manage usage and ensure your organization stays compliant with licensing agreements.

Key concepts

To choose the most suitable license model for your business and correctly monitor usage, it’s important to understand how licensing works in the Digibee Integration Platform.

Number of pipelines

There is no limit to how many pipelines you can create in the Digibee Integration Platform. However, only deployed pipelines (whether in Test or Prod environments) are counted toward resource usage.

The more deployed pipelines you have, the greater your consumption.

Different major versions of the same pipeline are considered unique pipelines.Each version may consume a different amount of resources.

Runtime Unit (RTU)

RTU is the unit of measurement for resource consumption when deploying a pipeline. Each deployment consumes a specific number of RTUs depending on the pipeline size.

RTUs support both vertical and horizontal scaling of integrations:

• Vertical scaling: Consumption depends on the size of the pipeline.

• Horizontal scaling: Each additional replica consumes the same number of RTUs as the original deployment.

Each RTU is delivered with the underlying infrastructure for its operation.

The following table serves as a reference:

Pipeline size	RTU consumption
Small	1
Medium	2
Large	4

Shared or Private platform

SaaS (Software as a Service) is a software delivery model in which the software is hosted in the cloud and accessed over the internet. The Digibee Integration Platform offers two hosting options:

• Shared hosting (Public SaaS): All accounts share the same platform and features, but each account belongs to a unique realm. No data is shared between realms. All access is governed by Digibee’s security system.

• Private hosting (Dedicated SaaS): Only your company and Digibee have access to a dedicated environment. You can build and deploy pipelines with the same set of features and connectors available on the shared platform.

To learn more, visit the Platform Hosting documentation.

Platform usage quotas

Platform usage quotas are technical limits applied to each realm to maintain platform stability. These limits are based on average usage patterns and include:

• Deployment size and number of replicas (CPU and memory)

• Egress traffic rate

• Number of produced/consumed messages

• Messages retained for processing

• Log retention

• VPN connections Storage usage (Object Store, Digibee Storage, and Relationship Data)

Licensing models

Digibee currently offers three licensing models:

• Pipeline-based model

  • Consumption is based on the number of deployed pipelines, with no distinction between environments.

  • This model is no longer available for new purchases but is still fully supported for existing customers.

• Subscription-based model

  • Consumption is based on RTUs, with separate RTU packages for production and test environments.

  • This allows better control over resource usage per environment.

• Consumption based model

  • Consumption is measured using multiple metrics, including:

    • GB-seconds (GB-s)

    • Egress traffic

    • Pipeline executions

Consumption based model exclusive concepts

The following concepts apply only to the Consumption-Based Licensing Model:

GB-seconds (GB-s)

Represents the total memory usage of a pipeline replica over time. It’s calculated by multiplying the memory allocated (in GB) by the duration the instance is running (in seconds).

Overage

Overage happens when you exceed your allocated credit limit. Pipelines will continue running, but any usage beyond your original commitment is billed separately at an overage rate applied to all consumption metrics.

Pipeline executions

Represents the number of times a pipeline is executed.

Egress traffic

Refers to all data that exits the Digibee Integration Platform—whether to the public internet, other clouds, or on-premise networks.

Autoscaling

Autoscaling automatically adjusts the number of active replicas based on the workload. Replicas are created or removed depending on the number of messages in the queue (invocations).