Market overview
The SAP AI-agent landscape. As of September 2026.
If you are evaluating AI agents for SAP, you have more options today than a year ago. We track this market systematically — it is our field of work. This page summarises what vendors themselves claim: linked, dated, without judgment. The market moves fast; every statement holds for the date shown.
The starting point
SAP Joule.
Joule is SAP's AI assistant, and access to it is tied to SAP's cloud contracts: it is available natively in S/4HANA Cloud — Public and Private Edition — via RISE with SAP or GROW with SAP. Classic ECC, Business One, and on-premise S/4HANA estates without RISE are outside its native reach (SAP Note 3632703, updated June 2026). Those estates are exactly where we work. At Sapphire 2026, SAP announced it will extend selected Joule assistants and agents to ECC and on-premise S/4HANA systems — for customers who commit the majority of their landscape to RISE (SAP News Center, 14 May 2026) and enroll in the Max Success Plan; per SAP's own Sapphire 2026 Innovation News Guide, general availability is planned for Q4 2026; as of September 2026 it had not been confirmed. Pure on-premise estates without a RISE commitment remain outside the programme.
Where a customer runs Joule, we don't replace it — aplexio Copilots integrate as A2A peers. Our difference is private deployment on open-weight models: a different product answering a different buyer concern.
Independent vendors
Six vendors, six different approaches.
What they ship, which SAP estates they reach, how they handle write-back — and which language they show up in. All read from the linked vendor pages on September 7, 2026.
CLARITY
Pre-built AI agents for revenue operations, “ERP-transaction ready”: validated sales orders and invoices post directly in SAP S/4HANA or ECC. Invoices within tolerance on price, quantity, and tax “auto-post in MIRO without human intervention”, per their own copy; critical workflows run with human-in-the-loop validation. On-premise or cloud deployment, no RISE with SAP requirement. German-language site since May 2026. Named customers: none on the pages we read.
ChatFin
AI agents for finance and accounting teams. The homepage advertises connections to 16 ERPs including SAP Business One and positions the agents as draft-first with human approval; the Business One page, by contrast, advertises touchless automation for routine tasks across AP, AR, reconciliation, and close workflows — “without any human intervention for routine tasks”, at a 70%+ touchless rate. The approval model varies by workflow. The B1 connection runs over the Service Layer plus an MCP server. ChatFin makes no explicit ECC-native claim — ECC appears as a hybrid sidecar next to S/4HANA. English only.
enosix arnold
Connects AI assistants directly to live SAP over the Model Context Protocol — the documentation lists SAP ECC and SAP S/4HANA as supported customer-managed systems. Users retrieve live data and execute SAP business processes in natural language. Available for Microsoft Copilot, Salesforce Agentforce, ServiceNow, and other MCP-compatible AI hosts.
Neptune Software
A platform for teams to build and run business applications and AI agents directly on SAP ECC and S/4HANA — without middleware and without copying business data outside SAP. The MCP Designer turns SAP functionality into AI-ready tools. Named references: Johnson & Johnson, Vattenfall. Not a packaged business agent — a development platform.
ABAPilot (Crimson Consulting SL)
A pure ABAP add-on for ECC 6.0 and above plus on-premise S/4HANA, with an MCP server on your own network — “No RISE. No BTP.” Read-only by default; writes only after explicit configuration. With local models, per the vendor, nothing leaves your network. Focused on queries and ABAP development tooling. Since September 2026 there is a Community Trial: installed via abapGit, read-only for customer repository objects and business data — writes stay confined to a resettable lab report. Website in English and Spanish; a first German-language guide appeared in September 2026, the product page remains in English and Spanish. Named customers: none.
superkind
A German consultancy building “KI-Mitarbeiter” (AI co-workers) for mid-market companies. Agents read and write on ECC, S/4HANA, and Business One — via BAPI, OData, RFC, and IDoc. Every new use case starts read-only or with full human approval; auto-posting only above a confidence threshold. EU-sovereignty option, per-use-case pricing. Custom build, not a product.
Where we fit
Where aplexio fits into this picture.
Several vendors now reach ECC natively — reach alone is no longer a differentiator. Three things still are, as the market reads today.
Read-only by construction
Others ship agents that can write and are configured not to. Our diagnosis agents take SAP exports as input and have no write path into SAP — nothing to misconfigure, bypass, or accidentally enable. That is a property of the build, not a setting.
Diagnosis shaped like exceptions
Not a horizontal ask-anything assistant, but built workflows for specific exceptions: triaging IDoc and EDI errors, clearing delivery blocks, explaining freight-cost variances. Input: the exports your people already pull from SAP. Output: root cause and next action.
Delivery with no aplexio backend
Open-weight models in your own tenant or on-premise, at an engagement size that fits the mid-market — weeks, not programmes. No aplexio backend, no telemetry, nothing that talks to us after handover.
Caveat
An honest caveat.
Vendors change features, pricing, and commitments quickly. Every claim on this page is the vendor's own — linked and dated as of September 2026, not independently tested by us. If you spot something outdated, tell us.
Hold us to the same standard.
In the fit call we show the architecture and the data flow behind every sentence on this page.