Murano Glossary

This section presents the various terminology use on this documentation page & by Exosite & Murano sites.

Platform Overview


A Murano Application is a type of Murano Solution targeting end-user access, and device monitoring page. Typically a Murano Application contains a web-site with dashboards for user to manage & monitor owned devices and an API for mobile Apps access. ExoHome and ExoSense are examples of Exosite provided Murano Applications.

An application can connect and consumes data from one or many IoT-Connectors at the same time.

Learn more about Application


An ExoSense Asset is a digital twins of a physical setup specific to the ExoSense Application. An asset can group Channels from various device sensors from potentially different IoT-Connectors into a single entity.

Not to be confused with Web Asset files managed by the Murano Asset Micro-Service.


A Exosite Business is an account on the Exosite IoT-platform. The business contains:

Learn more about Exosite Business


An ExoSense Channel is a the representation of a device sensor specific to the ExoSense Application. Channels are defined in Murano IoT-Connectors for each devices using the Config IO connectivity resource.

Learn more about Channel configuration.


A Cloud-Connector is a special type of Murano IoT-Connector including capability to fetch device data from a 3rd party APIs where physical IoT Devices are Typically connected. Cloud-Connectors enable Murano Applications to consumed data from devices already connected to other services such as AWS-IoT or Sigfox in a transparent manner.

Learn more about Cloud-Connectors


See Service Config

Config IO

The Config_IO contains the data model definition of ExoSense Application Channels. The Config_io is stored as resource in each device in the IoT-Connector.

Learn more about Config_IO


A Connector-As-A-Service is a special type of Murano IoT-Connector including multi-tenant capability. It enables devices connected to an IoT-Connector to be consumed securely by multiple Murano or external Applications from different Exosite Businesses. Each exposed device are claimed and owned by a single user.

Connector-As-A-Service provides an API for external application to consume device data as well as an OEM branded web-interface for user to claim and manage owned devices.

Learn more about Connectors-As-A-Service


Murano Content files are a static private file hosted on Murano using the Murano Content micro-service. Files hosted securely and private and made accessible using authenticated URLs. Content files can be uploaded and managed by Murano Solution scripting, Murano User interface or through the Murano HTTP device API.

Not to be confused with Web-Assets which are public static files dedicated for website dependencies.


A device is the representation of a physical client connected to Murano (a smart object, a mobile device, a gateway or a custom application) using the Device APIs and belonging to a Murano IoT-Connectors. Within IoT-Connectors, devices are managed by the Murano Device2 micro-service. On Murano, a Device holds the connectivity settings (like its credentials) and the state of resources being transmitted from & to the physical device.


An Exchange Element is an item on the Exosite Exchange IoT-Marketplace. Elements can be published and consumed by different Murano business.

An Exchange element can be of one of the following types:


A Solution WebService Endpoint is a public Web-Service API element handling incoming HTTP requests to a Murano Solution. Endpoints have dedicated scripting functions powered by the Murano WebService Micro-Service. Those functions are automatically compiled into an Event-Handler and can be defined as part of a Solution Template.

Murano Endpoints handle common HTTP methods as well as WebSocket connectivity through the WebSocket Micro-Service. As well an Endpoint can serve a static Web Asset file and handle secure authentication for the end-users.

Endpoints are the common way for Murano Applications to expose their website & APIs.


A Micro-Service Event is message sent by a Murano Micro-Service to Murano scripting which executes the related Event Handler function if available.

Find all events on the Murano Services Reference page

Event Handler

A Solution Scripting Event Handler is a Lua scripting function executed when a Murano Micro-Service triggers an event. Find all events on the Murano Services Reference page

Event handler function can call Scripting Modules for code re-usability. Event handlers belong to a single Murano Solution and can be defined in a Solution Template.

Learn more about Scripting Event Handlers


The Exosite Exchange IoT-Marketplace is a place to find and publish elements to build IoT solutions.

Learn more about Exosite Exchange IoT-Marketplace


One of the main Exosite Applications dedicated for end consumer Home Automation products.

Learn more about ExoHome (need login)


