SAP Advanced Event Mesh: SAP's Event Broker Service, Built on Solace Technology

SAP Advanced Event Mesh, formally SAP Integration Suite, advanced event mesh, is SAP’s managed event broker service, and it is built on Solace technology. SAP’s training calls it “a fully-managed event streaming and management service that enables enterprise-grade event-driven architecture”. Solace says it is “powered by Solace”. SAP released it in the third quarter of 2022. It is a different product from SAP Event Mesh, and confusing the two is the most common mistake in this area.

This page sets out the relationship in each company’s own words, what is inside the service, how it compares with SAP Event Mesh, and what it means for a manufacturer that runs SAP. It belongs to Solace integration in the Solace cluster.

How SAP and Solace describe SAP Advanced Event Mesh

The safest way to describe a commercial relationship is to quote the parties. Here is what each says, as of October 2026:

Source	What it says
SAP Learning	A “fully-managed event streaming and management service”. The course describes the service as based on Solace PubSub+ and names its management interface “Solace PubSub+ Event Portal”
SAP Help (advanced event mesh docs)	“A complete event streaming, event management, and monitoring platform”; Event Portal manages events “whether they come from Solace event brokers or other streaming technologies”
Solace, SAP page	SAP has added “hundreds of event objects to SAP Business Accelerator Hub”, designed for “SAP Integration Suite, advanced event mesh, which is powered by Solace”
Solace blog	Advanced event mesh is “powered by Solace” and aligned with SAP BTP

What neither says. The arrangement is widely called an “OEM” deal, but we did not find that word on SAP’s or Solace’s own pages. The commercial terms are not public. So this page uses the wording both companies support: SAP sells advanced event mesh, which is built on Solace technology.

The technical footprint confirms it. SAP hosts the advanced event mesh documentation at help.pubsub.em.services.cloud.sap, and its pages mirror the structure of docs.solace.com. Solace’s GitHub organisation SolaceLabs hosts an aem-sap-integration repository of demo artefacts that asks contributors to consult the “SAP Tiger Team” before changing anything.

What is inside SAP Advanced Event Mesh

SAP’s documentation describes three service areas, and their names match Solace’s own products:

• Event streaming (Mission Control): broker services offering “publish-subscribe messaging pattern, queuing, streaming, replay, and request-reply”, managed through Cluster Manager and Mesh Manager. The Solace equivalents are the Event Broker and Solace Cloud.
• Event management (Event Portal): design, catalogue and governance of events, “whether they come from Solace event brokers or other streaming technologies (such as Kafka)”. See Solace Event Portal.
• Monitoring (Insights): dashboards that detect broker issues early, with Datadog integration according to SAP Learning.

It is not cloud-only. SAP’s docs describe Public Region and Dedicated Region environments, plus broker services in your own virtual private cloud, in Kubernetes “in the cloud or on-premises”, and on-premises deployments. SAP Learning lists AMQP, MQTT, SMF, SMF over WebSockets, REST and JMS as supported protocols.

SAP Advanced Event Mesh vs SAP Event Mesh

SAP Event Mesh (formerly SAP Cloud Platform Enterprise Messaging) is SAP’s own simpler eventing service on SAP BTP. SAP’s comparison material describes it as an in-house development, and advanced event mesh as the Solace-based one. SAP Learning lists the differences:

Dimension	SAP Event Mesh	SAP Integration Suite, advanced event mesh
Maximum message size	1 MB	30 MB
Storage	10 GB	6 TB
Deployment	SAP BTP	AWS, Azure, Google Cloud, on premises and edge
Event management and lifecycle tools	Not listed	Event Portal
Event API products	Not listed	Yes
Message replay	Not listed	Yes
Dynamic event routing and filtering	Not listed	Yes
Distributed tracing	Not listed	Yes

One source conflict to know about. Older Solace pages described its cloud broker as “the digital backbone for SAP Event Mesh”. Current SAP material treats the two as distinct, with advanced event mesh as the Solace-based product. We could not resolve whether Solace technology ever sat under SAP Event Mesh, and it does not change the choice: SAP Event Mesh fits light BTP-internal eventing, advanced event mesh fits enterprise-wide, multi-site, multi-protocol event distribution.

What SAP Advanced Event Mesh means for a manufacturer

For many SAP manufacturers, Solace technology arrives as advanced event mesh. It comes through the SAP contract, the SAP account team and SAP BTP. An architect evaluating “Solace” may already own the same broker technology under another name.

Events can flow both ways. SAP publishes standard event objects in the Business Accelerator Hub. For SAP ECC, the partner ASAPIO Cloud Integrator uses SAP change pointers to extract events and publish them over REST. On the plant side, because the service speaks MQTT, JMS and AMQP, a MES, a warehouse system or a plant broker can exchange events with SAP without a point-to-point interface for each pair. That is the same pattern as our unified namespace guide, extended up to ERP.

Solace states three customer results on advanced event mesh in its SAP partnership post: Farys handles more than two million smart meter readings a day; JDE Peet’s replaced polling with real-time event delivery in its global distribution; and Danone built a real-time system called Cortex across factories and warehouses. Solace’s Danone case study describes an event mesh across more than 100 production sites, integrating MES, WMS, SAP and IoT.

An illustrative scenario. A plant posts goods receipts in SAP from handheld scanners. A downstream MES needs to know before releasing a batch, and today it polls SAP every 15 minutes. With advanced event mesh, the goods receipt becomes an event, the MES subscribes, and the release waits seconds instead of minutes. The same event can feed a quality system and a data platform without new SAP interfaces. The MES selection question “how does it consume ERP events?” becomes a concrete test.

SAP channel or Solace direct? Both routes lead to the same broker technology, so the decision is mostly about the organisation. If the integration team, budget and support relationships already sit with SAP BTP, and most event producers are SAP systems, advanced event mesh keeps everything in one contract. If most producers and consumers are non-SAP, if the plants need self-managed brokers on their own hardware, or if you plan to use the wider Solace integration toolset, buying from Solace directly is worth pricing. In both cases, ask which products and features, such as micro-integrations or Agent Mesh, are included and when new broker releases reach your service.

Where it gets hard

• Two channels for one technology. Buying through SAP or through Solace changes the contract, the support path and possibly the release cadence. Ask SAP how closely advanced event mesh tracks Solace broker releases; we found no public statement.
• Pricing is not public from either company for this service.
• Name confusion costs time. Confirm in writing which product a proposal means: SAP Event Mesh or SAP Integration Suite, advanced event mesh.
• SAP events are not plant events. Business events describe documents and transactions. Plant events describe state and measurements. Keep separate topic trees and owners, and plan the mapping between them.
• Documentation splits. SAP hosts its own copy of the docs; features documented on docs.solace.com may differ in timing. Check SAP’s copy for what your service supports.

---

Related: Solace integration overview · Solace connectors · Solace for manufacturing · Solace hub