First of all, that's kinda apples and oranges. If kops is basically an installer, Deckhouse is much more a Kubernetes distribution. It's not just about deploying new clusters but about keeping them running all the way.
Kops installs a "bare" cluster; Deckhouse gives you a set of integrated modules for monitoring, authentication, etc. — as much "out of the box" as you might need to run real applications in K8s. Another outcome is that when you upgrade the Kubernetes version in Deckhouse, it also makes all the relevant work with components and modules in use (they are also updated with compatibility issues in mind, thus everything "just works"). That's why it's marketed as NoOps: it aspires to automate all these routine operations [so you can focus on other exciting challenges ;)].
Deckhouse can also be installed on bare-metal servers, provides SLAs & support for those who need.
