@Ivo trying to give a nuanced answer because ‘it depends’ 😉 frameworks like Kratix and Crossplane for example are also building on that Kube CRD API capabilities and can complement and be integrated in the approach I presented. Humanitec orchestrator is more a rule engine and together with score.dev specs specifically targetted at application workloads, thus less flexible to also create other abstractions like data products. Additionally, the k8s operator pattern we use is a continuously self-healing pattern meaning that when something in the environment breaks/disappears, then the reconciliation will restore this, humanitec orchestrator does not detect this and needs an explicit trigger/deploy to reconcile again if I am not mistaken. Could complement each other by letting humanitec orchestrator reconcile the CRD resources with your own operators reconciling each resource, which can also be done by crossplane and others for example. In short, for as far as I see it was not such a good fit for our use cases.