Constrained devices
Devices are constrained by CPU, memory, and storage, so cloud-first stacks quickly become too heavy to run where the data starts.
Kafka-compatible. Lightweight. Built for flaky networks, constrained devices, and high-volume edge data.
$ docker pull leafcuttr/leafcuttr:latest
Modern data streaming tools weren’t built for the edge.
Devices are constrained by CPU, memory, and storage, so cloud-first stacks quickly become too heavy to run where the data starts.
Networks are intermittent, flaky, and often expensive to depend on for every message, every time.
Bandwidth is expensive, data is high-volume but low signal, and teams are forced to push cloud-first architectures into environments where they do not fit.
Existing systems are too heavy and complex, and they fail when the edge stops behaving like a data center.
LeafCuttr is a lightweight, Kafka-compatible streaming platform built specifically for edge environments.
Kafka-compatible. Integrate without changing your existing ecosystem.
Runs close to the data. LeafCuttr sits at the edge, where buffering, aggregation, and forwarding can happen efficiently even when conditions are unreliable.
Buffer → Aggregate → Forward. Keep data local, shape it intelligently, and forward only what matters upstream.
LeafCuttr delivers Kafka compatibility, multi-protocol ingestion, resilience, schema registry, observability, and async replication for edge teams.
Fully compatible with the Kafka protocol so teams can integrate without reworking their existing ecosystem.
Native support for MQTT, HTTP, and Kafka, with no need for proxies or additional layers.
Runs on constrained devices with low CPU and memory usage.
Handles flaky networks and intermittent connectivity without collapsing the local pipeline.
No external service required to keep schemas aligned as message formats evolve.
Metrics and monitoring are part of the product, not something you bolt on later.
Async replication keeps data moving upstream when connectivity is available, without blocking local streaming.
Workflow
LeafCuttr keeps data close to the source, survives bad networks, and forwards only the signals that matter upstream.
LeafCuttr runs on edge devices or gateways close to where data is generated.
It accepts MQTT, HTTP, and Kafka traffic from devices and local applications.
When networks fail, LeafCuttr keeps buffering locally instead of dropping the flow.
Data can be shaped at the edge so downstream systems receive less noise and more signal.
LeafCuttr forwards to central cloud systems when connectivity returns and capacity allows.
There is no constant connectivity requirement and no large distributed cluster to keep alive at the edge.
INPUT → MQTT, HTTP, Kafka
EDGE → buffer, aggregate, filter
UPSTREAM → forward when connectivity returns
Where it fits
Leafcuttr fits the places where cloud-first stacks break down: low bandwidth, intermittent networks, and devices that need to keep running even when the connection does not.
Industrial
Process machine data locally with minimal latency, even in plants with unreliable connectivity and constrained hardware.
Buildings
Handle distributed sensor data efficiently across floors, sites, and building systems.
Retail
Keep stores in sync with dependable local buffering and remote delivery when connectivity returns.
Video
Manage high-volume streams at the edge without forcing every byte upstream.
Mobility
Stream data through unstable networks while vehicles are in motion and routes are changing.
Robotics
Enable real-time decisions without depending on a cloud round trip for every event.
Proof
We’re collaborating with early adopters to refine LeafCuttr for real-world use cases.