What SAP TechEd 2026 changed for AI builders

#What changed, and when

SAP TechEd ran in Berlin from 27 to 29 October 2026. SAP used it to announce a set of tools for building, running and governing AI agents. Some are usable today. Most are announced with no date. This page sorts them, as of 3 November 2026, from SAP's own pages.

Sources: SAP's 27 October release, the 28 October keynote article, the Architecture Center's GA note for the agent gateway, the 30 October governance article and the 29 October data article.

Only one item in the table is generally available. One is in beta, two are in early-adopter programs, one is a time-limited promotion, and the rest are announced without a date.

#Why it matters to the business

TechEd announcements reach steering committees within days, often before anyone checks the status. Getting the status wrong costs money in both directions:

• Waiting for something that isn't ready. If you pause your own controls for SAP Enterprise AI Gateway, you run agents without budgets or logs until a date SAP hasn't given.
• Building what SAP now ships. The agent gateway is generally available. A team that builds its own front door for partner agents into Joule duplicates it.
• Budgeting on a promotion. The free Joule Studio runtime is for select customers, and it ends in December 2026. A business case that assumes free running costs is wrong from January.

Take a procure-to-pay example. A supplier's AI agent wants the status of a sourcing event. It can now call a Joule agent through the agent gateway. SAP registers the supplier's client and limits which agents it may call, and the Joule agent acts with the signed-in user's permissions. That is usable now, if your landscape has the agents it needs.

#How SAP does it

SAP groups these announcements under its Business AI platform. Read them in five layers:

• Traffic. The agent gateway is the governed entry for outside agents calling Joule agents, using the open Agent2Agent (A2A) protocol. SAP Enterprise AI Gateway, announced on top of SAP Integration Suite, is meant to govern all AI traffic: model calls, MCP servers, APIs and agent-to-agent calls.
• Build and run. Joule Studio is where custom agents and workflows are built. Its managed runtime runs them. SAP announced observability and admin controls for usage and spend, and n8n workflows for early adopters.
• Models. SAP-RPT is SAP's model for predictions on tables of business data. Version 2.0 adds anomaly detection and embeddings. SAP-RPT-TS forecasts time series inside SAP IBP.
• Data. SAP Business Data Cloud (BDC) adds Ontology Manager in beta, so teams can define business meaning on top of SAP Knowledge Graph.
• Governance. SAP AI Agent Hub keeps an inventory of agents, models and MCP servers. The new AI Governance Assistant drafts EU AI Act assessments for review by legal and compliance.

SAP's 28 October article also names an Autonomous Suite of about 40 assistants and 300 agents, without dates. Treat that as direction, not a product you can plan against yet.

#Announced, beta, GA: a decision guide

Each status means something different for a plan. Use this guide before a steering committee commits.

"GA" is a statement about SAP's product, not about your tenant. Check region, edition, license and price before you count on it.

#Questions to ask

1. Which of these announcements does our roadmap depend on, and what status does SAP's own page give each one today?
2. Are we one of the select customers in the Joule Studio runtime promotion? What will running our agents cost from January 2027?
3. Do any partners or suppliers want their agents to call ours? If so, is the agent gateway available in our region and contract?
4. If we build or buy an AI gateway now, how will we move to SAP Enterprise AI Gateway later?
5. Who owns the AI inventory in SAP AI Agent Hub, and who reviews what the AI Governance Assistant drafts?
6. Which announcements has our partner shown us as "available"? Where did they get that status?

#Common misconceptions

• "Everything announced at TechEd is available now." As of 3 November 2026, only the inbound agent gateway is stated as generally available on SAP's pages.
• "Joule Studio is free." Design-time is free under fair-use limits. Running agents is free only for select customers, and only through December 2026.
• "The agent gateway and SAP Enterprise AI Gateway are the same thing." The agent gateway handles outside agents calling Joule agents. Enterprise AI Gateway is the broader, announced control point for all AI traffic.
• "A quarter in the trade press is a release date." Some articles list quarters that SAP's own pages don't state. Plan on SAP's pages, and ask your account team for the rest.
• "The AI Governance Assistant makes us EU AI Act compliant." SAP says its outputs are drafts for legal and compliance review. People still decide.

