The issue, according to SAP’s chief AI officer Jonathan von Rüden, was that SAP had favored ease of use over power in its original architecture. “People wanted to see more pro-code flexibility,” he said in an interview at Sapphire 2026. “We had gone with a low-code approach. You could give it extension points and tools, but you couldn’t touch the core of it. Now you can build a custom agent, connect it to your own GitHub.”
Customers also came with “big plans” but needed hard rules and approval gates that the original Joule Studio didn’t support natively. “What people want is agentic flows with clear gates and workflows and subagents,” von Rüden said. “Old Joule didn’t provide that. Now it’s all baked together.”
What actually shipped
Joule and AI Agent Hub are generally available, though the latter is now getting a “massive revamp” with version 2.0. The Knowledge Graph is live and has expanded beyond its original scope. Initially used for building Joule skills, it now feeds context directly to AI agents so they can “figure out how to call something dynamically,” von Rüden said.
Joule Studio, however, is still in early customer adoption; general availability is expected in the third quarter — a year behind the original target. Joule Work, the new engagement layer announced this week, isn’t expected until the second half of this year.