
The newer addition I find most interesting is Agent Management, which provides cross-platform inventory, monitoring, business-KPI measurement and governance for agents, including agents created outside Dataiku. Agent sprawl is a real problem, and Dataiku's own survey found 81% of global CIOs say they've lost oversight of their AI agents. Having one place to govern them regardless of where they were built is the right answer for regulated industries Review collected by and hosted on G2.com.
My main critique is on the infrastructure and operations side. Deploying and running Dataiku in air-gapped environments, which is the norm in banking, takes real effort. Plugins, code environments and container images all need mirrored repositories and custom image builds, and that work isn't as streamlined as I'd like. For a platform that sells strongly into regulated industries, disconnected operations should be a first-class path, not something each customer engineers on their own. Second, the core design node is still a fairly traditional stateful server. Compute scales out well to Kubernetes, but the node itself doesn't behave like a cloud-native application on OpenShift, so high availability and upgrades need more planning than with operator-managed platforms. Third, on GenAI, the LLM Mesh is a strong gateway, but I'd like deeper native integration with self-hosted serving stacks like vLLM, KServe and NIM, including visibility into GPU utilization and per-model cost. Most of the value in on-prem LLMs sits in that layer, and today Dataiku mostly treats the model endpoint as a black box. Finally, licensing. Per-seat pricing works against the democratization story. Rolling it out broadly to business users gets expensive quickly, and the new products add packaging complexity on top Review collected by and hosted on G2.com.