When a company sees a GitOps-based IDP for the first time, the reaction is often predictable: Isn’t this too complex? A central repository. ArgoCD. Promotion flows between environments. A control center. Jsonnet or templating logic. Secrets management. Rollback mechanics. Git-based approvals. Standardized deployment patterns. A clear separation between application state, infrastructure state, and external resources. At first glance, it may look like overengineering. Especiall