Introduction

Looking for the old Kubernetes Helm stack? See the UMH Core vs UMH Classic FAQ to understand which edition fits your project and the current migration path.

UMH Core is a single Docker container that turns any PC, VM, or edge gateway into an Industrial Data Hub.

Inside that one image you'll find:

  • Redpanda – an embedded, Kafka-compatible broker that buffers every message.

  • Benthos-UMH – a stream-processor engine with 50+ industrial connectors.

  • Agent – a Go service that reads config.yaml, launches pipelines, watches health, and phones home to the Management Console.

  • S6 Supervisor – keeps every subprocess alive and starts them in the correct order.

Why teams pick UMH Core

Benefit
What it means in practice

Simple

PLCs, sensors, ERP/MES, cloud services all talk to one Unified Namespace (UNS) instead of point-to-point spaghetti.

Lightweight

Runs on almost everything

No lock-in

100 % open-source stack: Redpanda, Benthos, S6, and much more

Key concepts at a glance

Instance
└─ Core
   β”œβ”€ Bridges           # ingest or egest data (ex-"Protocol Converters")
   β”‚   β”œβ”€ Read Flow βœ…   # read side - Available now
   β”‚   └─ Write Flow 🚧  # write side - Roadmap Item
   β”‚   └─ Connection βœ…  # monitors the network connection - Available now
   β”œβ”€ Stream Processors 🚧  # Roadmap - transforms messages inside UNS
   └─ Stand-alone Flows βœ…  # Available now
  • Bridge – connects external systems to the UNS with health monitoring. See Bridges for details. (Read flows available βœ…, Write flows in development 🚧)

  • Stream Processor 🚧 – transforms messages already inside the UNS. (Roadmap item)

  • Stand-alone Flow βœ… – point-to-point when UNS buffering isn't wanted. (Available now)

  • Connection βœ… - a continuous network check whether the external system is available. (Available now)

Typical architecture

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€ PLC / Device ───────┐
β”‚  OPC UA / Modbus / S7 / …   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
             β”‚  Bridge (Read Flow)
             β–Ό
    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
    β”‚ Unified Namespace β”‚
    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
             β”‚  Bridge (Write Flow)
             β–Ό
   MQTT broker β–Έ Cloud β–Έ Historian β–Έ Dashboards

Every message first lands in the Unified Namespace, giving you replay, buffering, and reliable data processing. MQTT Brokers, Databases, Historians, Dashboards, etc. then consume the data from that.

Getting Started

  1. Quick Setup - Get UMH Core running in minutes

  2. Unified Namespace Guide - Understand the core messaging architecture

  3. Connect Your First Device 🚧 - Bridge industrial protocols to the UNS

  4. Data Modeling 🚧 - Structure your industrial data for enterprise-scale analytics

Documentation Structure

Learn More About UNS

For deeper understanding of the concepts behind UMH Core:

Community & Support

Last updated