Module Store
The Module Store is your central catalog of all modules available in Tricloud Nexus. It allows you to browse, search, and filter modules, making it easy to find the components you need to extend your architecture. Whether you are looking for a connector to a new protocol, an in-house developed application, or third-party infrastructure services, the Module Store provides a single place to discover and manage them.
Browsing Modules

The main grid in the Module Store displays all modules currently available. Each module card contains key details such as:
Name and Publisher – e.g., Tricloud, Microsoft, Apache Foundation, etc.
Type - The type defines the overall type of the module.
System module - The module is an essential module for any Edge device installation
Platform module - The module is part of Nexus platform and is available as part of any installation
Custom module - Any custom Module imported that is not a System- or Platform module
Category The category classifies the functional purpose of the module.
General Module - General modules category includes modules that extend the functionality like third party containers imported from docker hub or other repositories. General modules can provide miscellaneous functionalities such as data transformation, custom analytics, or device management features tailored to specific use cases.
Nexus Data Connector - Nexus data connector modules are responsible for collecting data from various sensors, devices, or external systems in the field. They acquire, preprocess, and transmit data to the edge or cloud for further processing and analysis. Nexus data connector modules can be configured on an area in a hierarchy.
Hub/Orchestrator - Hub/Orchestrator modules act as a central point of communication and coordination between different edge modules. They manage the flow of data and control between modules, ensuring proper execution of tasks and overall system performance. Examples of such modules are MQTT Broker, Kafka or NodeRed.
Data Storage - Data Storage modules provide local storage capabilities on the edge device. They store the data collected from data connector modules for short or long term retention, enabling faster data access and reducing data transfer costs to the cloud. Examples of such modules are SQLServer, BlobStorage, RedisCache etc.
Analytical Model - Analytical modules can contain analytical models (machine learning, AI models or other types) that have been trained in the cloud or on-premises. They perform inferencing or predictions on the edge device, making real-time decisions based on the data collected by Nexus data connector modules. Models can be configured on an asset in a hierarchy.
Location Determines whether the modules is internal or external.
Internal - the module is developed and hosted by your organization and is hosted in a container registry configured in platform settings
External - the module is imported from an external public repository such as dockerhub
Version – The latest imported version of the module
Selecting a module card will display additional information in the Details panel on the right, including description, image reference, version selector, and access to module settings.
Search and Filter Capabilities
At the top of the page, several filter options make it easier to locate the right module:
Search – Quickly find modules by name or keyword
Publisher filter – Narrow down modules by publisher (e.g., Microsoft, Tricloud, Apache Foundation)
Type filter – Focus on modules by type, such as System, Platform- or Custom Module
Category filter – Find modules by their functional category such as Data Connector, Data Storage, or Hub/Orchestrator etc.
Location filter – Choose between Internal (in-house modules) or External (third-party modules).
These filters can be combined for precise navigation of large module catalogs.
Next Steps
Once you’ve found the modules you need in the Module Store, the next steps typically include:
Import a new Module Add a completely new module to your Module Store, either from a public container registry like Docker Hub or from your organization’s internal registry.
Import a new Version of a Module Keep your modules up to date with the latest features, performance improvements, and security patches by importing newer versions. These can then be rolled out to devices via the Update Center.
Edit Module Settings Adjust configuration parameters for a module directly in Nexus, tailoring its behavior to your deployment needs.
Last updated
Was this helpful?