You now know what Joule connects to. The next question is how it holds together. Joule Work is not a single application. It is a layered system — an experience layer you interact with, a build and services layer that extends it, and an agent runtime that executes work. Underneath all three sits a shared platform of data, routing, and governance components.
Understanding this structure at a high level helps you see why Joule is enterprise-grade — and what SAP manages so you do not have to.
The Three Zones of Joule Work
Joule Work is organized into three distinct zones.
This zone is also SAP-managed, meaning the infrastructure for building and deploying agents is handled by SAP rather than your IT team.
SAP-Managed Joule — The Experience Layer
This is the zone you interact with every day. It contains everything that makes up the Joule Work user experience.
The EL web client is the primary browser-based interface for Joule Work, covering Conversations, Spaces, and the Develop entry point. Mobile Services power the Joule Work mobile app, including Joule Voice for hands-free interaction. Spaces is the dynamic AI-generated workspace layer. The Compositional Design System ensures a consistent interface across all surfaces. Joule Work Desktop Middleware connects the desktop app to the same managed infrastructure as the web and mobile experience.
SAP manages this entire zone. Updates, integrations, and new capabilities roll into it automatically.
Agent — The Execution Layer
This is where agents run. The Agent zone contains the Deployment API for registering and launching agents, the AppFnd Managed Runtime for customer-deployed agents, and the frameworks that host Skills and agentic workflows alongside Node and CAP applications.
Agents in this zone operate within your organization's authorization boundaries. Every action is traceable back to the user and role that triggered it.
SAP-Managed Build Core Services — The Build Layer
This zone is where Joule is extended. It contains the tooling for building agents, apps, and workflows.
Joule Studio is the intent-to-deployment environment where developers and power users build custom agents and automate processes. The broader Build Solutions layer includes additional frameworks for building with n8n and other tools. An Agent Runtime manages deployment and execution of custom-built agents in both provider and customer-managed environments.
The Shared Foundation
All three zones connect to a shared set of platform components that run underneath Joule Work.
Business Knowledge Graph gives Joule its understanding of SAP business data, processes, and relationships. It is what makes responses grounded in your actual landscape rather than generic AI output.
Enterprise Knowledge Exploration extends that grounding to unstructured enterprise content — documents, policies, and knowledge sources connected through document grounding.
Agent Gateway is the secure routing layer. Every request from Joule to an agent or backend service passes through it. It handles authentication, principal propagation, and tool discovery.
AI Agent Hub is the governance command center. It provides visibility and control over every agent running in your landscape — SAP-built, custom, and third-party.
Task Center aggregates work items and approvals from across SAP applications into a single place, so agent-driven tasks requiring human input surface in a single inbox.
Products represent the connected SAP application landscape — SAP S/4HANA, SAP SuccessFactors, SAP Ariba, and others — that Joule Work reads from and acts on.
What This Means for You
You do not need to manage any of this. SAP-Managed Joule provisions and maintains the experience layer and build layer on your behalf. The shared foundation components are included as part of that managed service.
What you get is a system where agents can act, developers can build, and every action is traceable — without your IT team carrying the infrastructure burden.
For teams who want to go deeper into the technical architecture, SAP's architecture center documents the full reference architecture at architecture.learning.sap.com.
Lesson Summary
- Joule Work is organized into three zones: the experience layer (what you use), the build layer (where agents are created), and the execution layer (where agents run).
- The experience layer includes the web client, mobile, Spaces, Voice, and Desktop Middleware — all SAP-managed.
- The build layer includes Joule Studio and the agent build and deployment tooling — also SAP-managed.
- The shared foundation underneath all three zones — Business Knowledge Graph, Agent Gateway, AI Agent Hub, Task Center, and connected Products — provides grounding, routing, governance, and application reach.
- SAP manages the entire stack. Your IT team activates. SAP handles the rest.