Does the agent need inbound network access to my SAP hosts?

No. The agent is outbound-only. It polls Farrenio over HTTPS for its config and pushes metrics the same way. No new firewall rules, no exposed ports on your SAP boxes.

Can my service desk see alerts without touching production?

Yes. The service_desk role is read-only on alerts and incidents, with no SAP transaction access, no config changes and no token reveal. Granular per-action RBAC means you can carve out exactly what each team sees.

How long does a proof of concept take?

A 30-minute call to scope. We typically have one production SID streaming live metrics within an hour of agent install, and the rest of the landscape follows as fast as you can roll out the package.

Why we built it · 01

Is the SAP landscape healthy right now? That answer should take one screen.

Every SAP team can answer "is the landscape healthy right now?". The trouble is the time it takes, the number of tools involved, and how much the answer depends on who happens to be on shift.

Request a demo All insights

The answer exists. It just arrives late.

A typical morning check still looks the same in many landscapes: a logon per system, SM37 in one window, SM50 in another, the HANA cockpit somewhere else, and a spreadsheet that someone updates on Monday mornings. Each tool is good at what it does. Together they make the status of the estate something you assemble by hand.

Landscapes have also changed shape. On-premises and cloud side by side, ECC and S/4HANA running in parallel for years, HANA underneath a growing share of it. The operating model did not follow. It is still one screen per system and one specialist per question.

The cost is rarely a dramatic outage. It is the slow drain of specialist hours on routine checks, the incident that users report before tooling does, and the status report that is out of date by the time it is read.

What a control layer for SAP operations should give you

One view of the estate
Every system, every SID, with the system name already attached to the answer.
SAP-level depth
Work processes, jobs, dumps, locks and HANA health, not only CPU and disk.
Signals that become actions
Thresholds that fit each system, escalation by severity, and procedures that run the same way every time.
Evidence for management
Availability and audit records that hold up when someone asks how a number was calculated.

What Farrenio Cloud Control is

SaaS, in the browser

A browser and an account. No platform infrastructure to build or run.

ECC, S/4HANA and HANA

The ABAP stack and the database in the same console.

Outbound-only collector

A lightweight agent on each SAP host connects out over HTTPS. Nothing listens on the host.

Built for teams

Granular roles, per-customer isolation and an audit trail behind every privileged action.

FCC does not replace SAPGUI, and it does not replace your infrastructure monitoring. It is the SAP-aware operational layer that sits between them.

Go deeper

Topic

SAP Basis monitoring

SM50, SM37, ST22 and related transactions, across every system.

Topic

SAP HANA monitoring

SYSTEMDB and tenant databases in one operational view.

Capability

Security and audit

How access is scoped, credentials protected and actions recorded.

Common questions

Is FCC available today?

Yes. FCC is in Beta and running against real SAP systems. Beta participants work directly with the team building it.

Does FCC replace SAP Solution Manager?

It covers the technical monitoring and operations layer. Full ALM functions such as ChaRM, test management and process monitoring stay with SolMan or SAP Cloud ALM.

See your own landscape on one screen.

Start with one system you know well and judge FCC on your own data. FCC is in Beta.

Request a demo See pricing

"SAP" and SAP product names are used descriptively. Farrenio Cloud Control is a Farrenio product and implies no partnership with or endorsement by SAP.