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
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
Quick Setup - Get UMH Core running in minutes
Unified Namespace Guide - Understand the core messaging architecture
Connect Your First Device π§ - Bridge industrial protocols to the UNS
Data Modeling π§ - Structure your industrial data for enterprise-scale analytics
Documentation Structure
Usage Guides - Step-by-step implementation guides
Unified Namespace - Core messaging architecture
Data Modeling π§ - Enterprise data structuring
Data Flows - Connect and process data streams
Production Deployment - Scaling, security, and operations
Reference Documentation - Complete API and configuration reference
Learn More About UNS
For deeper understanding of the concepts behind UMH Core:
The Unified Namespace Course Series - 4-chapter comprehensive course
Chapter 1: OT Foundations - Automation pyramid challenges
Chapter 2: The Rise of UNS - Core architecture principles
Chapter 3: IT Foundations - Modern IT patterns
Industrial IoT Architecture - Edge computing in manufacturing
MQTT vs UNS Comparison - Why data contracts matter
Community & Support
Discord Community - Get help and connect with other users
GitHub Repository - Source code and issue tracking
Management Console - Web-based configuration and monitoring
UMH Website - Company and product information
Last updated