#Key terms

All course terms, A to Z, in the glossary

• Agent gateway: SAP's governed entry point through which outside agents call Joule agents, using the A2A protocol.
• SAP Enterprise AI Gateway: an announced SAP control point for authentication, policy, routing, monitoring and auditing of all AI traffic.
• Agent2Agent (A2A): an open protocol that lets one AI agent hand a task to another.
• Generally available (GA): a product SAP sells and supports for production use.
• Early adopter program: a limited program in which selected customers use a feature before broad release.
• Ontology Manager: a beta tool in SAP Business Data Cloud for defining business views on SAP Knowledge Graph.
• AI Governance Assistant: an assistant in SAP AI Agent Hub that drafts EU AI Act assessments for human review.

#Check yourself

#Mental model: a status ladder, and you are on the last rung

Every announcement climbs the same ladder: announced → early adopter or beta → generally available → available to you. The last rung is the one that matters for a design. It means it's in your region, your edition, your contract, at a price you know.

A TechEd week moves many items one rung, and some items not at all. Your job as a builder is to put each dependency on the right rung, design so that the ones low on the ladder can arrive later, and re-check on a schedule. Everything below follows from that.

flowchart LR
  A[Announced] --> B[Early adopter or beta]
  B --> C[Generally available]
  C --> D[Available to you]
  D -.-> E[Region, edition, license, price checked]

#How it works: where each announcement sits

This diagram puts the announcements in one agent landscape. Solid boxes are usable now. Dashed links are announced.

flowchart TB
  P[Partner agent] -->|A2A, GA| AG[Agent gateway]
  AG --> J[Joule agent]
  J --> S[S/4HANA and other SAP apps]
  B[Builders] --> JS[Joule Studio]
  JS --> RT[Managed runtime]
  RT --> J
  EAG[Enterprise AI Gateway] -.->|announced| LLM[Models, MCP servers, APIs]
  RPT[SAP-RPT-2.0 and RPT-TS] -.->|announced| J
  BDC[BDC Ontology Manager, beta] --> KG[SAP Knowledge Graph]
  HUB[SAP AI Agent Hub] --> GOV[AI Governance Assistant]

#Traffic: the agent gateway (GA) and Enterprise AI Gateway (announced)

SAP's Architecture Center announced general availability of inbound A2A through the agent gateway in October 2026. The mechanics, as described on that page:

• An administrator registers the outside client as an Agent Gateway Consumer through SAP for Me. It is then onboarded in three steps SAP calls formations: identity, trust and an access control list.
• At run time the gateway validates the token, resolves the customer tenant and checks the access list before it routes the call.
• The Joule agent acts within the signed-in user's permissions, and the interaction is logged for audit.
• Discovery returns a catalog of agents, but SAP notes that discovery does not grant permission to invoke one.

The inbound A2A reference architecture (updated 26 October 2026) adds detail. Tokens are SAP Cloud Identity Services App2App tokens carrying named user context. Audit logging runs through SAP Cloud ALM. SAP Integration Suite can sit in front for API management and delegates the calls to the gateway. The same page says the architecture is in a transitional state and not fully GA. It also says two-way communication with third-party and self-hosted agents is not yet supported. Calls from Joule agents out to other agents or MCP servers are future direction.

SAP Enterprise AI Gateway is a different scope. SAP's 27 October release describes centralized management of AI traffic: authentication, policy enforcement, routing, monitoring, usage tracking and auditing. The 30 October article says it covers MCPs, APIs, agent-to-agent connections and LLMs and runs on SAP Integration Suite. The 28 October article calls it an overlay to the agent gateway. None of the three gives a status, date or price. The pattern is taught in AI gateways: governing model and agent traffic.

#Build and run: Joule Studio

The managed Joule Studio was announced on 13 May 2026 with a managed runtime, embedded n8n and pro-code frameworks. At TechEd, the 27 October release added three things:

• Runtime promotion. Deploying and running custom agents on the SAP-managed runtime stays free through December 2026, as a time-bound promotion for select customers. Design-time tooling stays free under fair-use limits.
• Observability and admin controls for agent behavior, model usage and spend. No status is given. The May announcement already pointed to SAP Cloud ALM for monitoring usage, cost and business impact.
• n8n workflows for designing and running workflows, in the early adopter program, with broader availability to follow.

