NVIDIA and SAP announced on 12 May 2026 that NVIDIA's open-source OpenShell runtime will become the default security layer for all AI agents on SAP Business AI Platform, creating a dual-layer trust architecture that separates infrastructure containment from business-logic governance across finance, procurement and supply chain systems.
Aisha covers EdTech, telecommunications, conversational AI, robotics, aviation, proptech, and agritech innovations. Experienced technology correspondent focused on emerging tech applications.
LONDON, May 18, 2026 — At SAP Sapphire on 12 May 2026, NVIDIA founder and CEO Jensen Huang joined SAP CEO Christian Klein's keynote by video to announce an expanded collaboration that embeds NVIDIA's open-source agent runtime, OpenShell, directly into SAP Business AI Platform. The partnership addresses what many chief information officers regard as the single largest barrier to deploying autonomous AI agents in production: trust. SAP will use OpenShell as the runtime security layer for all its AI agents, including custom agents built in Joule Studio, SAP's environment for building and managing end-to-end enterprise agents. NVIDIA's NemoClaw reference blueprint will also be made available inside Joule Studio, giving development teams a structured path from prototype to governed deployment. This analysis examines the technical architecture of the partnership, its competitive positioning against rival enterprise agent platforms, and the implications for regulated industries that run core business processes on SAP.
Executive Summary
• SAP embeds NVIDIA OpenShell — an open-source runtime providing isolated execution, filesystem-level policy enforcement and infrastructure containment — into SAP Business AI Platform, announced at SAP Sapphire on 12 May 2026.
• SAP engineers are co-designing OpenShell alongside NVIDIA, contributing enterprise-focused hardening back to the open-source project.
• NVIDIA NemoClaw, a reference blueprint for autonomous agent development, will be available natively inside Joule Studio.
• The collaboration creates a two-layer trust model: OpenShell validates whether an agent action can safely execute; Joule Studio's runtime validates whether it should execute at all.
• NVIDIA itself runs finance, supply chain and logistics on SAP, giving both firms shared operational context for governance requirements.
Key Developments
OpenShell as an Enterprise Runtime Security Layer
OpenShell provides three distinct containment mechanisms for autonomous agents: isolated execution environments, policy enforcement at the filesystem and network layers, and infrastructure-level containment designed to guard against damage when agent logic fails. SAP's decision to make OpenShell the default runtime security layer for all SAP AI agents — not merely a plug-in for advanced users — signals the company's view that agent containment must be architectural, not optional. According to NVIDIA's official blog post, SAP engineers are "codesigning OpenShell alongside NVIDIA, contributing back to the open source project," with contributions focused on runtime hardening, policy modelling, enterprise identity integration, and auditing and governance hooks.
The Two-Layer Trust Model
The most significant architectural detail in this announcement is the separation of concerns between two distinct control planes. NVIDIA OpenShell asks: "Can this agent action safely execute?" The Joule Studio runtime — the enterprise control layer within SAP Business AI Platform — asks: "Should this action happen at all?" As NVIDIA stated in its 12 May 2026 blog post, "Together, they close a gap that application-layer security alone cannot." This dual-layer approach means that even if an agent passes OpenShell's technical safety checks — confirming it has not escaped its sandbox, has not accessed forbidden network paths and has not violated filesystem policies — Joule Studio can still block the action on business-logic grounds: wrong role, wrong approval chain, wrong data classification. NVIDIA's NemoClaw reference blueprint gives SAP customers a pre-engineered starting point for building agents that operate within both layers from the first line of code.
Jensen Huang's Five-Layer Framework
Jensen Huang has described AI as a five-layer cake: energy, chips, infrastructure, models and applications. Applications sit at the top, where AI creates economic value. SAP, which runs finance, procurement, supply chain and manufacturing workflows for a significant portion of the world's largest enterprises, occupies a critical position in that fifth layer. Huang's framework contextualises the partnership not as a product integration but as a structural play: NVIDIA controls layers one through four; SAP provides governed access to the application layer where agents must operate within policy, identity and process controls.
Market Context & Competitive Landscape
Microsoft and Copilot Studio
Microsoft's Copilot ecosystem, built on Azure OpenAI Service, remains the most visible competitor in enterprise agentic AI. Microsoft shipped Copilot Studio in 2024 and has since expanded its agent-building capabilities, integrating with Dynamics 365 and Microsoft 365. However, Microsoft's approach to agent security has largely relied on Azure-level identity management and Responsible AI tooling rather than a dedicated, open-source runtime sandbox. The NVIDIA-SAP two-layer model — infrastructure containment plus business-logic governance — offers a more explicit separation of concerns than Microsoft has publicly detailed as of May 2026.
Google Cloud and Vertex AI Agent Builder
Google Cloud's Vertex AI Agent Builder, announced at Google Cloud Next 2025, provides a managed environment for building and deploying agents with grounding in enterprise data. Google's approach emphasises retrieval-augmented generation and tight integration with Google Workspace. But Google Cloud has not yet published an equivalent to OpenShell's filesystem and network-level containment for autonomous agents. For organisations that run core ERP on SAP — rather than on Google-native platforms — the NVIDIA-SAP integration offers a more direct path to governed agent deployment.
Salesforce Agentforce
Salesforce launched Agentforce in late 2024, positioning its platform as the CRM-native agent runtime. Salesforce's Data Cloud provides the grounding layer, and its Einstein Trust Layer handles prompt injection defence, toxicity filtering and audit logging. The trust-layer concept parallels what OpenShell does at the infrastructure level, but Agentforce operates primarily within the CRM domain. SAP's scope — spanning finance, procurement, supply chain and manufacturing — covers a broader set of systems of record, giving the NVIDIA-SAP combination a wider attack surface to defend but also a wider footprint of enterprise processes to address.
| Platform | Agent Runtime | Containment Model | Open-Source Component | Primary ERP Scope |
|---|---|---|---|---|
| SAP Business AI Platform + NVIDIA OpenShell | Joule Studio + OpenShell | Dual-layer (infra + business logic) | Yes (OpenShell) | Finance, procurement, supply chain, manufacturing |
| Microsoft Copilot Studio | Azure OpenAI Service | Azure IAM + Responsible AI tools | Partial (open models via Azure) | Dynamics 365, Microsoft 365 |
| Google Vertex AI Agent Builder | Vertex AI | Google Cloud IAM + grounding controls | No dedicated agent sandbox | Google Workspace, BigQuery |
| Salesforce Agentforce | Einstein Trust Layer | CRM-scoped trust layer | No | CRM (Sales Cloud, Service Cloud) |
Source: Company announcements and official documentation as of May 2026. Competitive details compiled from public disclosures by NVIDIA, Microsoft, Google Cloud and Salesforce.
Industry Implications
Finance and Audit
Financial services firms operating under European Banking Authority guidelines and the EU AI Act face stringent requirements for auditability and human oversight of automated decision-making. SAP's position as the system of record for finance in many global banks means that any agent touching general ledger entries, accounts payable or treasury operations must produce a complete audit trail. OpenShell's governance hooks — combined with Joule Studio's policy engine — give compliance teams two distinct logging surfaces: one at the infrastructure level (what the agent technically did) and one at the business level (why it was allowed to do it). For banks running SAP S/4HANA, this dual audit capability addresses a specific gap that Basel Committee guidance on operational resilience has highlighted since 2024.
Supply Chain and Manufacturing
Manufacturing firms using SAP for production planning and logistics face a different risk profile. An autonomous agent that miscalculates material requirements or triggers an erroneous purchase order can cause physical supply chain disruption. OpenShell's filesystem and network isolation ensures that a malfunctioning agent cannot access adjacent systems — a containment property that matters when agents span procurement, warehouse management and transport logistics. NVIDIA itself runs supply chain and logistics on SAP, as confirmed in the 12 May 2026 announcement, providing the partnership with a live reference deployment.
Healthcare and Government
Public-sector and healthcare organisations subject to GDPR data residency requirements and HIPAA (in US contexts) face particular challenges when deploying autonomous agents against sensitive records. The open-source nature of OpenShell allows security teams to audit the containment runtime's code directly — an important property for government procurement processes that often require source-code review of security-critical components.
Business20Channel.tv Analysis
The Trust Deficit Is the Real Bottleneck
Our assessment is that this partnership matters less for what it enables agents to do and more for what it prevents them from doing. Throughout 2025 and into the first half of 2026, we have tracked a consistent pattern in enterprise AI adoption: organisations prototype agentic workflows rapidly but stall at the governance stage. The SAP-NVIDIA collaboration attacks this bottleneck directly. By making OpenShell the default — not optional — runtime for all SAP AI agents, SAP removes the decision burden from individual project teams. Every agent built in Joule Studio inherits containment by default. That architectural decision is, in our view, more consequential than the technical specifications of OpenShell itself.
Open Source as a Trust Mechanism
SAP's choice to co-develop OpenShell as open source, rather than building a proprietary containment layer, is strategically significant. It allows SAP's enterprise customers — many of whom employ large internal security teams — to inspect, fork and harden the runtime for their own regulatory environments. This is a direct response to a procurement objection we hear repeatedly from CISOs at Business20Channel.tv briefings: "We cannot deploy an agent runtime we cannot audit." Open-sourcing the containment layer neutralises that objection. It also creates a network effect: as more enterprises contribute hardening patches, the runtime improves for all users, including SAP itself.
The NemoClaw Accelerator
Making NVIDIA NemoClaw available inside Joule Studio is a practical accelerator for development teams. Reference blueprints reduce time-to-production by providing pre-validated architectural patterns. For SAP customers, this means a development team building a procurement agent in Joule Studio can start from NemoClaw's reference architecture, inherit OpenShell containment automatically, and focus engineering effort on business logic rather than security scaffolding. We estimate this could reduce agent development cycles by 30–50%* for teams that would otherwise need to build containment infrastructure from scratch.
*Business20Channel.tv editorial estimate based on comparable open-source framework adoption patterns; not sourced from NVIDIA or SAP.
| Layer | Component | Primary Function | Control Type | Audit Output |
|---|---|---|---|---|
| Infrastructure containment | NVIDIA OpenShell | Isolated execution, filesystem/network policy | Technical (can it execute safely?) | Infrastructure-level logs |
| Business-logic governance | Joule Studio runtime | Role, permission and process enforcement | Business (should it execute?) | Business-level audit trail |
| Agent development | Joule Studio + NemoClaw | Build, test, deploy agents with pre-validated patterns | Development lifecycle | Version and deployment records |
| Enterprise data | SAP S/4HANA, SAP BTP | System of record for finance, procurement, supply chain | Data access and classification | Data lineage and access logs |
Source: Architecture details from NVIDIA blog, 12 May 2026. Layer naming and audit output categories are Business20Channel.tv editorial interpretation.
Named Perspectives on the Partnership
"AI agents will create value only when enterprises can trust them with their data. For many organizations, that data is in SAP." — NVIDIA, official corporate blog, 12 May 2026.
"SAP and NVIDIA are making agents ready to act, while staying within the boundaries enterprises require." — NVIDIA, official corporate blog, 12 May 2026.
"An agent that can touch systems of record, cross application boundaries and operate without review at every step needs boundaries, policy enforcement and an audit trail before it can become part of production work." — NVIDIA, official corporate blog, 12 May 2026.
Jensen Huang described AI as "a five-layer cake: energy, chips, infrastructure, models and applications," positioning the application layer as "where AI creates economic value and drives productivity for knowledge workers." — Jensen Huang, Founder and CEO, NVIDIA, as cited in NVIDIA blog, 12 May 2026.
"Together, they close a gap that application-layer security alone cannot." — NVIDIA, official corporate blog, 12 May 2026, referring to the combined OpenShell and Joule Studio runtime architecture.
Why This Matters for Industry Stakeholders
For CIOs and chief digital officers evaluating agentic AI pilots, the SAP-NVIDIA partnership shifts the build-versus-buy calculus. Before this announcement, enterprises wanting to run autonomous agents against SAP systems of record had three options: build bespoke containment infrastructure (expensive, slow, requires specialist security engineering); rely on cloud-provider IAM controls alone (insufficient for autonomous agents that cross application boundaries); or limit agents to read-only, human-in-the-loop assistants (safe but low value). The OpenShell integration creates a fourth option: deploy agents with pre-validated containment inherited from the platform itself.
For chief information security officers, the open-source nature of OpenShell allows direct code inspection — a property that will matter for organisations subject to EU AI Act requirements for transparency in high-risk AI systems. CISOs at SAP customer organisations should be evaluating OpenShell's codebase now, before pilot agents reach production. The risk of not doing so is clear: an ungoverned agent operating inside a system of record can create compliance exposure that extends well beyond the AI system itself.
For SAP's partner ecosystem — system integrators such as Accenture, Deloitte and IBM Consulting — this announcement creates a new service line: agent governance implementation. Integrators that develop OpenShell expertise early will have a first-mover advantage in a market that, by our assessment, will grow significantly as SAP's installed base begins deploying autonomous agents at scale during 2026 and 2027.
Forward Outlook
The partnership announced on 12 May 2026 is an early move in what we expect to be a multi-year convergence between enterprise application vendors and AI infrastructure providers on the question of agent governance. Three developments bear watching over the next 12 to 18 months. First, whether OpenShell attracts contributions from enterprise software vendors beyond SAP — if Oracle, Workday or ServiceNow adopt or fork the runtime, it could become a de facto standard for agent containment. Second, whether the EU AI Act's implementing regulations, expected in final form by late 2026, will mandate specific containment properties for autonomous agents operating in high-risk domains — properties that OpenShell may already satisfy. Third, whether NVIDIA's NemoClaw blueprint evolves from a reference architecture into a broader agent development framework that competes directly with LangChain and Microsoft AutoGen in the open-source agent tooling market.
The open question is whether dual-layer governance — infrastructure containment plus business-logic enforcement — proves sufficient for the most sensitive enterprise use cases, or whether a third layer of real-time human oversight will remain necessary for agents operating in regulated financial and healthcare environments. SAP and NVIDIA have not yet published performance benchmarks for OpenShell under high-concurrency agent workloads, and enterprises planning large-scale deployments will need that data before committing to production rollouts. The trust architecture is sound in principle; the test will be whether it holds under the operational pressures of enterprise-scale agentic AI.
Key Takeaways
• SAP has made NVIDIA OpenShell the default runtime security layer for all AI agents on SAP Business AI Platform, announced at SAP Sapphire on 12 May 2026.
• The dual-layer trust model — OpenShell for infrastructure containment, Joule Studio for business-logic governance — addresses a gap that neither layer could close independently.
• SAP engineers are co-developing OpenShell as open source, enabling enterprise security teams to audit and harden the containment runtime directly.
• NVIDIA NemoClaw, available inside Joule Studio, gives SAP customers a pre-validated blueprint that could reduce agent development cycles by an estimated 30–50%.
• Enterprises in finance, supply chain, healthcare and government should evaluate OpenShell's codebase now, before autonomous agents reach production against SAP systems of record.
References & Bibliography
[1] NVIDIA. (2026, May 12). NVIDIA and SAP Bring Trust to Specialized Agents. https://blogs.nvidia.com/blog/sap-specialized-agents/
[2] SAP. (2026). SAP Sapphire 2026 Conference. https://www.sap.com/events/sapphire.html
[3] SAP. (2026). About SAP — Company Information. https://www.sap.com/about/company.html
[4] NVIDIA. (2026). NVIDIA Official Blog. https://blogs.nvidia.com/
[5] European Commission. (2024). EU AI Act — Regulatory Framework for Artificial Intelligence. https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai
[6] European Banking Authority. (2025). Guidelines on AI in Financial Services. https://www.eba.europa.eu/
[7] Basel Committee on Banking Supervision. (2024). Principles for Operational Resilience (BCBS d584). https://www.bis.org/bcbs/publ/d584.htm
[8] European Union. (2018). General Data Protection Regulation (GDPR). https://gdpr-info.eu/
[9] U.S. Department of Health and Human Services. (2023). HIPAA — Health Insurance Portability and Accountability Act. https://www.hhs.gov/hipaa/index.html
[10] Microsoft. (2026). Microsoft Copilot — Official Page. https://www.microsoft.com/en-us/microsoft-copilot
[11] Microsoft. (2026). Azure AI Services Documentation. https://learn.microsoft.com/en-us/azure/ai-services/
[12] Google Cloud. (2026). Vertex AI — Agent Builder. https://cloud.google.com/vertex-ai
[13] Salesforce. (2025). Agentforce — Official Page. https://www.salesforce.com/agentforce/
[14] LangChain. (2026). LangChain — Open Source Agent Framework. https://www.langchain.com/
[15] Microsoft. (2025). AutoGen — Multi-Agent Framework. https://github.com/microsoft/autogen
[16] Accenture. (2026). Accenture — Technology Consulting. https://www.accenture.com/
[17] Deloitte. (2026). Deloitte — Consulting Services. https://www.deloitte.com/
[18] IBM. (2026). IBM Consulting. https://www.ibm.com/consulting
[19] Business20Channel.tv. (2026). Agentic AI Coverage. https://business20channel.tv/?category=Agentic+AI
[20] NVIDIA. (2026). Jensen Huang — Five Layers of AI. https://blogs.nvidia.com/blog/sap-specialized-agents/
For further reading: NVIDIA CEO Jensen Huang CMU Speech 2026: AI Industrial Era Mes....
About the Author
Aisha Mohammed
Technology & Telecom Correspondent
Aisha covers EdTech, telecommunications, conversational AI, robotics, aviation, proptech, and agritech innovations. Experienced technology correspondent focused on emerging tech applications.
Frequently Asked Questions
What is NVIDIA OpenShell and how does it work within SAP Business AI Platform?
NVIDIA OpenShell is an open-source runtime designed for securely developing and deploying autonomous AI agents. It provides three containment mechanisms: isolated execution environments, policy enforcement at the filesystem and network layers, and infrastructure-level containment that guards against damage when agent logic fails. Within SAP Business AI Platform, OpenShell serves as the default runtime security layer for all SAP AI agents, including custom agents built in Joule Studio. SAP engineers are co-developing OpenShell with NVIDIA, contributing enterprise-focused improvements back to the open-source project. The integration was announced at SAP Sapphire on 12 May 2026.
How does the NVIDIA-SAP partnership affect the competitive landscape for enterprise agentic AI?
The partnership positions SAP and NVIDIA against Microsoft's Copilot Studio, Google Cloud's Vertex AI Agent Builder and Salesforce's Agentforce. The key differentiator is the dual-layer trust model: OpenShell provides infrastructure-level containment while Joule Studio enforces business-logic governance. Microsoft relies primarily on Azure IAM and Responsible AI tooling, Google Cloud has not published an equivalent open-source agent sandbox, and Salesforce's Einstein Trust Layer operates mainly within the CRM domain. SAP's broader ERP scope — covering finance, procurement, supply chain and manufacturing — gives it a wider footprint of enterprise processes to govern, though this also creates a larger attack surface.
What does this announcement mean for enterprises in regulated industries?
For financial services firms subject to European Banking Authority guidelines and the EU AI Act, the dual-layer audit capability — infrastructure-level logs from OpenShell and business-level audit trails from Joule Studio — addresses specific compliance requirements for automated decision-making. Healthcare and government organisations subject to GDPR and HIPAA can benefit from OpenShell's open-source nature, which allows security teams to audit the containment runtime's source code directly. The Basel Committee's guidance on operational resilience, published in 2024, has highlighted the need for exactly this kind of dual-surface audit capability in AI-driven financial processes.
What is NVIDIA NemoClaw and how does it accelerate agent development?
NVIDIA NemoClaw is a reference blueprint for developing and deploying autonomous agents. By making NemoClaw available directly inside SAP's Joule Studio, development teams get a pre-validated architectural pattern that inherits OpenShell containment automatically. This means teams can focus engineering effort on business logic rather than building security scaffolding from scratch. Business20Channel.tv estimates this could reduce agent development cycles by 30–50% for teams that would otherwise need to build containment infrastructure independently, based on comparable open-source framework adoption patterns observed across the industry.
What are the key risks and open questions for enterprises considering this technology?
The primary open question is whether dual-layer governance — infrastructure containment plus business-logic enforcement — will prove sufficient for the most sensitive use cases, or whether a third layer of real-time human oversight will remain necessary in regulated financial and healthcare environments. SAP and NVIDIA have not yet published performance benchmarks for OpenShell under high-concurrency agent workloads, which enterprises planning large-scale deployments will need before committing to production. The regulatory landscape is also evolving: the EU AI Act's implementing regulations, expected in final form by late 2026, may mandate specific containment properties that could validate or complicate the current architecture.