The principles behind MACH architecture

MACH stands for Microservices-based, API-first, Cloud-native and Headless.

MACH architecture


Microservices-based means that the functionality is divided into separate consumable parts that are divided into business value or business process.


API-first is a concept using standardised communication between different applications, enabling fast integration of services. It is a prerequisite for being able to replace or add future services without having to rebuild the entire solution.


Cloud-native means that the service is a genuine cloud service that all customers share in terms of code, enabling automatic scaling of performance and capacity and continuous updates in real time, making the solution future-proof. We call this True SaaS.


Headless separates the business logic from the presentation layer, enables faster development and supports seamless communication in all channels. This means you can freely choose the user interface and build omnichannel solutions in a sustainable and future-proof way with the customer experience in focus.