The TechEd pages read for this topic give no general availability statement for the managed Joule Studio itself. Check its status for your tenant before you plan on it. Joule and Joule Studio explains the two Joule Studios.

#Models: SAP-RPT-2.0 and SAP-RPT-TS

The 27 October release says SAP-RPT-2.0 will expand the tabular model beyond classification and regression to anomaly and outlier detection and embeddings. A new model, SAP-RPT-TS, forecasts time-indexed metrics in SAP Integrated Business Planning without custom machine learning. No status or date is given. SAP's HPE article of the same day describes a planned SAP-RPT deployment for space telemetry, expected by early 2027. It names no version. The concepts are in Tabular AI and SAP-RPT.

#Data: Ontology Manager and the lakehouse

The 28 October article says SAP Business Data Cloud Ontology Manager is "available as beta". The 29 October data article describes it as an AI-assisted way to build domain-specific views of SAP Knowledge Graph. The same article states one GA item, SAP Reltio master data management in BDC. It also describes open-lakehouse support (Apache Iceberg and the Apache Polaris catalog) and federated queries through Dremio, whose acquisition is complete, without status labels. Ontologies are taught in SAP Knowledge Graph and Business Data Cloud.

#Governance: AI Agent Hub and the AI Governance Assistant

The 30 October article adds the AI Governance Assistant to SAP AI Agent Hub. It flags incomplete agent inventory documentation, pre-fills fields from completed assessments, points to likely high-risk systems that lack a classification, and triggers a reassessment when an agent's fact sheet changes. All its outputs are drafts for legal and compliance review. The 28 October article says SAP releases it to SAP Early Adopter Care customers in November. The same governance article describes a LeanIX knowledge intake agent that proposes knowledge graph links and needs human approval before agents use the data. See AI governance for SAP programs and The EU AI Act.

#What TechEd named without a status

Three more items appear on SAP's pages without a status, so they stay off a plan for now:

• Joule Work, the engagement layer for Joule, was tested by more than 110,000 SAP employees and more than 150 Early Adopter Care customers, per the 28 October article. The 27 October release says it supports MCP and A2A as open protocols. No general availability is stated.
• Autonomous Suite, about 40 assistants and 300 agents from SAP and partners, is named in the 28 October article without dates.
• Databricks in BDC. The same article says the full Databricks platform will be available natively in Business Data Cloud, with no further status.

Treat each as a signal of direction. If your design would change because of one, record it in the status register with "announced, no status" and a re-check date, as the next section shows.

#Re-check the status yourself

Statuses on this page will move. This checklist is how you re-check them in about 20 minutes, with no code.

Before you start: you need only a web browser. Nothing from Set up your computer for this course is needed for the checklist; the exercise later saves a file in your orchestrate-course folder.

#Step 1: List what your design depends on

1. Open your solution design or roadmap.
2. Write down every SAP AI product or feature it names. One line each.

#Step 2: Find SAP's own page for each

1. Start at SAP News' TechEd coverage and the SAP Architecture Center.
2. For a product already in use, look for its "What's new" page on help.sap.com.
3. Skip trade press and partner slides at this step. They are useful leads, but not the status.

#Step 3: Copy the status words exactly

1. Look for the words SAP uses: "generally available", "beta", "early adopter", "planned", or a dated promotion.
2. If the page gives no status, write "announced, no status". Don't fill the gap with a quarter you read elsewhere.
3. Record the page's date and the date you read it.

#Step 4: Check the last rung

1. For each GA item, ask your account team or check your contract for region, edition and license.
2. For each promotion, write the end date and who qualifies.

#Step 5: Set the next check

1. Put a re-check date next to each item. Monthly is enough for announced items; check promotions a month before they end.

What success looks like: a short list where every line has a status in SAP's words, a source link, two dates and an owner.

Agent gateway (inbound A2A) | GA, October 2026 | architecture.learning.sap.com news, 27 Oct | read 2026-11-03 | owner: integration lead | recheck 2026-12-01
SAP Enterprise AI Gateway  | announced, no status | news.sap.com, 27 Oct | read 2026-11-03 | owner: platform lead | recheck 2026-12-01

