Licensing models
Learn more about the licensing models of the Digibee Integration Platform.Learn about the licensing models Digibee offers.
The Digibee Integration Platform offers various licensing models to better meet the needs of individual customers. These are:
Pipeline-based model: the first licensing model offered by Digibee, which is no longer marketed.
Subscription-based model: a model developed to replace the Pipeline-based model, with the aim of creating a clearer separation between Test and Prod environments and making it easier to scale operations.
You can find out more about the concepts used by the models below.
Concepts
Number of pipelines
Only deployed pipelines, regardless of whether they are in Test or Prod environments, are taken into account for resource consumption. Different major versions of the same pipeline are considered different and unique pipelines, and therefore each version of the pipeline may consume a different amount of resources.
The Platform doesn't set a limit on the number of pipelines you can create.
RTU
RTU stands for Runtime Unit, which means a unit of resource consumption for the deployment of a pipeline. Each deployment consumes a certain amount of RTU depending on its size.
The following table serves as a reference:
Small
1
Medium
2
Large
4
RTUs can be used for vertical and horizontal scaling of integrations. For vertical scaling, they can be used in three different sizes: Small (consumes 1 RTU), Medium (consumes 2 RTUs), and Large (consumes 4 RTUs). With horizontal scaling, each new Replica consumes the same number of RTUs as the original deployment. Each RTU is delivered with the underlying infrastructure for its operation.
Do environments consume RTUs differently?
In some plans, the RTU package includes the Prod, Test, and other environments. This means that if you have 10 RTUs and deploy 1 Small pipeline in Prod and 1 Small pipeline in Test, 2 of the 10 RTUs will be consumed and 8 RTUs will remain.
In other plans, the RTU packages are separated by environment. Let’s say you have 10 RTUs for the Prod environment and 5 RTUs for the Test environment. If you deploy 1 Small pipeline in each environment, you will have 9 RTUs for the Prod environment and 4 RTUs for the Test environment.
What happens when all RTUs are consumed?
The following algorithm is applied before each pipeline deployment in a specific environment: first, the algorithm checks if the number of individual pipelines being deployed is less than the number of available contracted pipelines.
If this is the case, the algorithm checks whether the number of available RTUs for the respective plan can accommodate the number of RTUs requested for the pipeline deployment. If this further check is successful, the pipeline is deployed.
Otherwise, the deployment fails due to either the number of available pipelines or the number of available RTUs.
Hosting Platform
The plans can be hosted in two ways:
Shared hosting: plans that use the Digibee Integration Platform hosting. Digibee is hosted by Google Cloud Platform (GCP), which means that the Platform is developed according to the Software as a Service (SaaS) model. The cloud infrastructure part of this model is the responsibility of Digibee and not the customer.
Private hosting: the customer is responsible for their own cloud infrastructure, whereby they also manage the SaaS structure. The Digibee Integration Platform offers support for many different cloud providers.
Shared or private Platform
Depending on the hosting type, the Platform works as follows:
Shared Platform: The customer uses the Digibee Integration Platform, where all accounts share the same platform and all available features. However, each user account belongs to a single realm. No data can or is exchanged between the realms. Everything is controlled by Digibee's security system.
Private Platform: With Private SaaS, only the company and Digibee have access to the Platform, on which the customer can develop and deploy their pipelines. All connectors and features of the Digibee Integration Platform are available.
Platform Usage quotas
Some plans have Platform Usage quotas, which are technical limits imposed on each realm to avoid overloading the Platform, created based on the average usage of the Platform. These are some of the limits:
Deployment size and Replicas (meaning CPU and Memory to run a pipeline or a set of replicas).
Egress Traffic Rate.
Messages that are produced/consumed.
Messages retained in the pipeline for processing.
Logs retention.
VPNs.
Object Store, Digibee Storage, and Relationship Data.
Comparison of the plans
Below is a table showing the specifics of the plans available. For more information on the details of your current plan, please refer to your contract or contact your CSM.
Pipeline-based model
Licenses
Prod and Test deployments consume the same License package.
Shared hosting
Shared Platform
Doesn’t apply
Subscription-based model
RTUs (Runtime Units)
Prod and Test deployments consume different RTU packages.
Shared hosting
Shared Platform
Uses Platform Usage quotas
Last updated
Was this helpful?