top of page
Search

Joule Studio vs Pro-Code Agents on SAP BTP: A 2026 Decision Framework for SAP Customers and Partners

Nov 7
4 min read

Post-TechEd 2026 edition — written for enterprise architects, SAP CoE leads and system integrators who need to pick the right agent-building path before committing budget.

At SAP TechEd 2026 in Berlin (27 October 2026), SAP made one thing very clear: the conversation has moved from "can AI understand our business?" to "can AI run parts of it?". Joule Work now plans and executes multi-step tasks, Joule Studio has expanded into a full agent and workflow environment, and SAP has opened a governed gateway so third-party agents can invoke Joule Agents over A2A and MCP.

For customers and partners, this creates a very practical question: should we build our next agent in Joule Studio, or as a pro-code agent on SAP BTP? Picking wrongly costs months. This post gives you the framework we use at Raven Infotech when we scope agent projects.

1. What actually changed in 2026

  • Joule Studio Agent Builder reached general availability in Q1 2026, and SAP is now rolling out the broader Joule Studio and Joule Work GA in phases.

  • Joule Studio offers no-code and pro-code options with a choice of 70+ AI models, role-based access (business users define intent, developers refine in their IDE or the Joule Studio CLI) and a built-in sandbox with execution traces and auto-generated tests.

  • Agents built in Joule Studio can be deployed to the SAP-managed Joule Studio runtime, where they become discoverable in SAP AI Agent Hub and usable inside Joule Work conversations.

  • n8n workflows can be designed and run from Joule Studio (initially for early adopters).

  • Existing Joule Agents can be extended with extra instructions, APIs, MCP connections and workflow triggers — you no longer have to rebuild a standard agent to tweak it.

  • Commercials: SAP announced a time-bound promotion where select customers can run custom agents on the Joule Studio runtime free through December 2026; design-time tools stay free under fair-use limits. Always confirm entitlements for your contract and region.

2. The two paths, side by side

Path A — Joule Studio (low-code / managed). Configuration-driven agents with instructions, tools (skills, actions, APIs, MCP connections), grounding documents and model choice. Registration in Joule is automatic, the runtime is managed by SAP, and lifecycle (test, version, deploy) lives in one place.

Path B — Pro-code agents on SAP BTP. You own the code: Python or TypeScript using the SAP Cloud SDK for AI against the Generative AI Hub (orchestration service), typically structured with SAP CAP and a framework such as LangGraph, CrewAI, AG2 or Smolagents. The agent runs on Cloud Foundry or Kyma and is plugged into Joule through the Agent2Agent (A2A) protocol ("Bring Your Own Agent").

3. Our decision framework (7 questions)

  1. Is the process mostly SAP-native and conversational? (e.g., "summarise blocked invoices for my company code and propose next actions") → Start with Joule Studio, or extend an existing Joule Agent.

  2. Do you need deterministic, multi-step orchestration with custom state, retries and long-running waits? → Pro-code. Graph-based frameworks give you explicit checkpoints and resume semantics that a configuration-driven agent cannot express as cleanly.

  3. Does the agent need heavy non-SAP integration (legacy databases, partner portals, custom ML)? → Pro-code with CAP as the service layer, or expose those systems as MCP servers and consume them from Joule Studio.

  4. Who will maintain it? A business-led CoE with limited developers → Joule Studio. A product team with CI/CD, tests and code review → Pro-code is sustainable.

  5. Do you need to sell or reuse it across customers (partner IP)? → Pro-code packaged as a multitenant BTP extension, with A2A and MCP endpoints, gives you portability.

  6. What are your data-residency and model constraints? Both paths can use Generative AI Hub models; pro-code gives you finer control of orchestration modules (masking, filtering, grounding, fallbacks).

  7. How fast must you prove value? Weeks → Joule Studio prototype first. You can always "graduate" a validated use case to pro-code later.

4. The hybrid pattern we recommend most often

In real landscapes the answer is rarely either/or. The pattern that scales best is:

  • Joule (Joule Work) as the user entry point and orchestrator — users stay in one experience.

  • Joule Studio agents for SAP-centric reasoning and quick wins.

  • Pro-code specialist agents on BTP for complex logic, exposed to Joule via A2A.

  • Tools exposed via MCP: CAP services annotated with @mcp, and enterprise APIs published through the SAP Integration Suite MCP gateway with API-management policies.

This keeps the core clean, keeps tools reusable across agents and vendors, and keeps governance centralised.

5. Common mistakes we see

  • Exposing raw OData APIs as agent tools. Agents work best with a small number of well-described, business-level tools. Curate first.

  • Skipping identity design. Decide early whether the agent acts as the user (principal propagation) or as a technical user — this drives audit and authorisation.

  • No evaluation set. Use the Joule Studio sandbox or your own test harness with 30–50 realistic prompts before go-live.

  • Building on a dirty core. Agents amplify whatever APIs you give them. Level C/D custom code makes agent behaviour fragile after upgrades.

FAQ

Is Joule Studio part of SAP BTP? Yes — it is part of the SAP Business AI Platform on BTP and is accessed through Joule Work.

Can a pro-code LangGraph agent appear inside Joule? Yes. Expose it as an A2A server and register it in Joule as a scenario whose dialog function calls the agent's A2A endpoint.

Do agents consume AI units? Premium AI scenarios and agent executions generally consume SAP AI units; check your current commercial terms.

How Raven Infotech helps

Raven Infotech is an SAP BTP and AI agent engineering partner. We run 2-week Agent Discovery Sprints that end with a scored use-case backlog, a target architecture (Joule Studio, pro-code or hybrid) and a working prototype on your BTP subaccount. Book a free 30-minute architecture call through our contact page.

 
 
 

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page