#What to build on now, and what to design for

#Build vs. SAP

#Architecture view

Where it sits. The diagram in How it works shows the landscape. The agent gateway sits at the edge of SAP's Business AI platform, in front of Joule agents that reach S/4HANA and other SAP applications. Enterprise AI Gateway is announced as a layer on SAP Integration Suite over all AI traffic, including non-SAP models and MCP servers.

Non-functional requirements.

Integration and identity. For inbound A2A, the outside client authenticates with SAP Cloud Identity Services App2App tokens that carry named user context. The gateway checks the access list and routes to the Joule agent, which reaches SAP systems within that user's permissions. Audit logs go to SAP Cloud ALM. Integration Suite can sit in front for API management. The detail is in Agent permissions and SAP authorizations.

The decision to record. At Calder Pumpworks (a fictional company), the integration lead writes one ADR in the form from the design-doc topic:

• Context: a distributor wants its purchasing agent to ask Calder's Joule agents for order status. Calder also runs its own gateway for invoice triage agents.
• Options: (A) a custom A2A endpoint; (B) SAP's agent gateway for inbound calls, own gateway for model traffic; (C) wait for SAP Enterprise AI Gateway for both.
• Decision: B. Inbound calls use the generally available route. Model traffic keeps the course's own gateway, with policies stored as data.
• Consequences: two control points until SAP's gateway is available; a monthly status check; a migration plan when SAP states a date.

What a design review will ask.

1. Which status, from which SAP page and date, does each dependency have?
2. Whose permissions does an outside agent's call run with, and where is that logged?
3. What does running these agents cost from January 2027?
4. How do policies move from our gateway to SAP's when it ships?
5. Which beta or early-adopter features sit on a production path?

#Production concerns

• Security and SAP authorizations. Register each outside client with its own identity and the smallest access list. The Joule agent acts within the signed-in user's permissions, so role design still decides what is possible. Discovery isn't permission.
• Evaluation. A new model version, such as SAP-RPT-2.0, needs your own test set before it replaces anything. See Tabular AI and SAP-RPT.
• Cost. Log tokens and calls per agent now, so you can price the runtime when the promotion ends. Token economics shows how.
• Operations. Beta and early-adopter features can change without the notice periods of GA products. Keep them off paths where an outage stops a business process.
• Clean core. These are side-by-side services on SAP's platform. They call released APIs and run with user permissions; none of them needs a modification in S/4HANA.

#Pitfalls

• Status by keynote. A demo on stage is not a release. Use the status words on SAP's pages.
• Mixing up the two gateways. The agent gateway is GA for inbound A2A. Enterprise AI Gateway is announced. They have different scopes.
• Free in the pilot, priced in production. The runtime promotion ends in December 2026 and covers select customers only.
• Filling gaps from trade press. Quarters that SAP's pages don't state belong in the "Needs verification" column, not the plan.
• Beta on a critical path. Ontology Manager is beta. Prototype with it; don't run month-end on it.
• Stale pages. This page is dated 3 November 2026. Re-check before you quote it.

#Exercise

Build a status register for your own program, so the AI roadmap from the roadmap and operating model topic rests on checked statuses.

Before you start: complete Set up your computer for this course, which creates your orchestrate-course folder and sets up Git.

1. Open a terminal in your orchestrate-course folder. The commands are the same in PowerShell and on macOS or Linux.
2. Create a folder for it:
   Copy

   mkdir radar

3. In a text editor, create radar/teched-2026-status.md.
4. Add one line for each item in this page's first table, in the format from the checklist: item, status in SAP's words, source link, page date, date read, owner, re-check date.
5. Re-open each source. If a status has changed since 3 November 2026, write the new one and its date.
6. Add one line for any other SAP AI feature your design depends on.
7. Mark each line build on now, design for or ignore for now, using the table in "What to build on now".
8. Save your work:
   Copy

   git add radar/teched-2026-status.md
   git commit -m "TechEd 2026 status register"

Done when: every line has a status copied from an SAP page, a link, two dates, an owner and a decision, and no line uses a date that only trade press gives.

#Check yourself