SAP TechEd 2026: What Developers and Architects Should Take Away

SAP TechEd 2026 ran from 27 to 29 October at Messe Berlin, with a virtual edition on the same days. SAP’s TechEd press release and keynote recap are about agents, governance and data; ABAP and CAP don’t appear in them. The developer news that matters day to day arrived earlier in the year, in release notes. We cover both.

TL;DR: At TechEd 2026 SAP said general availability of Joule Work and Joule Studio is underway in phases and that the agent gateway is generally available. The SAP Enterprise AI Gateway, new Knowledge Graph capabilities and the Dremio lakehouse in Business Data Cloud are planned for Q1 2027. For developers, the bigger news is older: CAP’s MCP adapters went GA in September 2026, and the ABAP MCP server is GA.

This post builds on our explainer on the rename: SAP BTP is now SAP Business AI Platform (BAIP). We do not repeat it here. SAP Business AI Platform (BAIP, formerly BTP) is the foundation everything below runs on.

What did SAP announce at TechEd 2026?

SAP’s TechEd press release of 27 October 2026 is about moving AI from answering questions to running work. CTO Philipp Herzig put it as “moving from AI learning your business to running it”. The release itself gives almost no dates, so we sorted the items by what SAP’s other TechEd material and the trade press state.

Item	Status	Source
Joule Work (one entry point for intent-driven, multi-step work)	GA underway in phases	SAP TechEd innovation news guide, SAPinsider
Joule Studio (no-code and pro-code agent building, more than 70 AI models)	GA underway in phases	SAP press release, SAP Q3 highlights
Agent gateway (third-party agents call Joule Agents via A2A and MCP)	“Generally available today” per SAP’s keynote recap; enhanced interoperability in phased GA	SAP keynote recap
n8n workflows in Joule Studio	Early adopter programme, broader availability later	SAP press release
AI Governance Assistant (EU AI Act risk classification)	Early Adopter Care customers from November 2026	SAP keynote recap
SAP Enterprise AI Gateway (on Integration Suite)	Planned Q1 2027	SAP TechEd innovation news guide, SAPinsider
SAP Knowledge Graph with customer-specific and non-SAP sources	Planned Q1 2027	SAP TechEd innovation news guide
Business Data Cloud Ontology Manager	Beta: SAP’s keynote recap says “available as beta”, SAP’s innovation news guide lists the beta for November 2026	SAP keynote recap, SAP TechEd innovation news guide
Dremio lakehouse in Business Data Cloud (Apache Iceberg, Polaris)	Planned GA Q1 2027	SAP TechEd innovation news guide, SAPinsider

Nota bene: SAP’s own two statements on the Ontology Manager differ slightly. Check whether the beta is open for your tenant before you plan with it.

Joule Studio: what you can build now, and what it costs

Joule Studio is SAP’s place to build agents and skills on SAP BAIP. According to SAP’s Q3 2026 release highlights, “the agent builder is available for free until December 2026, after which it becomes a premium AI feature”, while the skill builder is a base AI feature. The TechEd release adds that design-time tooling stays free under fair-use limits, and the SAP-managed runtime is free through December 2026 for select customers.

A skill, in SAP’s description, is a natural-language description plus a few lines of code. An agent combines skills and plans its own steps. SAP’s keynote also showed a Process Consulting Agent that works out what to build before anyone writes code, and claimed intent-to-agent in about 2.5 hours instead of 13. That figure comes from SAP’s own testing, so read it as a vendor number.

The pro-code side is the interesting part for architects. When SAP introduced the new Joule Studio at Sapphire in May, it named LangChain, Pydantic AI and LlamaIndex, extension from VS Code, Cursor and other agentic IDEs, and agent memory on SAP HANA Cloud. So you are not locked into a drag-and-drop canvas.

What we tell customers: use the free months to build one agent on a real process, then decide with real usage data whether the premium price after December is worth it. Building three demo agents and then facing a bill nobody planned for is the scenario to avoid.

Agents, gateways and governance

SAP wants every agent to be callable from outside and controllable from inside. In the keynote, SAP stated that every agent is natively an A2A (agent-to-agent) endpoint, and that agents not verified in SAP AI Agent Hub “cannot be invoked” at runtime (SAP keynote recap). That is the right default. Prima vista it sounds like bureaucracy; in practice it is the difference between an agent inventory and agent sprawl.

Two gateways are easy to mix up:

• The agent gateway connects agents across landscape boundaries, so that third-party agents can call Joule Agents. SAP called it generally available at TechEd; enhanced interoperability is rolling out in phases.
• The SAP Enterprise AI Gateway is a layer on SAP Integration Suite for authentication, policy enforcement, routing, rate limiting and audit. It is planned for Q1 2027.

If you already run SAP Integration Suite, the second one will feel familiar. API management for agents is still API management. The questions do not change: who may call what, with which identity, and who sees the log.

The AI Governance Assistant is aimed at the EU AI Act and produces an audit-ready risk classification. SAP is releasing it to Early Adopter Care customers in November 2026. Swiss companies are not automatically out of scope: under Article 2 of the AI Act, the regulation also covers providers that place AI systems on the EU market and providers and deployers outside the EU whose AI output is used in the EU.

Data: Knowledge Graph, Ontology Manager, Dremio

Agents are only as good as the data they can reach and understand. SAP’s TechEd data announcements add a Dremio-based lakehouse to Business Data Cloud (planned GA Q1 2027 per SAPinsider), more native Databricks capabilities, SAP Reltio for master data management, and the Ontology Manager to enrich the SAP Knowledge Graph with your own business concepts.

