As a side not I think your view is a bit too simplistic. For my own situation and I guess many other that most software packages assume some level or another ro

As a side not I think your view is a bit too simplistic. For my own situation and I guess many other that most software packages assume some level or another root access and trying to manage all the hybrid of configuration files when you're deploying multiple web-frameworks on the same machine/vm can be a configuration nightmare. Put it more simply, yes to do it correct requires inspecting each and every web-tire solution, and its sockets, permissions, group permissions, and dependencies . This consumes a hell of a lot of time! The alternative is to throw the web-tire solutions or package in it's own container, and place monitoring software on the container to kill the container if things go wild or somebody figures out how to hack through the web-tire solution.