Multi-Protocol Gateway
Native support for MQTT, HTTP, and Kafka means teams can integrate without adding proxies or extra layers.
Capabilities
LeafCuttr groups the features that matter most during evaluation: how it connects, how it survives, and how it stays observable when conditions get messy.
Native support for MQTT, HTTP, and Kafka means teams can integrate without adding proxies or extra layers.
No need for external services. Schema metadata stays with the broker, keeping producers and consumers aligned as message formats evolve.
LeafCuttr runs on constrained devices with low CPU and memory usage.
Flaky networks and intermittent connectivity do not stop local streaming from continuing.
Metrics and monitoring are included out of the box, so operators can see what the broker is doing in the field.
When connectivity is available, data can sync to the cloud mothership without blocking the local workload.
This roadmap item will add lightweight transformation closer to the device so teams can cut bandwidth and keep local decisions fast.
It moves more value closer to the device, where edge teams can reduce noise before data leaves the site.