Integrations
What Hermetry connects to
Devices and field networks, your own software, the channels your team reads and the AI assistants they use. Each entry links to the documentation that shows how it works.
Devices and networks
Devices connect the way they can
Whatever a device can do, there is a way in: a live connection, a message now and then, a radio, or a gateway that speaks for it.
MQTT 3.1.1
Devices keep one TLS connection on port 8883, send readings and receive commands and settings at once.
HTTPS device API
One POST per message for devices that wake, send and sleep. Commands wait for them in a long poll.
LoRaWAN network server
Built in, with OTAA and ABP, Class A and Class C, and Basics Station gateways or licensed routers.
LoRaWAN codecs
106 codecs for common sensors turn each frame into named values. Your own codecs are JSON tables, never code.
Devices behind a gateway
A gateway reports for its field devices, up to 500 by default, and each one appears as its own device.
The topics your firmware uses
Profiles accept legacy compatible topics or topics of your own, so existing firmware keeps its topic names.
Device certificates
Devices can sign in with X.509 certificates issued by Hermetry’s own device certificate authority.
Field and site equipment
Equipment that cannot dial in
Meters, controllers, UPSs and cameras are read where they are: on site by Hermetry Edge, or polled by the platform.
Modbus RTU and Modbus TCP
Hermetry Edge on a licensed gateway or router reads Modbus over RS485 or the site network. Protocols depend on the model.
OPC UA and BACnet/IP
OPC UA servers and BACnet/IP devices on the site network are read by Hermetry Edge and appear as child devices.
SNMP
The platform polls UPSs, switches, servers and printers by OID over SNMPv3, or v2c when an administrator allows it.
IP cameras and recorders
Live H.264 video on device pages and dashboards, pulled only while someone watches and never stored.
Cellular and eSIM
Routers on a mobile link protect your data allowance. Administrators manage a router’s eSIM profiles from Hermetry.
Router web panels
Open a licensed router’s own web panel through its outbound tunnel, with no fixed IP address and no open ports.
Your systems
Your software, in both directions
Your systems call Hermetry, Hermetry calls them when something happens, and flows forward data as it arrives.
REST API
Devices, readings, commands, alarms, assets, rules, dashboards and flows, with keys that hold only the permissions you give them.
Webhooks
Signed HTTPS calls when a device goes offline, an alarm opens or a command ends. CloudEvents 1.0 if you prefer it.
HTTP request from a flow
Call an HTTPS API as data arrives, with basic, bearer, header, OAuth 2 client credentials or AWS Signature V4 sign-in.
Your own MQTT broker
A flow’s MQTT out block publishes messages to a broker you run, with retries and an idempotency key.
History API
The latest values and the history of any key, for your ERP, data warehouse or reporting tool.
CSV and Excel
Dashboard cards download what they show as CSV or Excel (.xlsx), in the board’s current time window.
Organisation export
An owner downloads the whole organisation as one JSON file: devices, settings, members and more.
Notifications
Reach people where they are
Alarms and flows notify people in the app, by e-mail, by text, by push and in the chat apps they already use.
Alarm and flow notifications to any address, through the platform’s mail service or your own SMTP server.
SMS
Text messages to the phone numbers a flow names, through the platform’s provider or your own.
Browser and app push
A notification with a link to the alarm, on every browser and app install a member has registered.
Telegram, Slack, Discord and WhatsApp
An administrator connects the chat app once. Each member links their own account and gets notifications as messages.
Mobile app
Alarms, approvals and live device values on your phone, with a second person approving critical steps.
Sign-in
Your identity provider
People sign in with their company account, and leavers lose access when you switch them off in your directory.
SAML 2.0 and OpenID Connect
Each organisation connects its own identity provider, so members sign in with their company account.
SCIM 2.0
Members are kept in step with your directory: someone you switch off there loses access here.
AI assistants
Assistants that read your data
An AI assistant that supports MCP can answer questions about your devices, readings, alarms and dashboards, with the rights of the person who connected it.
MCP servers
Devices, telemetry, alarms and dashboards each have an MCP server. They are off until an administrator switches them on.
A second person for changes
An assistant can acknowledge an alarm. Clearing one waits until a second person approves the call.
Missing a connection?
Tell us what you need to connect. Most devices and systems reach Hermetry over MQTT, HTTPS or a flow’s HTTP request.

