An agent at the edge. A cloud for the fleet.
ConHive splits cleanly into two halves: an agent that runs on every device, and a cloud that manages the fleet. The intelligence lives at the edge; the cloud gives you oversight and control.
A modular runtime on every device.
The ConHive Agent captures, analyses and automates on the device itself. It's composed of independent modules — you enable only what a device needs.
A handful of core modules form the runtime; sensing, automation and management modules layer on top. Each is enabled per device, so a node stays as small as its job.
+ sensing, monitoring & management modules · enabled per device
Oversight and control — not where your logic runs.
The ConHive Cloud manages devices, auth, and projects, and gives you a fleet-wide view. It connects to each agent; it doesn't run your device logic.
Register, group and operate every device from one place.
Organise fleets into projects with role-based access.
Monitor state, metrics and alerts across every site.
If the cloud is unreachable, a device keeps sensing and acting. The edge doesn't depend on it to function.
One platform, every device profile.
About 47 modules, each independently enabled or disabled without affecting the others. One unit is a sensor node; another is a gateway — same platform, different module set.
Amber = enabled · grey = available, off — toggle per device, no redeploy of the platform
Wire signals to actions in a visual editor.
The Automation Manager is a drag-and-drop flow engine — and every module contributes its own nodes. Build a flow, test it in a sandbox, deploy it to a device, and watch it run.
A radar node detects presence → a condition node checks time of day → a notification node alerts the on-call team. No code.
The agent captures and analyses a signal on-device.
Wire the signal through nodes in the visual editor — no code.
Trigger an alert, a notification, or a command across the agent.
One definition generates the whole platform.
A single YAML definition generates the Go backend, the TS/React frontend, the protobuf/gRPC/HTTP APIs, the docs, and the flow nodes — from one source of truth. The API reference always matches the implementation, and new modules arrive consistent.
module: acoustic capabilities: - capture - analyze - events nodes: auto api: grpc + http
Role-based access on every operation.
Permissions are scoped by role across the platform, and the API surface is documented — so governance is explicit, not implied.
Read-only access to fleet state, metrics and flows.
Build and deploy flows, configure modules on devices.
Manage projects, members, access and registration.
Looking for the hardware?
ConHive is the software platform. divVoice GmbH, the operator of ConHive, also develops acoustic sensor hardware — see the hardware range on divvoice.de.
Want to see the architecture applied to your fleet?
We'll walk you through the agent, the cloud and the flow engine on your use case.