Trust

Open connectivity. Bring your stack.

ELIAN talks to most of the field protocols you already use, and exposes a clean REST and webhook layer for everything else. Anything that speaks HTTP, MQTT, or one of our eight edge protocols is in scope today.

Trust

Field-side protocols

Protocol adapters run as lightweight pods on the edge gateway. One adapter per protocol; per-device protocol settings.

01

Modbus TCP / RTU

Pull holding / input registers from PLCs, BMS controllers and meters. Per-register polling intervals; signed and unsigned 16/32-bit support.

02

OPC-UA

Subscribe to existing SCADA tag namespaces. Browse the address space from the admin UI; pin tags to ELIAN sensors.

03

LoRaWAN

Webhook-based ingestion from The Things Network and ChirpStack. Per-LNS configuration, per-device decoder support.

04

BACnet/IP

Ingest building-management signals (HVAC, lighting, occupancy). Read-only by default.

05

M-Bus

Wired meter-bus for water, heat and energy meters. Periodic polling with at-least-once semantics.

06

BLE GATT

Bluetooth-LE characteristic reads from beacons and sensors via the gateway’s built-in radio.

07

Zigbee

Through Zigbee2MQTT — every device the project supports works.

08

KNXnet/IP

Building-control bus for European installations.

Trust

Cloud-side protocols

For cloud-native devices and your own integrations.

01

REST

Devices POST readings with API-key auth (header or body). Per-device primary & secondary keys, bcrypt-hashed, rotatable from the UI.

02

MQTT

Native broker (Mosquitto) on topics like `elian/<org>/telemetry` and `elian/<org>/vision/events`. External pub/sub supported.

03

CoAP

Lightweight UDP for constrained devices.

04

Webhooks (in)

Trigger workflows from external systems with a per-workflow URL and shared secret.

05

Webhooks (out)

Workflow actions can fire arbitrary HTTPS POSTs with template-rendered bodies.

Trust

Notification & messaging

Alerts and reports go out through gateways you can swap.

01

Email

Azure Communication Services as primary path with O365 SMTP fallback. Multi-language templates.

02

SMS

Twilio, Vonage, MessageBird or Azure Communication Services. E.164 validation, per-notifier event-type filters, per-user quiet hours (critical alerts override).

03

In-app notifications

Real-time WebSocket delivery to the Notification Center. 13+ categories with per-category email / in-app toggles per user.

A clean bridge to the rest of your stack.

Outbound webhooks fire arbitrary HTTPS POSTs with template-rendered bodies. The public REST API exposes every entity. Together they cover the bridge to ticketing tools, ERP, CMMS, chat platforms and anything else your team already runs — we’re happy to walk through the specific integration shape you need.

Ready to connect your operations?