---
title: "Composable MES: Build Apps Around Your MES | FlowFuse • FlowFuse"
description: "Build a composable MES with FlowFuse: AI-assisted, low-code apps and MES integration that work alongside the system you already run, without replacing it."
canonical_url: "https://flowfuse.com/use-cases/mes/"
meta:
  "og:description": "Build a composable MES with FlowFuse: AI-assisted, low-code apps and MES integration that work alongside the system you already run, without replacing it."
  "og:image": "https://flowfuse.com/images/use-cases/mes/platform-home.webp"
  "og:title": "Composable MES: Build Apps Around Your MES | FlowFuse"
---

> Index of every page on this site: [llms.txt](https://flowfuse.com/llms.txt)

# **Keep your MES. **Make it composable.

FlowFuse engineers work alongside your team to deliver the first application, one costly problem at a time, and leave you a foundation your team can run and extend across every plant.

[**Talk to Us**](https://flowfuse.com/book-demo/) [**View Pricing**](https://flowfuse.com/pricing/)

No rip and replace. Start with one line, then scale to every plant.

![Diagram: FlowFuse sits between the shop floor and your MES. PLCs, machines, sensors, SCADA and legacy systems feed apps built with FlowFuse, such as OEE dashboards, andon calls, quality checks, operator screens, production tracking, shift reports, maintenance alerts and energy monitoring, deployed to every plant and exchanging data with your MES, which stays the system of record](https://flowfuse.com/images/use-cases/mes/composable-mes-hero.webp)

## MES integration without touching the core.

FlowFuse connects to MES platforms over the interfaces they already expose: [APIs](https://flowfuse.com/docs/node-red/integration-technologies/rest/), [databases](https://flowfuse.com/docs/node-red/database/), file exchange, and [MQTT](https://flowfuse.com/blog/2024/06/how-to-use-mqtt-in-node-red/). Define who owns each record, [validate payloads](https://flowfuse.com/blog/2025/06/structuring-storing-data-mes-integration/), and control any write-back to production systems.

- ![Siemens Opcenter](https://flowfuse.com/images/mes-logos/siemens-logo.svg "Siemens Opcenter")
- ![Rockwell Automation Plex](https://flowfuse.com/images/mes-logos/rockwell-automation-logo.svg "Rockwell Automation Plex")
- ![SAP Digital Manufacturing](https://flowfuse.com/images/mes-logos/sap-logo.svg "SAP Digital Manufacturing")
- ![AVEVA MES](https://flowfuse.com/images/mes-logos/aveva-logo.svg "AVEVA MES")
- ![Critical Manufacturing MES](https://flowfuse.com/images/mes-logos/critical-manufacturing-logo.svg "Critical Manufacturing MES")
- ![Dassault Systèmes DELMIA Apriso](https://flowfuse.com/images/mes-logos/dassault-systemes-logo.svg "Dassault Systèmes DELMIA Apriso")
- ![GE Vernova Proficy](https://flowfuse.com/images/mes-logos/ge-vernova-logo.svg "GE Vernova Proficy")
- ![Tulip](https://flowfuse.com/images/mes-logos/tulip-logo.svg "Tulip")

[See all integrations](https://flowfuse.com/integrations/)

## Composable MES: Your MES + FlowFuse are better together.

Your MES is the system of record, and it should stay that way. Most software vendors want to become your system of everything. We don't. Here's how the work splits.

| **Area** | **Your MES** | **FlowFuse** |
| --- | --- | --- |
| **Role** | System of record for orders, routing, genealogy, and validated records | The application layer around it: [integrations](https://flowfuse.com/integrations/), operator apps, and line-specific workflows |
| **Data** | Production records and transactions | Live machine data, collected and [shaped](https://flowfuse.com/blog/2025/06/structuring-storing-data-mes-integration/), then handed to the MES |
| **Changes** | Kept standard, with vendor-managed upgrades | Built and changed by your own team, with AI, and approved before going live |
| **Deployment** | Per your vendor's architecture | [Hosted and edge instances](https://flowfuse.com/product/edge/) managed from one platform, across every site |
| **AI** | Varies by vendor | [FlowFuse Expert](https://flowfuse.com/ai/) (our Built-in AI) plus MCP integration with the agents your company already approved, scoped by team and logged |

Capabilities vary by MES vendor, edition, and configuration.

## Don't replace your MES. Build around it.

There's always a machine that doesn't fit the standard, [a legacy device the MES can't talk to](https://flowfuse.com/use-cases/shop-floor-communication/), or [an operator screen that takes three weeks to learn](https://flowfuse.com/platform/dashboard/). We work with your team to build those customizations as applications around the MES, so its core stays standard, and your team can run and extend them across every plant.

### **Connect what the MES can't**

Bring in data from PLCs, [legacy devices](https://flowfuse.com/platform/device-agent/), and other systems over [OPC UA](https://flowfuse.com/integrations/opcua/), [Modbus](https://flowfuse.com/integrations/node-red-contrib-modbus/), [MQTT](https://flowfuse.com/docs/user/mqtt-nodes/), Sparkplug B, REST, and more, then hand it to the MES in the format it expects.

[Browse integrations](https://flowfuse.com/integrations/)

### **Describe it, and AI builds it with you**

Tell FlowFuse's [built-in AI](https://flowfuse.com/ai/) what the line needs, such as [live OEE](https://flowfuse.com/blueprints/manufacturing/oee-dashboard/), [andon calls](https://flowfuse.com/blueprints/manufacturing/andon-system/), or a [quality check](https://flowfuse.com/blog/2026/07/defect-and-quality-monitoring/) at the machine. It builds the first version of the logic and the operator screens in [FlowFuse Dashboard](https://flowfuse.com/platform/dashboard/), explains flows you inherited, and writes custom code. Nothing changes until your team approves it.

[Learn about FlowFuse AI and see how it builds apps](https://flowfuse.com/ai/)

### **Reuse it across sites**

Version applications, [promote them through pipelines](https://flowfuse.com/docs/user/devops-pipelines/), and [deploy to every line and plant from one place](https://flowfuse.com/use-cases/remote-device-management/).

[Explore the FlowFuse platform](https://flowfuse.com/platform/why-flowfuse/)

### **Connect the AI you already use**

[Bring the agent your company has already approved](https://flowfuse.com/blog/2026/09/industrial-ai-agent/), such as Microsoft Copilot, ChatGPT, or Claude, or run a local model so nothing leaves your network. Agents reach only the teams you allow, and every action is logged.

[Read how to connect an industrial AI agent to FlowFuse](https://flowfuse.com/blog/2026/09/industrial-ai-agent/)

**From real conversations**

## What manufacturers say about changing their MES

From discovery calls with manufacturing teams, shared anonymously.

> ***“Suppliers say, okay, this is possible. But when you try to change it — oh, it costs millions.” ***

***Application manager** Regulated manufacturer*

> ***“If you have ever worked with MES, there is nothing standard. All MES systems are custom.” ***

***Digital manufacturing lead** Building-products manufacturer*

> ***“We've spent over 12 months implementing our MES, I'm too scared to spend more time to customize it. But I need value now, so customizations have to be easy.” ***

***Operations lead** Automotive supplier*

01/03

## Built for Enterprise Manufacturing

FlowFuse is SOC 2 Type I and Type II certified, with role-based access control, single sign-on, audit logging, and air-gapped, self-hosted deployment options, built for the security and compliance requirements of large-scale manufacturing organizations.

[Review our security and compliance details](https://flowfuse.com/platform/security/)

SOC 2 Type II

Single Sign-On

Audit Logs

Role-Based Access Control

Air-Gapped / Self-Hosted Deployment

## Composable MES: FAQs

Clear answers for teams deciding what belongs in the MES and what belongs around it.

###

###

###

###

###

###

###

**Build the app your MES is missing.**

Bring one real use case: a line that doesn't fit, a system the MES can't reach, or a screen operators avoid. We'll bring an engineer and work out the first step together.

[**Talk to Us**](https://flowfuse.com/book-demo/)

```json
{"@context":"https://schema.org","@graph":[{"@id":"https://flowfuse.com/#website","@type":"WebSite","description":"FlowFuse builds your first industrial solution with your team, proves it at one plant, then helps you roll it out to every plant, faster each time.","inLanguage":"en","name":"FlowFuse","url":"https://flowfuse.com/","alternateName":["FlowForge","Flow Fuse"],"publisher":{"@id":"https://flowfuse.com/#identity"}},{"@id":"https://flowfuse.com/use-cases/mes/#webpage","description":"Build a composable MES with FlowFuse: AI-assisted, low-code apps and MES integration that work alongside the system you already run, without replacing it.","name":"Composable MES: Build Apps Around Your MES | FlowFuse","url":"https://flowfuse.com/use-cases/mes/","@type":["WebPage","FAQPage"],"isPartOf":{"@id":"https://flowfuse.com/#website"},"mainEntity":[{"@id":"https://flowfuse.com/use-cases/mes/#/schema/question/1"},{"@id":"https://flowfuse.com/use-cases/mes/#/schema/question/2"},{"@id":"https://flowfuse.com/use-cases/mes/#/schema/question/3"},{"@id":"https://flowfuse.com/use-cases/mes/#/schema/question/4"},{"@id":"https://flowfuse.com/use-cases/mes/#/schema/question/5"},{"@id":"https://flowfuse.com/use-cases/mes/#/schema/question/6"},{"@id":"https://flowfuse.com/use-cases/mes/#/schema/question/7"}],"potentialAction":[{"@type":"ReadAction","target":["https://flowfuse.com/use-cases/mes/"]}],"primaryImageOfPage":{"@id":"https://flowfuse.com/#logo"}},{"@id":"https://flowfuse.com/#identity","@type":"Organization","legalName":"FlowFuse Inc.","name":"FlowFuse","url":"https://flowfuse.com","alternateName":["FlowForge","Flow Fuse"],"logo":{"@id":"https://flowfuse.com/#logo"},"sameAs":["https://twitter.com/FlowFuseinc","https://github.com/FlowFuse","https://www.linkedin.com/company/flowfuse/","https://www.facebook.com/FlowFuse/","https://www.youtube.com/channel/UCbBzP8NZbv3WDtlt4UouA-g"]},{"@id":"https://flowfuse.com/use-cases/mes/#/schema/question/1","@type":"Question","inLanguage":"en","name":"Is FlowFuse an MES alternative?","acceptedAnswer":{"@type":"Answer","text":"No, and we don't want to be. Most software vendors want you to standardize on their platform. We'd rather you keep the MES you spent years implementing. For order management, genealogy, and validated records, it should stay. FlowFuse is how teams make an MES composable: the standard core stays in place, and the line-specific pieces are built as separate applications your team controls. Teams without an MES often start the same way, building OEE tracking or shift reporting as individual apps, and decide on MES scope later."}},{"@id":"https://flowfuse.com/use-cases/mes/#/schema/question/2","@type":"Question","inLanguage":"en","name":"How does FlowFuse use AI?","acceptedAnswer":{"@type":"Answer","text":"FlowFuse Expert, the AI built into the platform, builds flows from a plain-language description, explains flows your team inherited, writes custom code, and answers questions about what's running on the floor. Every change waits for your approval. You can also connect the AI agents your company already uses, such as Microsoft Copilot, ChatGPT, or Claude, or a local model so nothing leaves your network. Agents reach only the teams you allow, and every action is logged. Inside your applications, AI agents can work with live production data, and you can run your own models at the edge."}},{"@id":"https://flowfuse.com/use-cases/mes/#/schema/question/3","@type":"Question","inLanguage":"en","name":"How does MES integration work with FlowFuse?","acceptedAnswer":{"@type":"Answer","text":"The right integration path depends on what your MES exposes. Common options are REST or SOAP APIs, database connections, file exchanges, and MQTT. FlowFuse connects to these alongside equipment protocols such as OPC UA and Modbus."}},{"@id":"https://flowfuse.com/use-cases/mes/#/schema/question/4","@type":"Question","inLanguage":"en","name":"What is a composable MES?","acceptedAnswer":{"@type":"Answer","text":"A composable MES approach pairs a standard core with smaller, purpose-built applications for the needs that core doesn't cover, rather than relying on one vendor for everything. FlowFuse is a platform for building and managing those applications."}},{"@id":"https://flowfuse.com/use-cases/mes/#/schema/question/5","@type":"Question","inLanguage":"en","name":"Do we need an MES before using FlowFuse?","acceptedAnswer":{"@type":"Answer","text":"No. Some teams start with data collection and reporting, such as replacing paper shift reports, and decide on MES scope later. Others build the MES functions they need, such as production tracking, data collection, or resource management, as individual applications and add more over time. Because FlowFuse is built on open-source Node-RED, it gives you an open-source path to MES functionality without vendor lock-in."}},{"@id":"https://flowfuse.com/use-cases/mes/#/schema/question/6","@type":"Question","inLanguage":"en","name":"Will this disrupt our MES rollout?","acceptedAnswer":{"@type":"Answer","text":"No. A gradual evaluation can start with one application on one line while the MES project continues."}},{"@id":"https://flowfuse.com/use-cases/mes/#/schema/question/7","@type":"Question","inLanguage":"en","name":"What is FlowFuse built on?","acceptedAnswer":{"@type":"Answer","text":"FlowFuse is built on Node-RED, the open-source, low-code platform widely used in industrial automation. FlowFuse adds what production use requires: built-in AI, team collaboration, version control, deployment pipelines, role-based access, audit logs, and management of applications across sites."}},{"@id":"https://flowfuse.com/#logo","@type":"ImageObject","caption":"FlowFuse","contentUrl":"https://flowfuse.com/handbook/images/logos/ff-logo--square--dark.png","inLanguage":"en","url":"https://flowfuse.com/handbook/images/logos/ff-logo--square--dark.png"}]}
```

## Sitemap

See the full [sitemap](https://flowfuse.com/sitemap.md) for all pages.
