IN Brief:
- SUSE Industrial Edge combines SUSE runtime infrastructure with Losant’s industrial IoT platform.
- The platform supports industrial protocols including OPC UA, MQTT, Modbus, and BACnet.
- Industrial edge platforms are converging around Kubernetes, device management, low-code workflows, and operational data integration.
SUSE has launched SUSE Industrial Edge, integrating Losant’s industrial IoT platform into its edge portfolio following the company’s acquisition of Losant earlier this year.
The platform combines SUSE runtime infrastructure with Losant’s application and workflow capabilities, creating an industrial edge stack for distributed environments such as production facilities, power plants, ships, retail estates, and buildings. It is built to connect operational data and enterprise systems across sites where devices, control systems, dashboards, and IT services often remain separated by vendor, protocol, and deployment model.
SUSE Industrial Edge includes low-code and no-code tools for building workflows and applications, alongside dashboards for site-level and multi-site operational awareness. The system supports application templates, anomaly alerts, performance comparison tools, and integration with enterprise IT systems.
The platform normalises data from operational sources including Siemens and Beckhoff systems, HVAC equipment, kiosks, compute infrastructure, ship engines, and OPC UA sources. Protocol support includes OPC UA, MQTT, Modbus, BACnet, and other industrial interfaces.
The architecture is built around Kubernetes. Losant operates as a Kubernetes application, with SUSE providing the runtime through its Linux and Kubernetes stack. The application layer sits above the operating system and orchestration layer, using independently scalable and stateless services including NGINX load balancers, Mosca message brokers, RabbitMQ queuing systems, workflow runners, and data processors. Time-series data is stored using TimescaleDB, supported by MongoDB document databases and Redis clusters.
The deployment model supports both on-premises and cloud-based operation. In one model, a gateway collects local data before synchronising with higher-level systems. In another, devices such as smart meters connect directly to the cloud. Large deployments can handle tens of thousands of devices distributed across regions, with dashboards showing device status and location while keeping customer data separated.
Industrial edge computing has moved well beyond local data buffering. Plants, infrastructure operators, transport systems, and distributed estates now need software update control, protocol translation, analytics, device management, and operational visibility across mixed equipment. Many sites contain layers of automation installed over decades, and the edge platform has to connect existing systems without forcing a wholesale replacement of the control stack.
Kubernetes gives software teams a consistent deployment model, but industrial environments bring constraints that conventional IT platforms do not always address. Field systems must tolerate intermittent connectivity, long hardware refresh cycles, cautious change-control processes, and strict separation between operational technology and enterprise IT. Protocol support, data normalisation, local workflow execution, and fleet-level observability determine whether the platform can function in production rather than only in a demonstration environment.
The launch also shows the growing overlap between embedded systems, industrial automation, and enterprise software. Edge gateways, sensors, PLC-connected equipment, cloud dashboards, and application services are increasingly part of the same architecture. Design decisions now extend across security, updateability, observability, serviceability, and long-term maintainability, with the edge device acting as a managed part of a wider system rather than a fixed appliance.
