# What is Litmus Edge? Features, integrations and alternatives > Source: https://netray.co/software/litmus-edge > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Manufacturing Software Encyclopedia ## Short answer Litmus Edge is an industrial edge data platform from Litmus that connects to machines and controllers, normalises their data and forwards it to other systems such as MES, historians, cloud platforms and analytics tools. It is run at the plant on edge hardware or virtual machines and managed centrally across sites. ## Vendor Litmus ## Category integration-data ## Aliases - Litmus Automation Edge - Litmus Edge platform - Litmus Edge Manager ## Overview Litmus Edge focuses on the data layer at the plant edge. It connects to equipment through industrial drivers and protocols, models the data, applies processing such as filtering or calculations, and delivers it to destinations over standard interfaces such as MQTT and databases. The aim is a consistent, governed data flow rather than point to point integrations. Typical users are OT and IT teams in multi-site manufacturers that want one pattern for getting machine data to cloud, MES and analytics tools. A management layer is used to deploy and configure edge instances across plants, which helps when dozens of sites need the same data standards. In a manufacturing stack it overlaps with device connectivity products such as Kepware and with parts of IIoT platforms, while not replacing MES, historian or ERP. Teams often compare it with Kepware, Ignition and cloud edge services. The deciding factors are usually protocol coverage, central management, deployment model and how much application building is wanted. ## Best For - Multi-site manufacturers that need a standard way to move machine data to cloud and enterprise systems - Teams modernising brownfield plants with mixed controllers - OT and IT groups wanting centrally managed edge instances - Companies feeding data lakes and analytics platforms with normalised machine data - Organisations wanting a vendor neutral layer between equipment and cloud platforms ## Modules ### Device connectivity **Description:** Drivers and protocol support for connecting to PLCs, CNCs, sensors and other industrial equipment. ### Data modelling and processing **Description:** Tools to structure, normalise, filter and calculate on incoming data before it is forwarded. ### Data forwarding **Description:** Connectors that deliver data over MQTT, databases and other interfaces to MES, historians and cloud services. ### Containers and applications **Description:** Support for running containerised applications and analytics at the edge alongside the core data flows. ### Central management **Description:** A management product to deploy, configure and monitor many edge instances across sites. ### Digital twin and context **Description:** Capabilities to organise equipment data into models that add context for downstream consumers. ## Deployment Deployed at the edge on industrial PCs, servers or virtual machines in the plant, with central management available for multiple sites. Specific supported hardware and virtualisation platforms should be confirmed with the vendor. ## Integrations ### Industrial protocols **Detail:** Connects to controllers and servers using drivers and standards such as OPC UA and others, depending on the version. ### MQTT and messaging **Detail:** Publishes normalised data to MQTT brokers and similar messaging systems used by IIoT and cloud platforms. ### Cloud platforms **Detail:** Forwards data to cloud services such as AWS, Azure and Google cloud offerings and to data platforms. ### Databases and historians **Detail:** Writes to relational databases and integrates with historians and analytics tools. ### MES and ERP **Detail:** Feeds MES or integration middleware, which then handles production reporting to ERP. ### APIs **Detail:** Provides APIs for configuration and data access to support automated deployments. ## Strengths - Edge centric design suits plants with intermittent connectivity or latency needs - Central management helps standardise configuration across many sites - Vendor neutral position between equipment and multiple cloud or enterprise targets - Can host containerised apps and analytics at the edge - Reduces point to point integrations by normalising data once ## Limitations - Not an ERP, MES or historian, so those roles still need other products - Driver coverage for unusual or very old equipment should be verified case by case - Overlaps with other connectivity and IIoT tools, so architecture decisions need care - Requires governance of data models, or standards drift between plants - Smaller vendor ecosystem than some large platform providers ## Alternatives - Kepware KEPServerEX - Ignition (Inductive Automation) - AWS IoT SiteWise with SiteWise Edge - PTC ThingWorx - Siemens Insights Hub with Industrial Edge - HighByte Intelligence Hub ## Ai Opportunities - Generating tag mappings and data models from PLC exports and equipment documentation - Running anomaly detection or quality models at the edge on live machine data - Detecting drift or missing signals across many sites from configuration and data patterns - Delivering clean, labelled machine data to private language models and analytics tools - Answering questions about which machines publish which signals using the model catalogue ## Selection Tips - Inventory every controller type and protocol and test the drivers on real machines - Decide what runs at the edge versus central cloud before choosing hardware - Define the data model and naming standard centrally before rolling out to sites - Check security features, user management and network segmentation fit your OT policy - Compare against the connectivity your SCADA or MES vendor already provides - Pilot one plant with a measurable use case and a clear destination system ## Faq ### What is Litmus Edge? **Answer:** Litmus Edge is an industrial edge data platform. It connects to PLCs and machines, normalises and processes their data, and forwards it to MES, historians, cloud platforms and analytics tools. It runs at the plant and can be managed centrally across many sites. ### How does Litmus Edge compare with Kepware? **Answer:** Both connect to industrial equipment. Kepware is primarily a connectivity server exposing tags, often via OPC UA, while Litmus Edge positions itself as a broader edge data platform with modelling, processing, forwarding and central management. The best fit depends on your architecture and how much you want in one product. ### Does Litmus Edge replace MES? **Answer:** No. It moves and shapes machine data but does not manage work orders, routings or genealogy. It commonly feeds an MES, historian or cloud analytics platform, which then handles execution, reporting and any posting to the ERP system. ### Can Litmus Edge run in an air-gapped plant? **Answer:** Because it runs at the edge on customer hardware, local operation is possible, and some deployments avoid cloud use. Confirm with the vendor which features, licensing and update processes work without external connectivity for your version. ### How does Litmus Edge help with AI projects? **Answer:** AI projects need clean, consistent, labelled machine data. Litmus Edge can normalise data from different equipment and deliver it to analytics and model environments, or run lightweight models at the edge. It supplies the data foundation rather than the AI models themselves. ## Search terms what is litmus edge, litmus edge alternatives, litmus edge vs kepware, litmus edge mqtt, litmus edge manager, industrial edge data platform, litmus edge plc connectivity, litmus edge api, litmus edge vs ignition --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json