RISE bundles the migration and the subscription. On premise keeps the control and the capex profile. The CIO call hinges on five variables, not on which deck SAP lands first.
SAP RISE bundles S/4HANA, the hyperscaler infrastructure, and the managed service into a per FUE subscription. S/4HANA on premise keeps the licences as capex, the hosting decision separate, and the upgrade calendar in the buyer's control. The right choice depends on five variables that the SAP account team rarely puts in writing.
The RISE pitch is a clean migration plus subscription. The on premise model is a slower change with more buyer control. Both options run S/4HANA. The choice is not what to run. The choice is who controls the run.
This page maps the variables that drive the call. Five year cost, control posture, customisation friction, indirect access exposure, and exit rights. The buyer side calendar starts the model at 270 days out, not 60.
RISE with SAP is a managed cloud subscription. On premise is a perpetual deployment the customer runs.
RISE is the SAP subscription that bundles S/4HANA Cloud Private Edition, the underlying hyperscaler infrastructure, the SAP application managed service, and a small set of supporting capabilities into a single per FUE contract. The hyperscaler is selected at signing. SAP runs the upgrades on a fixed cadence.
S/4HANA on premise is the traditional perpetual licence model. The customer buys or migrates the licences, runs them on chosen infrastructure, and pays SAP annual support. The infrastructure choice can be on premise data centre, private cloud, or hyperscaler outside RISE.
GROW with SAP is the midmarket public cloud edition. It is not directly comparable to either option here. See the RISE versus GROW decision framework.
Modelling the five year total is the most important step.
RISE versus on premise. Five year total at 500 FUE indicative scale
| Line item | RISE | On premise | Notes |
|---|---|---|---|
| FUE subscription or licence base | High | Medium | RISE bundles infra and managed service |
| Annual escalator | 2.5 to 5 percent | Support fee increase per renewal | Negotiate cap on both |
| Infrastructure | Embedded | Separate | Hyperscaler EDP applies on premise side |
| Managed service | Embedded | Separate | Partner or in house on premise side |
| Five year total | Higher in most large estates | Lower at scale, higher at small scale | Run the model before scope lock |
Control posture is the second decision variable.
SAP owns the upgrade calendar, the patch schedule, the operational SLAs, the change control process, and the third party tool envelope. Customers contract through SAP's managed service framework. Custom code is permitted within the SAP defined boundaries.
The customer owns every operational decision. Upgrade timing, patch cadence, infrastructure design, third party integrations, custom code, and change control all sit inside the customer.
RISE reduces the operational headcount the customer needs. On premise keeps the operational sovereignty. Highly regulated industries with bespoke S/4HANA customisation typically favour on premise. Lean IT operations with standard processes typically favour RISE.
Indirect access calculation differs materially between the two models.
RISE uses the digital access document model. Inbound documents from external systems create chargeable events. SAP RISE digital access sizing must be set at signing. Underestimating the document count creates a true up at year two or three.
On premise indirect access exposure is governed by the master agreement signed before the digital access model existed for older customers, or by the digital access document model for newer agreements. Both can be negotiated as part of the on premise renewal cycle.
The standard SAP account team pitch is that RISE is the strategic direction and on premise is legacy. We disagree. In roughly two out of three large enterprise estates we have modeled in the last 24 months, the five year RISE total runs above the on premise equivalent and the operational risk profile is materially different. The buyer side move is to run both five year models in parallel, force a written confirmation of the migration path support window if on premise is chosen, and use the comparative number as the negotiation anchor.
Source: Redress Compliance advisory engagement file, 2023 to 2025.
RISE is sold as a migration. It is a contractual rewrite. Read the master agreement before the migration deck.
Exit posture is the variable most procurement teams underweight.
RISE is a fixed term subscription. At end of term the customer must either renew, migrate to on premise, or migrate to another platform. SAP controls the transition window. Data extraction support is hourly billed beyond a small allowance.
On premise licences are perpetual. The customer can step off SAP support, run third party support, or migrate to a different platform on the customer's calendar. The perpetual right remains in place.
The decision tree turns on five variables.
Build the five year model with both options to the same scope. If RISE is more than fifteen percent above the on premise total, on premise is usually the right answer at scale.
If the estate carries heavy customisation, regulated workloads, or non standard integrations, on premise is usually the right answer. If the estate is standard and lean, RISE is workable.
If the customer cannot staff a Basis and security operations team, RISE removes the headcount problem. If the customer already has that team, RISE reduces the team's role without removing the cost.
Model the digital access document count carefully under RISE. If the model is volatile, on premise digital access is easier to control.
If the customer wants the perpetual right and the option to step off support, on premise is the answer. If the customer accepts subscription discipline, RISE is workable.
Usually yes at large scale. The five year RISE total runs above the on premise equivalent in about three out of four large estates we have modeled. Always run the model with the same scope on both sides.
No. The base RISE FUE covers the core S/4HANA functions. Many add on modules sit outside the FUE and carry their own subscription line. Read the SAP product list before scope lock.
Not without a contract event. RISE is a multi year subscription. The move is treated as an early termination plus a new contract. Negotiate the step down right at signing.
Not necessarily. On premise here refers to the perpetual licence model. The deployment can sit on customer data centre, private cloud, or hyperscaler outside RISE. The licence type is what defines on premise.
RISE uses the digital access document model. Inbound documents from external systems create chargeable events. Underestimating the document count creates a true up at year two or three. Always size carefully.
Twenty two to thirty eight percent below the SAP first quote is the workable range with a properly prepared buyer side. The lever is the FUE count, the tier price, and the term length.
Third party support is a credible answer if the customer is not running new SAP innovation roadmap items and accepts the absence of new SAP feature releases. Model the support window before stepping off.
Open with the five year model on both sides before any SAP scoping deck lands. The model is the negotiation. The deck is the response.
RISE versus on premise, GROW for midmarket, indirect access exposure, SuccessFactors HRIS commercial posture, Ariba module sequencing, and the audit defense framework across the SAP estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next SAP renewal cycle.
RISE is sold as a migration. It is a contractual rewrite. Read the master agreement before the migration deck.
