---
title: Licensing
description: Check the Integrations licensing models
documentId: ipaas-licensing
locale: en-US
---

Check how the Sensedia Integrations licensing model works.

We currently offer 2 licensing models:

- [Model based on the number of deployed flows](#model-based-on-the-number-of-deployed-flows)
- [Model based on computational unit](#model-based-on-computational-unit)

## Model based on the number of deployed flows

- In this model, billing is according to the number of active flows, that is, with "Deployed" status, in Staging and Production environments.


<Callout type="IMPORTANT" title="IMPORTANT">

The same flow deployed in 2 environments (Staging and Production) counts as 2 licensing units.
</Callout>

- Additionally, there is an analysis of the complexity of deployed flows, which may impact the final licensing value. Read more about this below.

### Simple flow example

* The system receives a request containing data in JSON format, deserializes this data and extracts the customer ID. 
* Then, it makes a call to a REST API to get additional information about the customer, storing the response for later use. 
* Based on the customer information, the system makes a SOAP call to get details of associated orders, converting the response from XML to JSON. 
* The customer data and order details are then combined into a single JSON object, and a JSLT script is applied to transform the data as needed. 
* The final data is sent to MongoDB via REST API. 
* If any failure occurs in data persistence, an error message is published to a Kafka topic. 
* At the end of the process, the system returns an HTTP 200 OK status to confirm the operation's success.

*Components*

* 3 HTTPS connectors (REST and SOAP)
* 3 transformation steps with a simple payload (50 kb)
* 1 connector with some application (Kafka)
* 1 connector with some application (MongoDB)
* Data enrichment
* Exception handling

### Complex flow example

* The system receives a request and extracts the ID of each customer from the JSON data. 
* The data is split into individual items, which are processed in parallel. 
* For each item, information such as ID, name, and value is logged and used to create a new JSON.
* Then, a call is made to a REST API to get additional information about each customer, and the response is stored for later use. 
* Based on the data returned about the orders, the system makes a SOAP call to retrieve order details associated with the customer, converting the response from XML to JSON. 
* The enriched customer data and order details are combined into a single JSON object, and a JSLT script is applied to transform this data. 
* The final data is sent to MongoDB via REST API. If any failure occurs in data persistence, an error message is published to a Kafka topic. 
* At the end of the process, the system returns an HTTP 200 OK status, confirming that the operation was successful.

*Components*

* 3 HTTPS connectors (REST and SOAP)
* *Payload of 500 kb or larger*
* *1 Split for iterations over a list with parallel processing*
* *Parallel processing (Multicast)*
* 3 transformation steps with a large payload
* Poll Enrich/Enrich (Data enrichment)
* 1 connector with some application (Kafka)
* 1 connector with some application (MongoDB)

## Model based on computational unit

In this model there is no limit on the number of flows, but there is a minimum resource to deploy the integration.


For more information about our licensing models, contact Sensedia's sales team.