[ELASTIC Demo Series] Propeller – Lightweight Orchestration Beyond Kubernetes

This episode of the ELASTIC Demo Series presents Propeller, a WebAssembly-based orchestrator that supports running application logic from cloud systems down to small edge and IoT devices. The demo walks through how Propeller deploys WebAssembly modules, manages events and executes workloads in a lightweight and consistent way across different environments.

Propeller is built on top of SuperMQ, a message distribution layer that enables devices, services and applications to communicate through a publish–subscribe model. This foundation allows Propeller to distribute Wasm workloads reliably across systems with very different resource capacities. The project has been partly supported by the ELASTIC initiative.

What Propeller aims to solve

Deploying application logic on distributed systems often requires separate tools for cloud, edge and embedded devices. These environments vary in compute power, memory limits and operating systems. Traditional container-based orchestration works well in a data-centre but becomes heavy on constrained devices.
Propeller takes a different approach. It uses WebAssembly modules as deployable units. These modules are small, predictable and portable, and can run on servers, gateways, micro-nodes and even microcontrollers when supported.

What the demo shows

The demo explains how a user prepares an application as a Wasm module, registers it in Propeller and deploys it through the system. It also shows how Propeller:

  • uses SuperMQ channels to deliver messages and trigger logic

  • loads Wasm modules when needed and applies defined rules

  • evaluates conditions and executes functions on demand

  • keeps the runtime small and predictable on devices

  • distributes logic without the need for containers or large runtimes

The video highlights how rules and workflows are expressed, how they react to events and how state can be passed between components. This provides a practical view of how Propeller behaves in real conditions.

Core characteristics of Propeller

WebAssembly execution model

Propeller runs user-defined functions packaged as Wasm modules. These modules remain portable across different CPU architectures and operating systems, as long as a compatible Wasm runtime is available.

Event-based orchestration

Logic is not executed continuously. Instead, Propeller reacts to messages published through SuperMQ or other triggers. This helps avoid unnecessary resource use and suits distributed systems where activity is irregular.

Cloud-to-edge consistency

The same Wasm module can be deployed on a server, an edge gateway or a smaller device, creating a uniform execution model. Developers do not need to create separate builds or manage different deployment paths.

Lightweight footprint

Because WebAssembly modules are small and runtimes are compact compared to container stacks, Propeller is suitable for constrained hardware. This supports use-cases where memory, CPU or power must be conserved.

Rules engine

Propeller includes a rules engine that allows developers to define how messages, conditions and modules relate. This provides a clean way to build flows and decision logic without writing custom orchestration code.

Why it matters for ELASTIC

ELASTIC is focused on technologies that support distributed, efficient, multi-tier execution across future 6G-ready infrastructures. Propeller fits into this vision by showing how application logic can run closer to devices, reduce overhead and maintain consistency without depending on heavy container runtimes.

The demo illustrates how such tools can help future systems offload tasks to nearby nodes, respond faster to events and reduce cloud back-and-forth communication.

How to try Propeller

Users interested in experimenting with Propeller can:

  • review the open-source code on GitHub (https://github.com/absmach/propeller)

  • build a sample WebAssembly module using the supported toolchain

  • publish messages through SuperMQ and observe how Propeller reacts

  • deploy modules on different hardware to compare behaviour

  • explore the rules engine to define conditions and reactions

This helps demonstrate how Propeller behaves in both cloud and edge environments and how Wasm workloads can be coordinated without traditional container pipelines.

Future work

The Propeller team is continuing to expand runtime support, improve documentation, and broaden compatibility with more Wasm environments, including runtimes suited for microcontrollers and very small devices.
Additional work is also planned around monitoring, rule validation and deployment tooling to make the orchestrator easier to integrate into existing platforms.