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.

For service providers · 11

For SAP service providers, the hard part is the switching

If you run SAP operations for several customers, you already know the hardest part is not any single system. It is the switching.

Request a demo All insights

Each customer is reasonable. Together, a lot to carry.

Different landscapes, different access paths, different monitoring setups and different reporting expectations. Each customer's arrangement makes sense on its own. Together they add up to a lot of context for every engineer on every shift.

The result is time spent on tooling instead of engineering, and reporting that takes a different shape for every client.

What a service provider needs from the platform

Strict isolation
Each customer's data, users and roles separated from every other customer's.
Portfolio and single views
The whole book at a glance, or one customer in depth.
Per-customer tuning
Thresholds and escalation that fit each customer's systems.
Shareable evidence
Availability and audit records each customer can see for their own estate.

How FCC supports it

Multi-customer from the start

Per-customer isolation is part of the design, not a configuration convention.

Customer-scoped roles

Customer administrators and read-only customer users see their own estate only.

Thresholds and escalation per customer

Because their systems behave differently.

Per-system pricing

A commercial model that grows with your book of business.

The aim is simple: fewer tools to run, and more time for the engineering work your customers actually pay for.

Go deeper

Use cases

How service providers and in-house teams use FCC.

Pricing

Per-system pricing.

Common questions

Can my customers log in themselves?

Yes. Customer-scoped roles let a customer see their own systems and reports without seeing anyone else's.

Can thresholds differ per customer?

Yes. Thresholds and escalation are set per metric and per customer.

Compare notes on how you operate today.

If you run an SAP managed service, we would like to hear what slows your team down. 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.