Devices & Edge

Device connectivity and management for new and existing equipment

Connect a new embedded product or a 20-year-old PLC. Murano IoT Connectors provision, secure, and update each device, on a platform that already connects millions of them.

Talk to a solution engineer →Read the docs

Embedded products

HTTP, MQTT

PLCs and controllers

OPC UA, Modbus, BACnet

Industrial gateways

ExoEdge, partner gateways

Wireless sensors

LoRaWAN, cellular, Wi-Fi

Other device clouds

AWS IoT Core, Azure IoT Hub

Connect devices directly, through a gateway, or from another device cloud

Direct

Your product's firmware calls the Murano HTTP or MQTT device API. There's no gateway to install, and devices can register themselves on first power-on.

Device API reference ↗ (opens in new tab)

Gateway

ExoEdge or a partner gateway on site reads PLCs, SCADA systems, and local sensors, and sends the data to Murano.

Edge gateways →

Device cloud

Devices already reporting to AWS IoT Core, Azure IoT Hub, or a LoRaWAN network are federated into Murano without firmware changes. Each keeps its own identity.

Device cloud integrations ↗ (opens in new tab)

A simple device API for embedded firmware and protocol gateways

Send data over HTTP or MQTT, from your product's firmware or from a gateway reading local equipment.

Device HTTP API ↗ (opens in new tab)Device MQTT API ↗ (opens in new tab)

# 1. Activate: the device presents its identity and receives a token
curl 'https://<IOT_CONNECTOR_FQDN>/provision/activate' \
  -d 'id=12345678'

# 2. Write data
curl 'https://<IOT_CONNECTOR_FQDN>/onep:v1/stack/alias' \
  -H 'Authorization: token <token>' \
  -d 'data_in={"001":73.16}'

# 1. Activate: publish to $provision/12345678 and receive a token

# 2. Write data
mosquitto_pub -h <IOT_CONNECTOR_FQDN> -p 8883 \
  --cafile Exosite_Root_CA_RSA_2048.pem \
  -i '12345678' -u '12345678' -P '<token>' \
  -t '$resource/data_in' -m '{"001":73.16}'

Edge software and gateways

ExoEdge

Exosite's edge software for Linux gateways and industrial computers. It reads Modbus TCP and RTU, OPC UA, BACnet, CANopen, J1939, and MQTT, including SCADA tags over OPC UA, with read-only access to the control system.

Configure channels remotely from ExoSense
Update ExoEdge and its sources in the field
Add protocols with plug-in sources
Buffer data offline and send it with the original timestamps
Provision and activate on first connection

ExoEdge docs ↗

Gateway hardware from many vendors

Exosite is hardware agnostic. Gateways and edge computers from our hardware partners connect out of the box or with a small amount of configuration, and we can help connect the gateway you already use.

Hardware partners →Hardware integration guides ↗ (opens in new tab)

Device fleet management

Provision devices securely

Choose each device's identity format and how it authenticates: token, password, or TLS client certificate, with root CA options. Add devices in bulk from a CSV, let them register on first connection, or allow provisioning only from your factory network.

Over-the-air firmware and configuration updates

Upload a firmware or configuration package, apply it to one device or many, and follow each device as it reports progress and its installed version.

See the status of every device

Connection status, IP address, tags, and last report time across the fleet. Debug logs show authentication and TLS failures, and a misbehaving device can be locked.

Know where each device is and what it runs

Each device shows its customer and site, when and from where it last reported, and the software package it's running.

Claim and reassign devices

New devices wait as unclaimed until someone assigns them to a customer group. Reassign them when equipment changes hands.

Configure many devices at once

Save a device's channel configuration as a versioned template and apply it across the fleet.

Send settings and commands

Send setpoints and settings within allowed ranges, with optional acknowledgement from the device.

Device management docs ↗

Connectivity for equipment in the field

Device-initiated connections

Devices open every connection over TLS, so they work behind customer firewalls without any inbound ports.

Store-and-forward buffering

When the connection drops, ExoEdge and device clients store data locally and send it later. Each record keeps the time it was measured.

Files to and from devices

Send firmware and configuration files down. Devices can upload logs, high-resolution data, or images, up to 100 MB per file.

Device API encryption requirements ↗ (opens in new tab)Device HTTP API ↗ (opens in new tab)Device MQTT API ↗ (opens in new tab)

Talk with us about connecting your devices

Tell us about your equipment, and we'll recommend the connection path and hardware that fit.

Talk to a solution engineer →Next: Data Management