Licensing

Learn how the Sensedia Integrations licensing model works.

We currently offer two licensing models:

Model based on the number of deployed flows

In this model, billing is based on the number of active flows, that is, those with "Deployed" status, in the Staging and Production environments.

The same flow deployed in two environments (Staging and Production) counts as two licensing units.

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

The system receives a request containing data in JSON format, deserializes this data, and extracts the customer ID.
Next, it makes a call to a REST API to obtain additional customer information, storing the response for later use.
Based on the customer information, the system makes a SOAP call to retrieve 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 during 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 was successful.

Components

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 obtain additional information about each customer, and the response is stored for later use.
Based on the returned order data, the system makes a SOAP call to retrieve details of orders 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 during 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 the operation was successful.

Components

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

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

Thanks for your feedback!

EDIT