Architecture

how is mantsu built? audience this section is written primarily for it architects and technical specialists who design, deploy, or assess the mantsu setup non technical readers, such as plant managers and project stakeholders, can use it to understand the building blocks and compare deployment and licensing options mantsu is a modular mes (manufacturing execution system) designed for industrial plant environments, built from macro services 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 for a functional introduction to the modules, start with the overview docid\ fqe5vuvafla ozw agbzk or visit mantsu io/product https //mantsu io/product 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 you do not need the full suite from day one select the modules you need, start small, and let the deployment grow with the plant 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 build will be owned by you, the customer this means that you will own the code base and you will own the data there is no vendor lock in mantsu architecture overview showing the mes application services, redpanda event broker, reporting and data services, and ot edge nodes 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 erp integration production orders, master data, and confirmations are exchanged with the erp through flexible rest or odata interfaces, tracked in the core manager interface log (see erp interfaces docid\ gcaup35nmhwns28eznref ) 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 which technologies does mantsu use? 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 frequently asked questions can mantsu run on premises as well as in the cloud? yes mantsu is containerized and runs cloud native, on premises, or in a hybrid setup; the node topology is chosen per plant do you need the full suite from day one? no you start with the modules you need and let the deployment grow with the plant who owns the code and the data? you do mantsu delivers templates; the final build and all data are owned by the customer summary mantsu is a modular mes built from containerized macro services that run cloud native or on premises mendix based services, a redpanda event broker, and ot edge nodes are connected through a unified namespace you start from templates, customize fast, grow per module, and own the final build and data