Web toolWeb toolA hosted utility you use at a URL, rather than run or install. May be free or paid; source_available says whether anything behind it is inspectable.See every one →What this type is →by SAPby SAPPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
Joule Studio
SAP’s managed development environment for building custom agents, applications and workflows from business intent, in six phases from intent and specification to deployment on an SAP-managed runtime.
Joule Studio’s browser builder and the pro-code workflow through @sap/joule-studio-cli@sap/joule-studio-cliSAP’s CLI package for both legacy Joule digital assistants and the new Joule Studio solution workflow, through the joule and jl commands.sap official, btp follow the same six phases: intent, requirements, specification, code generation, testing and deployment to an SAP-managed runtime. It supports applications with CAP backends as well as custom agents and workflows. As checked on 15 October 2026, the product page offers notification when the trial opens, while SAP’s Connect 2026 guide says general availability for Studio, Work and related offerings starts in October. This entry covers the new environment; Joule Studio, classic editionJoule Studio, classic editionThe low-code capability in SAP Build for custom Joule skills and Joule agents: skills call OData APIs through BTP destinations, agents get a model, instructions, tools and MCP servers, and both deploy to Joule.sap official, btp remains a separate SAP Build capability.
Where it sits
Lives in
Provides
Agent toolingBTPCAPAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.
Who is behind it
SAPSAPMaintains this
In the atlas: maintains 137, wrote 14@SAPmaintainer
In the atlas: maintains 137, wrote 14@SAPmaintainer
Before choosing this
Conditions
PolicySAP API Policy 4.2026a§ 2.2.2from Agent toolingAn agent built into an application reaches SAP Application APIs, whether directly or through tools generated from a service that proxies them.
- § 2.2.2 AI call sequences and data extraction. Outside SAP-endorsed architectures, data services or expressly identified pathways, the policy prohibits specified agentic API use and systematic or large-scale extraction.
capire's own guide states that CAP-level agents are intended only for exposing custom CAP application services, and names section 2.2.2 for the agentic-access provisions. Check which endpoints the agent's tools end up calling, and consult SAP's reference architectures for the endorsed routes.
SAP API Policy 4.2026a →What it declares
Every artifact
- Type
- Web tool
- Origin
- By SAP
As a web tool
- Access
- does not say
- What it sends to its vendor
- does not say
For agent tooling
- Protocols
- MCPA2A
Connections
Group by
NodeRelationBasis
Functional
Agent toolingAgent toolingBuilding an agent into your own applicationSAP and community, unassessed
provides
stated
provides Agent tooling
Builds custom agents through browser and pro-code development flows and deploys them to an SAP-managed runtime, where they are registered with [SAP Joule](artifact:sap-joule).
“Deploy solutions to a fully managed runtime straight from Joule Studio.”“This tutorial guides you through building your first agent in Joule Studio from the terminal, using the jl CLI and an AI coding agent.”“An SAP S/4HANA system configured with an SAP BTP destination.”“title: Building AI Agents with SAP Joule Studio on SAP BTP”“The **Low-Code Flow** uses the visual, browser-based Joule Studio builder — no local setup or coding agent required.”
Building an agent into your own application
Technical
@sap/joule-work-dev-cli-early-adopters@sap/joule-work-dev-cli-early-adoptersPro-code CLI for building and deploying Joule Studio solutionssap official, btp
needed by
derived
needed by @sap/joule-work-dev-cli-early-adopters
Logging in, creating, validating, building and deploying solutions to the [Joule Studio](artifact:sap-joule-studio) backend and runtime.
“Deploy solutions to Joule Studio runtime”
Pro-code CLI for building and deploying Joule Studio solutions
teched2025-AI163teched2025-AI163TechEd 2025 lab building a Joule Agent for Global Track and Tracesap official, btp
used by
derived
used by teched2025-AI163
where the Joule Skills and the agent are built; the Agent Builder inside it has to be enabled.
“This exercise shows how to build a simple custom Joule Agent in Joule Studio that uses multiple Joule Skills along with Document Grounding via AI Core to manage shipments in the SAP Business Networks Global Track and Trace (GTT) system.”“Agent Builder is enabled and accessible.”
TechEd 2025 lab building a Joule Agent for Global Track and Trace
teched2025-AI165teched2025-AI165TechEd 2025 hands-on on a Joule Studio agent collaborating over A2Asap official, btp
used by
derived
used by teched2025-AI165
where the custom agent and its Joule Skills are built; the session grants access to it and to its Agent Builder.
“Access to Joule Studio and its Agent Builder”
TechEd 2025 hands-on on a Joule Studio agent collaborating over A2A
teched2025-DA265teched2025-DA265TechEd 2025 workshop on Just Ask natural-language questionssap official, btp
used by
derived
used by teched2025-DA265
the part of the SAP Build environment the README requires alongside SAP Analytics Cloud.
“A SAP Build environment that includes Joule Studio and SAP Analytics Cloud.”
TechEd 2025 workshop on Just Ask natural-language questions
Download
Learn more
Readings
- Be the First to Understand Joule Work's Agentic ThinkingBe the First to Understand Joule Work's Agentic ThinkingA Devtoberfest 2026 session on the agent harness behind agentic thinking in Joule Work: generic operating-system tools in a gVisor-isolated sandbox instead of hand-wired domain functions, a react loop, a warm pool of sandboxes torn down after each task, tenant-separated skill loading, and placeholder tokens the agent never sees swapped for real credentials at the egress path. A skill is a folder with a SKILL.md carrying metadata and instructions, and where it reaches a system, an SAP connectivity JSON that declares each connector by ORD ID with its guardrails — GET allowed by default, POST, PUT, PATCH and DELETE requiring human approval, everything else blocked. The demo uploads a cost-centre skill through the skills view, then has agentic thinking delegate over A2A through Agent Gateway to a custom agent built in Joule Studio, whose MCP tools read cost centres from an S/4HANA Cloud system, and ends by turning the result into a PDF; the Joule Studio trace is what shows the tool call actually happened.SAP Developers, published 2026-10-15SAP Developers, YouTube — SAP Developers playlists
- Building Agentic Workflows with n8n in Joule StudioBuilding Agentic Workflows with n8n in Joule StudioA Devtoberfest 2026 session, JS-31, on SAP-managed n8n inside Joule Studio, shown as a labs preview on a blocked-invoice scenario: a solution made of assets, an intent refined by the web agent into requirements and then a specification, and the generated workflow opened in the n8n editor that Joule Studio connects to its own n8n tenant, with the generated files committed through GitHub. The nodes carry the other edges — the human-in-the-loop node is built on SAP Task Center, and SAP AI Core is where model providers are configured centrally instead of per developer. It ends in Joule chat, where the approval task the workflow created is listed, opened and completed.SAP Developers, published 2026-10-08SAP Developers, YouTube — SAP Developers playlists
- From Intent to Arcade: Building Joule*Bert with Joule Studio and AI-Assisted Pro CodeFrom Intent to Arcade: Building Joule*Bert with Joule Studio and AI-Assisted Pro CodeA Devtoberfest 2026 AI-track session that takes a Q*bert-style arcade game, written as an Easter egg for colleagues, through every phase Joule Studio runs: intent analysis with its clarifying questions, a product requirements document, a specification with its task list, generated code, generated tests and deployment. The knowledge-graph lookup reports that the game maps to no enterprise process and the flow adjusts, and the presenter edits the requirements by hand when the first version declares sound out of scope. He then pushes the project to GitHub, clones it and initialises the jl command line so that Joule Studio's MCP servers are wired into the coding agent in VS Code, where mobile arrow keys were added afterwards; applications could not yet be deployed to the Joule Studio runtime, so this one runs on Kyma.SAP Developers, published 2026-10-01SAP Developers, YouTube — SAP Developers playlists
6 more
- Real Pro-Code Development with Joule StudioReal Pro-Code Development with Joule StudioA Devtoberfest 2026 AI-track session that runs one agent build across both of Joule Studio's paths. Playing a procurement manager, one presenter states the intent in the browser, answers the clarifying questions, watches the fit-gap analysis name the S/4HANA APIs the use case needs, and pushes the intent and requirements document to GitHub; the other clones it and carries on in a terminal, logging in with the jl command line against her landscape URL and running its init command to fetch Joule Studio's skills for OpenCode. From there the coding agent writes the specification, the discovered API specifications, the MCP translation and the agent's Python file with its model configuration and evaluation scenarios, which is the edge to Agent tooling; the skills themselves, which SAP says not to edit but which a developer may add to, are the edge to Agent guidance.SAP Developers, published 2026-10-01SAP Developers, YouTube — SAP Developers playlists
- Achieve Agentic Enterprise Automation with SAP Integration Suite and Joule StudioAchieve Agentic Enterprise Automation with SAP Integration Suite and Joule StudioA Devtoberfest 2026 integration-track session (INT-22), the second of that week's integration sessions, given by an SAP product expert for process automation and integration together with the product manager for Joule Studio, who walks the audience through it. The opening states the subject: process management, automation and orchestration unified into one combined approach, which the presenters put forward as the foundation for building custom AI agents.SAP Developers, published 2026-09-30SAP Developers, YouTube — SAP Developers playlists
- SAP BDC and AI: A Perfect MatchSAP BDC and AI: A Perfect MatchA Devtoberfest 2026 data-track session (DAT-22) in which Business Data Cloud's CTO sets out how SAP Business Data Cloud feeds SAP's business AI platform: data products whose primary persistence is an object store and whose semantics are kept with them, the one domain model that links a supplier in Ariba to a supplier in S/4HANA, and the SAP knowledge graph, a triple store running in SAP HANA Cloud and queried with SPARQL, that SAP Joule consults before answering. The live demo asks Joule for the available data products and the top ten open purchase orders, with the data product query agent compiling SQL over virtual tables and a space rendering a dashboard, which is the cataloguing side of this: a central registry, the Unified Customer Landscape, that every activated data product is registered in. The Q&A covers where the knowledge graph lives and what a customer may extend, base policies that turn into filter conditions on an agent's queries, and Joule Studio as the place to build your own agents and data products.SAP Developers, published 2026-09-29SAP Developers, YouTube — SAP Developers playlists
- Meet Joule Studio and Build your First AI AgentMeet Joule Studio and Build your First AI AgentA Devtoberfest 2026 session from the product manager of Joule Studio, walking one agent through the whole path the tool defines: an intent, the problem statement and goals a coding agent derives from it, the business context it takes from the SAP knowledge graph, and the solution type it proposes with a stated intent fit. The demo is a collections agent that drafts dunning emails: the product requirements document names the metrics and the human-in-the-loop review, the technical specification lists the artifacts to build — the MCP tools among them — and the build is followed by a business test run against business partner 10001, technical unit tests, and deployment to the managed runtime, where the agent and its MCP server appear as deployed assets. Two points shape how it is used rather than what it produces: every asset is a file, editable in the web editor or in the code view and pushable to git, and the same solution can be built from local pro-code tools; n8n workflows are stated as delivered out of the box inside the studio.SAP Developers, published 2026-09-24SAP Developers, YouTube — SAP Developers playlists
- How Redwood Software and SAP are shaping the next era of automation with Joule StudioHow Redwood Software and SAP are shaping the next era of automation with Joule StudioRedwood's Field CTO describes a tech preview where an SAP Basis administrator tells SAP Joule in natural language to pause background jobs and dependent Integration Suite iFlows for unplanned system maintenance; Joule acts as a control tower, triggering a pre-approved RunMyJobs workflow and asking for approval before the restart proceeds. The integration is built by publishing RunMyJobs operations to the SAP Business Accelerator Hub, securing access through SAP BTP with API keys and role-based permissions, and combining those actions into a skill inside Joule Studio's low-code design canvas.gmblom, published 2025-11-02gmblom, SAP Community
- Joule Studioがリリースされたので早速CAPアプリを自然言語で操作するカスタムスキルを構築してみたJoule Studioがリリースされたので早速CAPアプリを自然言語で操作するカスタムスキルを構築してみたA walkthrough of building a custom Joule Studio skill on a CAP bookshop app: cds add sample and cds add mta scaffold the project and its deployment descriptor, cds compile srv/ --to xsuaa generates the role template behind the @requires: 'admin' check on AdminService from the SAP Authorization and Trust Management service (XSUAA), and mbt build packages the app for deployment to the SAP BTP, Cloud Foundry Runtime. The skill reaches the deployed OData API through the SAP Destination service, configured with the OAuth2 Client Credentials grant using the client ID, secret and token endpoint from the app's XSUAA service key, so Joule answers a natural-language question about a book by its ID.takayuki_tanaka, published 2025-07-30takayuki_tanaka, SAP Community
Others providing
Compare all 5 on the Agent tooling page →Agent toolingAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.SAP and community, unassessed
- Joule Studio, classic editionJoule Studio, classic editionThe low-code capability in SAP Build for custom Joule skills and Joule agents: skills call OData APIs through BTP destinations, agents get a model, instructions, tools and MCP servers, and both deploy to Joule.sap official, btpLow-code SAP Build capability for custom Joule skills and agents
- @sap/joule-studio-cli@sap/joule-studio-cliSAP’s CLI package for both legacy Joule digital assistants and the new Joule Studio solution workflow, through the joule and jl commands.sap official, btpCLI for Joule digital assistants and Joule Studio solutions
- @sap/joule-work-dev-cli-early-adopters@sap/joule-work-dev-cli-early-adoptersjl, the pro-code CLI of the new Joule Studio: a solution is a folder with a solution.yaml and typed assets, validated, built into a zip and deployed to Joule Studio's managed runtime, with Claude Code or OpenCode wired in over MCP. Early Adopter Care.sap official, btpPro-code CLI for building and deploying Joule Studio solutions
- SAP JouleSAP JouleSAP's unified AI engagement layer across SAP applications: Joule Work is where a user expresses intent, Joule Assistants coordinate agents across business functions, and Joule Agents carry out the tasks, provisioned on BTP as a formation against SAP Cloud Identity Services.sap official, btpSAP's AI engagement layer across SAP applications
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainumbrella, ai-and-agents
History in the atlas
- The product overview describes "Workflows and integrations for both SAP and non-SAP systems." It also names CAP development; RA0029 places customer agents on BTP. These establish served views, while the new SAP-managed environment has no separate BTP catalogue listing established by this intake.
- web-tool; product tutorial; MCP and A2A stated
- First seen.
For your agent
- Ref
artifact:sap-joule-studio- JSON
- /artifacts/sap-joule-studio.json
- MCP
- Connecting an agent