ConHive is built to extend.
Modules, APIs, docs, and automation nodes are generated from a single definition — so adding a capability is fast and the whole platform stays consistent.
One definition. Every output — generated.
Write a single YAML definition. ConHive generates the Go backend, the TS/React frontend, protobuf gRPC/HTTP APIs, documentation, and automation flow nodes. Change the definition; everything updates. You never edit generated files by hand.
module: acoustic capabilities: - capture - analyze - events nodes: auto api: grpc + http
A module is a self-contained capability unit.
Each module declares its services, methods (with roles), optional flow nodes, and config schema. Enable or disable per device — the agent loads only what a given device needs.
Typed services & methods
Declare gRPC service definitions with method-level role annotations. The generator emits the full protobuf + Go implementation stubs.
Role-based access built in
Every method carries a role: read, write, or admin. Auth enforcement is generated, not hand-rolled — it stays consistent as the module evolves.
Optional node contributions
Set "nodes: auto" in the definition and the generator creates drag-and-drop nodes for every signal and action the module exposes.
Typed config schema
Module config is declared in YAML and validated at agent startup. Enable or disable the entire module per device through fleet management.
The platform ships with ~47 agent modules — each defined this way. Browsing their docs shows the full pattern in production.
Browse modulesEvery module extends the visual flow engine.
When a module declares nodes, the generator creates typed input/output ports for each signal and action. Build flows in the visual editor, test them against a live agent, and deploy to a device or a whole fleet.
Nodes are generated from the same definition — they never drift from the API.
Generated APIs with a consistent surface.
Every module exposes a generated protobuf API served over gRPC and HTTP. An OpenAPI spec is generated alongside — connect any system without hand-maintained wrappers.
Every service is served over gRPC and a generated HTTP/JSON gateway. Pick the transport that fits your integration.
The OpenAPI spec is generated from the same definition as the implementation — it cannot drift. Use it for code generation or interactive exploration.
Method-level role enforcement is generated alongside the API. No custom auth middleware — every endpoint is covered by the same mechanism.
Building on ConHive? Let's talk integration.
We can walk through how the generated model fits your architecture and what a custom module looks like end-to-end.