Containers help to ease the pain on the technology side. We are now responsible for containers that hide whatever software is running inside. But containers are not enough. The main problem of BPM Suites is that most of them were designed as monoliths, pushing the adopters to go for all or nothing. On the other side of the spectrum, you will find Open Source BPM Frameworks which aim to be as generic as possible to support a wide range of development and deployment scenarios. By doing this, these projects are troublesome to use, to maintain and to fit into different architectures. Because of this generic approach, Open Source BPM frameworks delegate too many decisions to the one implementing the solutions, pushing them to not only learn about the internals of the framework but also to make complicated decisions that only experts can make accurately.