One of the main Exosite Applications dedicated for industrial monitoring.

Learn more about ExoSense


The Murano HTTP is one of the communication protocols supported by Murano device connectivity APIs. The HTTP protocol is a setting of Murano IoT-Connectors and is powered by the Murano Device2 micro-service.

The Murano HTTP API is compatible with the legacy One-Platform API.

Learn more about Murano HTTP API


See Exchange.


An IoT-Connector is a type of Murano Solution targeting device connectivity and authentication. An IoT-Connector contains a device-api settings along with a unique connectivity sub-domain.

An IoT-Connector can be consumed by one or many Murano Applications at the same time.

Learn more about IoT-Connectors


See Modules


A Solution Scripting Module is a re-usable Lua scripting code file which can be used by many Event handler functions. Modules help a better code organization and can be organized in a tree structure. Modules belongs to a single Murano Solution and can be defined in a Solution Template.

Learn more about Solution Modules


The Murano MQTT is one of the communication protocols supported by Murano device connectivity APIs. The MQTT protocol is a setting of Murano IoT-Connectors and is powered by the Murano Device2 micro-service.

Learn more about Murano MQTT API


The legacy Exosite IoT-Platform. One-Platform is being deprecated and customers should use (or migrate to) the compatible Murano HTTP interface instead.

Learn more about One-Plateform


A standard for defining Http APIs. Murano utilize Open-API version 2 for publishing and consuming Murano Services. As well an OpenApi definition is automatically generated for Murano Applications by the Murano Webservice micro-service.


Over-The-Air update is a mechanism to update device source code, firmware or configuration files remotely with or without requirement of user action. Murano IoT-Connectors provides building blocks for easy OTA management including:


Stands for Product-As-a-Service, Aka Connector-As-A-Service.


User interface for the legacy One-Platform.


Technical term for IoT-Connector.


See Connector-As-A-Service.


An IoT-Connector Resource is a device connectivity state definition. Defined globally for all devices in an IoT-Connector, a resource defines the data type and how the sensor data are transmitted to & from the client device.

Resources are powered by the Murano Device2 Micro-Service.

Learn more about Connector Resources


See Endpoint


Murano Scripting is a servier-less programming environment using the LUA language. The scripting is used to consume Murano Micro-Services in order to build Web Applications as Murano Solutions.

Scripting execution are always trigger by a Micro-Service event. Murano Micro-Services

Learn more about Murano Scripting


A Murano Solution is a combined set of configured Murano Micro-Services consumed by a server less scripting Both Applications and IoT-Connectors are Murano Solutions with different set of configured services. A solution can use a Github Template to be deployed to Murano.

A solution belongs to an Exosite Business an is managed by its users.

Learn more about Murano Solution development


Murano Micro-Service are APIs exposed & integrated to Murano using the Open-API v2 standard and consumed by Murano Scripting to add functionalities to Murano Solutions.

Services exposes:

Services can be published on Exosite Exchange which host various existing Services elements including Exosite Native Core Services and other 3rd party APIs.

Learn more about Murano Micro-Services

Service Config

A Solution Service Configuration is a subscription from a Murano Solution to a Murano Micro-Service. It contains configuration parameters, such as security credentials for the solution to consume the service. Parameters definition are available on the Native Micro-Services Reference pages and can be set from Murano User-Interface.

Service configuration belongs to a single Murano Solution and can be defined in a Solution Template.

Learn more about Solution Service Configuration


Old name for Open-API


A Github Solution Template is a set of default Murano Service Configuration and Scripting (Modules, Endpoints & Event-Handlers) usable to create multiple instances of Murano Solutions (both applications and IoT-Connectors) ready for end-user to use.

Template can be published on Exosite Exchange which host various existing template elements including Exosite supported applications ExoHome and ExoSense.

Learn more about Github Solution Template


Web-Assets are public static files hosted by the Murano Asset micro-service on the public API exposed by the Murano Webservice micro-service usually used by Murano Application.

Web Assets are not supposed to change at run-time and should only change at application update or release. But can also be managed from Murano UI.

Not to be confused with Content files which are private files dynamically managed.