Subscription Based model

Learn how the subscription licensing model works in the Digibee Integration Platform

The Subscription-Based Model is the most commonly used licensing model in the Digibee Integration Platform. It is based on a basic license unit called a Pipeline Subscription, which provides access to the platform’s infrastructure, support, and customer success services.

This model is ideal for organizations that understand their integration needs and can plan their capacity requirements in advance.

License structure

A Pipeline Subscription includes Runtime Units (RTUs), which are used to scale pipelines either:

• Vertically (based on pipeline size), or

• Horizontally (based on the number of replicas).

Each Pipeline Subscription includes:

• 2 RTUs for deployments in the production environment

• 1 RTU for deployments in the test environment

Any non-production environment (such as homolog) is counted as a test environment for license calculations, regardless of the licensing model. Test and production RTUs are not interchangeable.

You can purchase as many Pipeline Subscriptions as needed to match your company’s usage. Each pipeline can be deployed in either test or production environments, as long as you have enough available subscriptions and RTUs.

• Each integration flow can have only one active major version per environment at a time.

• Different major versions of the same pipeline are treated as separate pipelines and require separate subscriptions.

• You can create unlimited pipelines, but deployment depends on the number of Pipeline Subscriptions and RTUs available.

Hosting and infrastructure

The Subscription-Based Model uses a shared platform (shared hosting). All customers share the same infrastructure and platform resources. However, each customer account belongs to a unique realm.

There is no data sharing between realms, and all access is governed by Digibee's security policies.

License consumption

RTU consumption depends on the pipeline size and number of replicas. The following table outlines RTU usage by deployment size:

Size	Consumed RTUs
Small	1
Medium	2
Large	4

Each replica of a pipeline consumes the same number of RTUs as the initial deployment size. So, total RTU consumption = pipeline size RTUs × number of replicas.

Usage examples

Example 1: Deploying a new pipeline

You have 10 pipeline subscriptions and 20 RTUs in production. You deploy a large pipeline (4 RTUs) in production.

• Subscriptions used: 1

• RTUs consumed: 4

• Remaining: 9 subscriptions, 16 RTUs

Example 2: Medium pipeline in test environment, with 2 replicas

• Size: Medium (2 RTUs per instance)

• Environment: Test

• Replicas: 2

• Calculation: 2 replicas × 2 RTUs = 4 Test RTUs

• Consumption:

  • 1 pipeline subscription

  • 4 Test RTUs

Example 3: Large pipeline in production, with 3 replicas

• Size: Large (4 RTUs per instance)

• Environment: Production

• Replicas: 3

• Calculation: 3 × 4 = 12 Production RTUs

• Consumption:

  • 1 pipeline subscription

  • 12 Production RTUs

Example 4: Two pipelines with different major versions

• Scenario: Pipeline A v1.0 and Pipeline A v2.0 are both deployed in production

• Each version is treated as a separate pipeline

• Consumption:

  • 2 pipeline subscriptions

  • RTUs per version depend on their respective deployment size and replica count.