Everything composes.
ConHive's capabilities come from independent modules — about 47 of them — that you enable per device. Here's what they do, grouped by what you're trying to achieve.
Six themes. Forty-seven modules.
Each theme covers a distinct job. Compose exactly the themes a device needs — one unit can be a pure acoustic sensor node; another a fully managed gateway.
Sense
Capture and interpret the physical world. Sensing modules run analysis on-device — the agent detects events before the cloud sees them.
Automate
Turn signals into action, no code required. Wire sensor outputs to commands and notifications in a visual drag-and-drop flow editor.
Monitor & alert
Know what's happening across the fleet. Collect metrics and logs at the edge; trigger multi-channel alerts when thresholds are crossed.
Manage devices
Operate the fleet with confidence. Control software, files, processes and power state across every device from the cloud console.
Connect
Link edge to cloud to external systems. Secure registration, streaming and network bridging keep every device reachable and synchronised.
Model & visualise
Live state and on-device UI. Maintain a digital twin of the device, track events and surface them through a managed interface.
Six themes, one agent.
Every module belongs to a theme. A device runs the themes it needs — nothing more is loaded.
Theme counts are representative.
One platform. Every configuration.
A device only runs the modules it needs. One unit is an acoustic sensor node; another is a gateway managing a fleet. Same platform, same agent runtime, different composition.
New capabilities are modules — built once, consistent everywhere.
Add a module from a single YAML definition and the platform generates its backend, frontend, APIs, docs, and flow nodes automatically.
Not sure which modules fit your use case?
Let's map it out. Tell us what you're sensing and we'll show you which themes compose into the agent you need.