Extended maintenance to 2030 does not cover Solution Manager monitoring.Read what SAP actually says

ENDETR
Book a demo

On-premise SAP monitoring

Every SAP monitoring vendor is adding AI.
We ship ours turned off.

LynxOps runs entirely inside your network — monitoring, alerting, anomaly detection, event correlation. No LLM. No cloud call. Nothing leaves. When you want AI root-cause analysis, you switch it on, you pick the provider, and we redact the prompt before it goes.

Book a 30-min demoSee the architecture
  • Kubernetes, Docker, or bare metal
  • 12 SAP transactions over native RFC — no SAP GUI
  • The default install makes zero outbound requests
Default deployment
Your network
SAP / HANA
LynxOps agent
LynxOps server

Runs on your hardware

  • Anomaly detection
  • Event correlation
  • Alerting & dashboards
AI providerOptional · off by default · prompt redacted

No outbound requests in this configuration.

12

SAP transactions over RFC

0

Outbound calls by default

22MB

Agent binary, SAP build

< 2h

Pilot on 3–5 hosts

What you actually get

A monitoring console, not a wrapper around one

Native RFC. No screen-scraping.

LynxOps reads SAP the way SAP expects to be read — over native RFC, with no SAP GUI in the path and no core modifications. Work processes, jobs, syslog, dumps, workload, transports, locks, sessions, IDocs and privileged users, alongside HANA, Oracle, SQL Server, PostgreSQL and the OS layer underneath them.

Platform

Covered transactions

  • SM66Work processes
  • SM37Background jobs
  • SM21System log
  • ST22ABAP dumps
  • ST03NWorkload
  • STMSTransports
  • SUIMPrivileged users
  • SM12Lock entries
  • SM04Sessions
  • USR02User audit
  • IDOCInterface docs
  • DBHANA · Oracle · MSSQL

Why teams pick it

Built for landscapes whose data cannot leave the building

01

Unplug the internet. It still works.

Not a degraded mode — the default install

Anomaly detection, event correlation, alerting and dashboards make zero LLM calls and zero outbound requests. Put LynxOps in a VLAN with no route out and nothing breaks. AI is a layer you switch on later. Or never.

02

Redacted AI, not blind AI

You pick the provider · you hold the key

When you do turn AI on, secrets, IPs, hostnames and emails are stripped from the prompt before it leaves — replaced with consistent pseudonyms (HOST_1, IP_1) so correlation across alerts still works without exposing your landscape. Every suggestion waits for an operator. Nothing executes on its own.

03

SAP depth, not SAP as a plugin

The main subject, not an extension

General-purpose APM reaches ABAP through remote polling, and reads a workload snapshot from outside. LynxOps treats SAP as the product: native RFC into the transactions a Basis team actually opens, correlated with the database and OS underneath.

Alert context

ST22 dump on host sap-prd-01 (10.34.12.31), user MMUELLER, short dump TSV_TNEW_PAGE_ALLOC_FAILED in program ZFI_POST

Sent to the provider

ST22 dump on host HOST_1 (IP_1), user USER_1, short dump TSV_TNEW_PAGE_ALLOC_FAILED in program ZFI_POST

Redaction, shown

What we send when AI is on

The error keeps its meaning. Your landscape keeps its anonymity.

Same pseudonym every time, so correlation across alerts survives. The dump type and program name are kept — they are what makes the diagnosis possible, and they identify nothing.

The 2027 problem

Your monitoring will not die. It will freeze.

Mainstream maintenance for SAP Solution Manager 7.2 ends 31 December 2027. It keeps running after that — you hold a perpetual licence. What stops is the maintenance: no new corrections, no new support packages, no legal changes, no new platform support.

"But we have extended maintenance until 2030."

Check the scope. SAP lists it explicitly: requirements management, project management, process management, test suite, change control management, IT service management and landscape management.

Application Operations — technical monitoring — is not on that list.

Everything outside that list moves to customer-specific maintenance in 2028. Extended maintenance or not.

And SAP does have an answer: Focused Run.

It is on-premise, it is monitoring-specific, and it stays in mainstream maintenance past 2027. It is also, in SAP's own words, the one piece that "needs to be licensed separately" — while Solution Manager and Cloud ALM are covered by maintenance.

So the real question in 2028 is not whether your monitoring survives. It is whether it freezes, or whether it starts sending you an invoice for something that used to be free.

The full picture, with sources
Sources: SAP — Solution Manager 7.2 maintenance scope · SAP — ALM FAQ (extended vs. customer-specific maintenance) · SAP — Transition to SAP Cloud ALM

Structural differences

LynxOps vs SAP Cloud ALM

Only rows SAP's own documentation settles

LynxOpsSAP Cloud ALM
Runs on-premiseSaaS only
Air-gapped deployment
Data stays inside your network
Native SAP RFC depth12 transactionsCloud-centric scope

SAP, on Cloud ALM and on-premise landscapes:

“SAP Cloud ALM is intended for cloud-centric solutions. This means on-premise-centric solutions will be only covered to a certain degree.”

Where we are

We are new. Here is how we de-risk that.

You will not find a hundred logos on this page. We are not going to borrow someone else's, either.

A named engineer

The person who installs it wrote it. Not an SDR, not a partner, not L1.

A 30-day pilot

In your landscape, next to your existing tools. If it does not hold up, walk away.

Your data, in writing

Core monitoring makes zero external calls. That is a contract term, not a docs page.

No data leaves during the pilot

Including the pilot. Especially the pilot.

Your SolMan monitoring has a support end date.
Your replacement does not have to be a cloud.

Book a 30-min demoTalk to an engineer

30-day pilot in your own landscape. You will talk to an engineer, not an SDR.