What SAP Business AI Really Is in 2026: Three Layers, Joule Studio 2.0, and the End of Premium Plus

SAP Business AI consists of three layers (Context Layer, Build Layer, Governance Layer), a shared frontend (Joule), and embedded AI functions in more than 35 solutions. Packaging has changed fundamentally since 2025. What SAP Business AI is today, what has changed, and which governance moments emerge for contract owners.

The Three Layers in Brief

SAP Business AI is not a single application. It is a platform architecture that SAP has officially marketed as the SAP Business AI Platform since the Sapphire 2026 conference. Those who understand this architecture understand the contract structure behind it. Those who do not will negotiate agreements that do not match their actual usage requirements.

The architecture consists of three stacked layers:

The Context Layer is the invisible foundation. It encompasses the Generative AI Hub with access to external foundation models, the SAP-proprietary models SAP-ABAP-1 and SAP-RPT-1, the SAP Knowledge Graph as a source for process domain knowledge, and the Business Data Cloud (BDC) as the data layer. Every higher-level service, whether a Joule conversation, an embedded AI feature, or a self-built agent, consumes resources from this layer.

The Build Layer is Joule Studio 2.0, generally available since June 2026. It is the development environment for customer-built agents: a visual Agent Builder, a library of more than 2,500 pre-built SAP skills, a command-line interface for DevOps pipelines, and an integration of the open Model Context Protocol (MCP) for external AI toolchains.

The Governance Layer is the SAP AI Agent Hub, planned for general availability in Q3 2026. It is built on SAP LeanIX and provides discovery, verification, observability, and policy management for all agents in the tenant.

For contract owners, this layered model is directly relevant: each layer has its own metering points and its own licensing logic. A Joule license does not automatically cover agent build operations. Agent build does not automatically cover governance infrastructure. Those who do not assess the layers separately will encounter unplanned line items on the next invoice.

This article explains each layer, describes the most significant changes since 2025, and identifies the governance moments that arise for contract owners.

Context Layer: AI Foundation and Knowledge Graph

The Context Layer is the layer that makes Joule and all embedded AI features intelligent in the first place. Without it, Joule would be a generic chatbot without SAP context.

Generative AI Hub

The Generative AI Hub is the access point for foundation models within the SAP ecosystem. It abstracts the APIs of various model providers so that customers can select a model per use case without establishing direct contractual relationships with individual providers. As of Q2 2026, models from several major providers are integrated (source: SAP Help Portal, SAP Documentation Generative AI Hub).

Pricing is token-based: every call to a foundation model is measured in tokens and converted into AI Units. The token rate varies substantially by model. SAP-proprietary models sit at the lower end of the pricing scale. More capable external models typically generate higher token costs. For a Joule conversation of ten messages, between 5,000 and 20,000 tokens is realistic, depending on model selection, grounding effort, and conversation length (source: SAP Help Portal, Metering and Pricing for Generative AI).

SAP-Proprietary Foundation Models

SAP develops two proprietary foundation models: SAP-ABAP-1 and SAP-RPT-1.

SAP-ABAP-1 was trained on 250 million lines of ABAP code and forms the basis for Joule for Developers. SAP cites a productivity improvement of 20 to 25 percent for ABAP development (source: SAP News, Our 2026 Roadmap for Joule for Developers).

SAP-RPT-1 is trained on SAP business process data and enables process inference for embedded AI features.

These SAP-proprietary models have two opposing characteristics: they offer a genuine advantage over generic language models because they carry SAP-specific domain knowledge. At the same time, they create a dependency. Organizations that optimize ABAP development around SAP-ABAP-1 will find this practice difficult to separate from SAP (sources: SAP News Joule Studio, SAVIC Technologies AI Foundation Architecture 2026).

SAP Knowledge Graph and IP Indemnification

The SAP Knowledge Graph connects S/4HANA data models, SAP best practice processes, industry-specific content, and customer-owned metadata. It is the source from which Joule draws business context. With Company Memory, the concept introduced at Sapphire 2026, this graph can be extended with customer-specific knowledge: policies, standard operating procedures, undocumented process knowledge.

For contract governance, the IP indemnification clause is relevant: SAP assures that using SAP-delivered foundation models and embedded AI features does not trigger IP violations for the customer, provided AI usage stays within the contractually regulated parameters. This assurance does not automatically extend to customer-built agents that call external models via the Generative AI Hub (source: SAP Trust Center).

