S/4HANA Cloud Private Edition — the RISE bundle, unpacked.

The RISE Private Edition stack, decomposed.

RISE with SAP Cloud Private Edition is a single-SKU bundle that contains: S/4HANA Cloud Private Edition (the application), HANA database, application hosting on a hyperscaler of SAP's choosing (AWS, Azure, GCP, or SAP-managed datacentre), SAP Business Technology Platform credits, SAP Datasphere credits, the Joule generative-AI overlay, and a defined level of application managed service. The list-price unit is the "Full User Equivalent" (FUE), which translates ECC named-user licences into a normalised RISE metric.

The FUE conversion

FUE conversion ratios from ECC user types vary: a Professional User maps to 1 FUE, a Functional User to 5 FUEs, a Productivity User to 30. The translation typically delivers a 60–80% reduction in nominal user count — which then anchors the RISE price. The trap is that FUE counts are forward-looking, not historical: SAP measures actual usage post-go-live and re-prices if the FUE count exceeds the contracted band.

What is bundled, what is not

The RISE bundle covers the S/4 application, HANA database, infrastructure, basic application management. It does not cover: non-S/4 SAP estate (BW/4HANA, Successfactors, Ariba, Concur), industry add-ons priced separately, third-party connectors, custom code remediation. The most common over-spend is buying the RISE bundle to cover the S/4 line then maintaining a separate enterprise agreement for the rest of the SAP estate at unchanged volume discounts.

Who actually picks the cloud underneath.

RISE Cloud Private Edition contractually grants SAP the right to select the underlying hyperscaler. SAP can deploy on AWS, Azure, GCP or SAP-managed infrastructure. The customer's preference is consultable but not contractually binding — unless it is written into the order form. We routinely see customers with significant Azure commit assume their RISE workload will land on Azure, only to find SAP placing it on AWS for SAP's own reasons.

Why this matters

The hyperscaler choice affects: existing committed-use agreements (a $20M Azure MACC is reduced if SAP workload sits on AWS), data residency (SAP-managed regions are narrower than hyperscaler regions), latency to other workloads, and egress costs for inter-cloud integration. The clean fix is a contractual hyperscaler designation in the order form, locked for the term.

Hyperscaler change events

Even with a designation, SAP reserves the right to move workloads between regions or hyperscalers under certain conditions (capacity constraints, regulatory changes, end-of-life). The clause needs to be narrowed: explicit notice period, customer right-to-veto for specified events, no cost-pass-through for SAP-initiated moves.

When RISE is the right answer.

RISE Cloud Private Edition is not the answer for every S/4 migration. Three customer profiles consistently get value from RISE; two consistently lose money. Understanding which one a buyer is in matters more than the price negotiation.

Where RISE wins

Greenfield S/4 implementations with limited custom code, mid-size estates without sophisticated FinOps capability, organisations standardising on a single hyperscaler that matches SAP's preference, and customers who want the application-management bundle as a substitute for in-house Basis capability.

Where RISE loses

Heavily customised ECC estates with significant ABAP custom code, sophisticated FinOps shops who can buy hyperscaler capacity 30–40% cheaper than the RISE pass-through, customers with existing significant hyperscaler commits, and customers running multiple SAP applications where the RISE bundle covers only one. In those cases, S/4HANA on-premises BYOL on the customer's own hyperscaler is typically 20–35% cheaper at five-year TCO.

The clauses that rarely make the draft.

RISE contracts are SAP-standard. The clauses that protect the customer are typically not in the first draft and have to be negotiated in. Six recur in the work we do.

1. FUE recount cadence. The default is annual; negotiate to bi-annual with a defined methodology and a customer audit right.
2. Hyperscaler designation. A named hyperscaler and a named region, with a change clause that requires customer consent.
3. Indirect access carve-out. Explicit treatment of indirect/digital access — what is included, what is metered, what triggers a re-price.
4. Exit ramp. Data export terms, transition assistance, BYOL conversion right at end of term.
5. Service credits. SLA credits with a meaningful cap and a financial credit (not service-day) remedy.
6. Price protection. A capped annual uplift across renewals, not just the first year.

Each of these is achievable inside a RISE deal of any meaningful size. None of them is in the standard template — negotiating them in is the heart of the software contract negotiation work we run on RISE deals.