Architecture

how is mantsu built? mantsu is a modular, macro service manufacturing execution system (mes) designed for industrial plant environments it is built as an orchestrated, containerized application that is able to run cloud native and/or on premises containers are grouped into kubernetes managed nodes to enable scalable, resilient deployments the architecture is intentionally adaptive the set of deployed nodes and services is determined by the size, ot complexity, and continuity requirements of the target plant a small plant may run a minimal configuration with a single lightweight ot edge node; a large plant may operate a fully clustered deployment with agentic data processing and an enterprise data lake integration mantsu uses a mixture of low code (mendix) and high code it offers code templates that are built to specification of the customer usage of templates assures that most recurring features are already developed and usable this allows a fast deployment of a mvp further customization to your specifications is done through the low code platform and ai assisted high code development this allows a fast iteration cycle the final built will be owned by the customer this means that you will own the code base and you will own the data there is no vendor lock in what are the guiding design principles? service orchestration each service is made responsible for a functional domain (execution, product quality, master data, etc ); functional objects are exchanged between services but the responsible service keeps the single source of truth unified namespace (uns) all data (from ot machine streams to it business events) flows is setup with the uns architecture; making plant data discoverable, contextualized, and available to all authorized consumers without point to point connections event driven integration business events flow through a kafka compatible streaming broker, decoupling producers from consumers scalability nodes can be added, clustered, or omitted based on customer specific requirements without architectural redesign ot it separation the boundary between operational technology and it networks is included in the architecture; mantsu respects the required firewall rules and certificates customer ownership & no vendor lock in mantsu delivers the templates; you own the final running system and data infrastructure there is no vendor lock in technology summary component technology license model mes application services mendix commercial enterprise (per app/user) service databases postgresql open source event streaming broker kafka broker redpanda community edition open source ot edge mqtt broker + low code open source or commercial enterprise reporting & uns historian custom high code app template code base (customer owned) metric dashboards grafana open source metrics collection prometheus + loki open source alerting prometheus alert manager open source container orchestration kubernetes open source edge container management docker / docker compose open source