Build Layer: Joule Studio 2.0

Joule Studio 2.0 is the development environment for customer-built agents. SAP positions it as an "Agent Factory" and introduced it at Sapphire 2026 as a strategic core product on the build side. The generally available version has been accessible since June 2026.

Three Construction Patterns

Joule Studio supports three construction patterns with different levels of effort and risk:

Skill Assembly combines existing SAP skills into new workflow agents. Effort is low and risk is limited, because only deterministic SAP skills are used. This pattern is suited for process automation that stays entirely within the SAP ecosystem.

API Integration embeds external REST APIs as new skills. Effort is moderate; risk lies in ongoing API maintenance and interface stability.

Custom Model Grounding grounds agents on customer-specific documents, policies, and master data. This pattern carries the highest effort and the highest data quality requirements, but at the same time delivers the greatest differentiation value over generic copilots.

Free-Tier Through End of 2026 and the Commercial Implication

Through end of 2026, SAP provides free design-time access to Joule Studio under fair-use conditions. This free tier covers the development environment, not production operations. Runtime licenses for running customer-built agents in production are separately required.

From a governance perspective, this is a relevant governance moment: the free tier is an adoption strategy from SAP. Organizations that build agents in 2026 create a technical dependency on runtime capacity in 2027. Those who do not plan today which agents should go into production, and what licensing costs that entails, will find themselves making 2027 decisions under time pressure (source: SAP News, Joule Studio for Enterprise Scale Agentic Development).

The distinction between design-time and runtime is therefore not a technical detail but a contract topic: which runtime conditions can be negotiated now, as part of the AI procurement contract, before the dependency exists?

Governance Layer: SAP AI Agent Hub

The SAP AI Agent Hub is the third layer and, in some respects, the one least visible commercially, even though it forms the governance foundation for everything beneath it. It will be generally available in Q3 2026 and is therefore not yet fully rolled out at the time of this article.

Structure and Functions

The AI Agent Hub is built on SAP LeanIX, the SAP acquisition for Enterprise Architecture Management. This technical foundation is deliberate: governance of AI agents is an enterprise architecture problem, not a pure operations topic.

The Hub provides four core functions:

Discovery creates a complete inventory of all agents in the tenant: SAP-delivered agents, customer-built agents from Joule Studio, and third-party agents.

Verification ensures that agents are authorized and operate under defined policies.

Observability provides logging and monitoring for agent actions, including the data accessed.

Optimization delivers KPI tracking and comparison metrics per agent.

Architectural Boundaries and Practical Relevance

The AI Agent Hub has one important architectural boundary: it can only observe and govern what is visible within the tenant. Agents operating outside the SAP tenant, or third-party agents not registered through the Hub, fall outside its observability.

In practice, this means the Hub is not a universal governance instrument but a governance instrument for the SAP perimeter. Organizations running AI architectures with both SAP and non-SAP components will need a complementary governance capability for the non-SAP side.

The relevance for SAP contract governance lies in EU AI Act compliance: from 2 August 2026, deployers of high-risk AI systems must be able to demonstrate a complete inventory, human oversight mechanisms, and logging. The AI Agent Hub directly addresses these requirements for the SAP perimeter (source: SAP Trust Center, SAP Insider Sapphire 2026 AI Agent Guardrails).

What Changed in 2025 and 2026

Three changes are structurally relevant for contract owners. They affect existing contracts as much as ongoing negotiations.

The End of Premium Plus, June 2025

