Article

SAP details phased Joule Studio rollout for custom workplace agents

SAP’s Joule Studio rollout separates free authoring from paid production. Here’s what teams need to know about access, runtime charges and n8n availability.

Editorial illustration for SAP details phased Joule Studio rollout for custom workplace agents: a controlled task flows from input to output. Not documentary evidence.

In its October 27, 2026 TechEd update, SAP detailed new Joule Studio capabilities for teams building custom workplace agents—software that can use tools to carry out tasks. General availability is proceeding in phases, rather than opening every feature to every customer at once.

The managed offering was announced in May. The practical change now is an SAP-hosted route for deploying agents that employees can use through Joule Work conversations, according to SAP’s rollout guide.

Access depends on your SAP setup

SAP lists two prerequisites: Joule must already be deployed, through either an AI Units entitlement or the no-cost Joule Base option; and the customer needs an SAP BTP Enterprise Agreement, Cloud Platform Enterprise Agreement or pay-as-you-go arrangement.

Those commercial requirements are not a rollout confirmation. The practical implication of phased access is that teams should check whether their own company environment has the features their workflow needs.

SAP also lists role-based participation in development and a testing sandbox for running queries and inspecting how an agent behaved. These are tools for checking work before deployment, not evidence that a particular business process will run correctly.

For the related question of who owns an agent and whose permissions it uses, see RohitAI’s coverage of IBM’s agent-identity controls.

Free authoring is not free production

SAP’s current pricing page distinguishes free authoring, subject to fair-use limits, from paid production use. Runtime—the hosted service where custom agents execute—is billed for compute and storage, plus agent memory, workflow runs and AI tokens.

A promotion removes custom-agent runtime charges for selected customers through December 2026. It is not a universal free-production offer, and the announcement does not spell out selection criteria or usage ceilings.

A packaged Joule Agent extended only with text instructions follows a different charging model: the extension adds no charge, but execution still consumes AI Units, SAP’s usage credits, per action. Those are not custom-runtime prices or fixed prices per completed task.

For a buyer, that makes the first decision whether an existing agent can meet the need before commissioning a custom one. Neither route is demonstrably cheaper without a workload estimate and contract rates.

SAP’s commercial page supplies no complete numeric tariff for the custom runtime. Request a post-promotion quote covering expected usage and any separately charged services, and confirm the authoring terms for the particular product edition.

n8n has a later rollout

n8n, the visual workflow tool, is currently available within Joule Studio to early-adopter participants. SAP’s guide targets general availability for Q1 2027. It also schedules offline evaluations for late Q4 2026 and direct Business Data Cloud integration for Q1 2027. These remain plans, not completed releases.

That matters if n8n is essential to the intended workflow: access to Joule Studio alone is not enough to justify a production start date.