Joule Studio: the single environment for building agents
SAP Joule Studio is the AI-first development environment for building custom agents, apps and workflows on SAP Business AI Platform. It's a single managed environment combining agent building, development with the SAP Cloud Application Programming Model, workflows and managed runtime — instead of having to assemble separate tools.
A detail that matters for anyone evaluating the platform: Joule Studio uses the technical and business context already present in SAP to generate solutions compatible with existing processes, applications and architecture. You don't start from zero: you start from what your company has already configured in SAP.
Two paths: low-code and pro-code
SAP supports two approaches for building custom agents, and the choice depends on the team and the complexity of the use case.
The low-code path goes through Joule Studio with visual configuration: you build the agent through a graphical interface, and registration with Joule happens automatically. It's the right path for less technical teams or standard use cases.
The pro-code path uses SAP Cloud SDK for AI, with support for agentic development frameworks like LangChain, LlamaIndex, LangGraph, AG2, CrewAI and Smolagents, integrated via the A2A protocol. It's the path for development teams that want full control over the agent's logic, while still keeping interoperability with the Joule ecosystem.
Want to build your first agent on SAP Joule?
30 minutes to discuss your specific case.
MCP: the bridge to external systems
A key enhancement in Joule Studio is native support for the Model Context Protocol (MCP), the open protocol that standardizes how an agent interacts with external tools and systems.
For anyone building agents that need to work not just inside SAP but with third-party systems too — a CRM, a digital signature tool, a data verification service — MCP is what avoids writing a custom integration for every system. It's the same principle behind how we integrate Claude into business systems: a standard protocol instead of fragile point-to-point integrations.
Governance is built in, not optional
Joule Studio governs agent identity, runtime and performance with controls designed to scale safely. In practice: identity and access controls via SAP Cloud Identity Services, pre-launch testing and validation, and continuous evaluation of agent performance once in production.
This is what separates a pilot project from a production-ready one. An agent that works in a demo and one that holds up in production, on real business data, are two different things — the difference almost always lies in governance, not in the model behind it.
Where a real project starts
In our experience, a Joule agent project doesn't start with the choice between low-code and pro-code: it starts with a specific, high-impact business process where an agent can genuinely make a difference. Only afterward do you choose the right technical approach — often low-code to validate quickly, pro-code when the use case requires more sophisticated logic or custom MCP integrations.
It's the method we apply together with PA ABS, our SAP Gold Partner: they bring S/4HANA depth and SAP architecture, we bring expertise in Claude, MCP and agent design. If you want to know how to set up a first project, let's talk.