The Knowledge Graph also plays a role in Joule Studio: SAP uses it to find the right APIs, MCP servers and data products for an agent. Concretely, that means the quality of your API documentation and data products affects how well SAP’s tooling can build on them.

We keep a BDC timeline from 2025 to 2026 and explain the data layer on our Business Data Cloud page. TechEd confirms the direction rather than changing it.

What developers got this year, away from the keynote

SAP’s TechEd press release and keynote recap don’t mention ABAP or CAP. The release notes do. The MCP adapters in CAP and the ABAP MCP server are generally available; CAP-level agents are still experimental.

CAP. In its September 2026 release, CAP made the MCP adapters generally available for Node.js and Java. A CAP service can be exposed as MCP tools to an AI client with annotations, not glue code. CAP-level agents (@agent services served via A2A) are labelled Gamma for Node.js and Alpha for Java. The October release added OpenTelemetry traces and token metrics for agents and MCP.

ABAP. SAP’s ABAP update of 18 August 2026 states that the ABAP MCP server for Eclipse and Visual Studio Code is generally available, and that ABAP development in Visual Studio Code started in Q2 2026, initially for the ABAP Cloud scope. SAP also released its first agent for custom code migration in Q2 2026; the article scheduled a clean-core transformation agent for Q3 2026, and we have not confirmed its current availability. The same article confirms the shift from per-user billing to usage-based “AI units”.

For S/4HANA Public Cloud teams, this matters more than any keynote demo. ABAP Cloud plus an MCP server means your coding assistant can read the released objects of your system instead of guessing. We explain the extension options in our post on embedded Steampunk and ABAP Cloud and our clean core approach with CAP. We go through CAP and ABAP with MCP in more detail in a separate post.

Spadoom’s view

We build on SAP BAIP ourselves, so we read TechEd with a practical filter. Engage, our extensions for SAP Sales and Service Cloud V2, runs multi-tenant on SAP BAIP, and our customer integrations between S/4HANA Public Cloud and the CX clouds run on Integration Suite.

The platform pieces (A2A endpoints, verification in AI Agent Hub, MCP in CAP and ABAP) are more mature than the business agents that run on them. So you can design a clean agent architecture now, even if the agent you actually want for your process is still on a roadmap.

What we see in projects is the boring work deciding success: released APIs, documented data, clear ownership of each interface. An agent that calls a badly documented API makes the same mistakes faster. The clean core discipline from the last five years is exactly the groundwork agents need.

What to do now

1. Use the Joule Studio promotions where you are eligible. Pick one process with clear data and a measurable outcome, build one agent before December 2026, and record the usage. That number decides whether the premium agent builder makes sense.
2. Inventory your agents early. Even two pilots belong in SAP AI Agent Hub. Verification becomes a runtime gate, so it pays to start clean.
3. Expose CAP services via MCP where it helps. The adapters are GA. Start with read-only tools, add write actions with human approval.
4. Move ABAP Cloud work to an MCP-aware IDE. Eclipse or VS Code, your choice; the ABAP MCP server is GA for both.
5. Plan the gateway question for 2027. If several systems will call each other’s agents, plan a decision on the SAP Enterprise AI Gateway and ask SAP for its commercial terms.
6. Classify your AI use cases against the EU AI Act if your AI systems or their output reach the EU, with or without SAP’s assistant.

Next step

Want to know which of your processes is ready for a first agent, or how your CAP and ABAP extensions fit the new tooling? Start with our SAP BAIP solution page and the Business AI page, or ask us directly. We look at one process or one extension with you and assess feasibility, prerequisites and where clean data has to come first. For the business view of this year’s announcements, read our Sapphire 2026 summary for Swiss SAP customers.

FAQ

When and where was SAP TechEd 2026?

SAP TechEd 2026 took place from 27 to 29 October 2026 at Messe Berlin, with a virtual edition on the same days. SAP published its main TechEd press release on 27 October 2026 with a Berlin dateline.

Is Joule Studio generally available?

SAP says general availability of Joule Studio is underway in a phased approach. The agent builder is free until December 2026 and then becomes a premium AI feature; the skill builder is a base AI feature. Design-time tooling stays free under fair-use limits, and the SAP-managed runtime is free through December 2026 for select customers.

What is the difference between the agent gateway and the SAP Enterprise AI Gateway?

The agent gateway lets third-party agents call Joule Agents through A2A and MCP; SAP said at TechEd it is generally available today, with enhanced interoperability rolling out in phases. The SAP Enterprise AI Gateway is a separate layer on SAP Integration Suite with authentication, policy enforcement, routing, rate limiting and audit. It is planned for Q1 2027.

Did SAP announce anything for CAP and ABAP at TechEd 2026?

Not in SAP’s TechEd press release or its written keynote recap. The relevant news came through the year: CAP made its MCP adapters generally available for Node.js and Java in September 2026, and SAP made the ABAP MCP server generally available and brought ABAP development to Visual Studio Code from Q2 2026.

Do Swiss companies need the AI Governance Assistant?

The EU AI Act also applies to providers outside the EU that place AI systems on the EU market, and to providers and deployers outside the EU whose AI output is used in the EU. If that describes you, it can apply. SAP announced the AI Governance Assistant, which produces an audit-ready AI risk classification, for Early Adopter Care customers in November 2026. Treat it as a helper for your own classification, not as a replacement for it.