The former top tier RISE with SAP Premium Plus was discontinued in June 2025. The AI capabilities that had been part of it were partly carried over into SAP Cloud ERP Private and partly repositioned as separate add-ons (sources: Redress Compliance, CIO Magazine, SAP's RISE rebrand conceals cost changes).

For existing contracts that still reference the tier name "Premium Plus," an immediate governance moment arises: what is the contractually secured scope today? Which capabilities are included under the new packaging rules, and which are not? This review is not optional when the contract comes up for renewal or adjustment within the next 12 to 24 months.

Joule Studio 2.0 and SAP Autonomous Suite

Joule Studio 2.0 (GA June 2026) and the SAP Autonomous Suite (Sapphire 2026) mark a paradigm shift: SAP no longer delivers primarily licensed software but an execution infrastructure for autonomous agents.

The SAP Autonomous Suite already encompasses 224 agents and 51 role-specific assistants at the time of Sapphire 2026, distributed across Finance, Spend Management, Supply Chain, Human Capital Management, and Customer Experience (source: SAP News, SAP Unveils the Autonomous Enterprise, Sapphire 2026). That is a different consumption profile than traditional software usage: every deployed agent generates continuous AI Unit consumption, not a one-time license fee.

Joule Work as the New UX Vision

Joule Work, also introduced at Sapphire 2026, is SAP's long-term strategy for the user interface: Joule as the primary interaction layer, gradually replacing application navigation. On desktop, mobile, and voice, across SAP and non-SAP systems.

For licensing planning, this is a medium- to long-term governance moment: organizations planning to use Joule Work in 2027 or 2028 should assess whether current contracts cover the licensing model for that usage pattern or whether new commercial vehicles are required.

Governance Moments That Emerge

The three-layer architecture of SAP Business AI generates several concrete governance moments for contract owners.

On the usage side, the first governance moment arises from the distinction between embedded AI features and custom agents. Embedded features have a calculable consumption per transaction. Custom agents can consume three to twenty times that, depending on the complexity of the process chains (source: SAP Licensing Experts, Negotiating SAP AI Contracts). Those who are not familiar with this distinction will size the AI Unit budget incorrectly.

On the authorization side, the AI Agent Hub is the structural governance moment: which agents are authorized? Which data may they access? Which processes may run autonomously, and which require human-in-the-loop? These questions are not IT architecture topics but contract topics. They should be documented before agents go into production.

On the infrastructure side, the three-pool logic (AI Units, BTP Capacity Units, BDC Credits) generates the central governance moment: those who know which pool is consumed by which use case can make forecasting reliable. Those who do not will notice deviations only on the invoice.

On the cost side, SAP's Joule Studio strategy is the most important governance moment: the free tier runs out at end of 2026. Those developing agents today should negotiate runtime conditions now. Those who wait will negotiate in 2027 without competitive leverage, because the agents are already built and running on SAP infrastructure.

For Contract Managers, Procurement, Controlling, and Executives, a shared task follows: bringing the contract foundation for SAP Business AI in line with the current architecture before the next renewal cycle begins. Further detail on the consumption structure and billing mechanics is available in the follow-up analysis of the three consumption pools. Those who want to understand how Joule and foundation models diverge commercially will find that in the cluster on Joule, Skills, Agents, and Foundation Models. For the connection to special cases in SAP overall contracts, the analysis of special cases in the SAP Contract Governance context offers additional depth.

Frequently Asked Questions

What is SAP Business AI in three sentences? SAP Business AI is the umbrella brand for all AI functions in the SAP ecosystem, consisting of three layers: Context Layer (AI Foundation, Knowledge Graph, foundation models), Build Layer (Joule Studio 2.0 for customer-built agents), and Governance Layer (SAP AI Agent Hub for policy and observability). Joule sits on top as the shared frontend, and the SAP Autonomous Suite offers 224 pre-built agents. Each layer has its own licensing logic and metering points.

What does the end of Premium Plus mean for my contract? Since June 2025, RISE with SAP Premium Plus no longer exists as a standalone tier. Contracts that still reference this name point to a discontinued contract subject. Which capabilities are currently included in SAP Cloud ERP Private and what must now be procured as an add-on should be actively reviewed before the contract expires or is renewed.

Why is the Joule Studio free tier a contract topic? The free design-time access to Joule Studio runs out at end of 2026. Those who develop agents during this phase are building a technical dependency on runtime licenses that must be separately procured from 2027 onward. The commercial conditions for these runtime licenses are negotiable today; after the agents are deployed, they are substantially harder to negotiate.

When will the AI Agent Hub be available and why is it relevant for governance? The SAP AI Agent Hub will be generally available in Q3 2026. It is the central governance instrument for agent inventory, policies, and compliance documentation under the EU AI Act. Organizations that do not deploy the Hub will need to build agent governance manually, which is not a practical approach for regulated industries or high-risk use cases.

Bernhard Mändle is Managing Consultant at FinOptory and advises organizations on the ongoing governance of SAP contracts after signature. Connect on LinkedIn or book an initial conversation directly.