S/4HANA deployment models. The licensing decision underneath.

S/4HANA licenses differently across on premise, RISE private cloud, GROW public cloud, and hyperscaler hosted models. The choice sets your metric, your lock in, and your leverage for a decade.

What are the deployment models and how do they license?

S/4HANA runs under four commercial models: on premise perpetual, private cloud subscription through RISE, public cloud subscription through GROW, and hosted on premise licenses on hyperscaler infrastructure. Each carries a different metric, a different lock in profile, and a different negotiation posture.

The licensing question is inseparable from the infrastructure question. Choosing the model chooses your leverage for the next decade.

Treat the four options as bids in a competition, not as steps toward a foregone RISE conversion. The moment SAP believes the destination is fixed, every remaining number moves in its favor.

The four models in brief

• On premise perpetual: FUE or legacy named user metrics, capex model, maximum control and maximum operational responsibility.
• RISE private cloud: FUE subscription bundling software, infrastructure, and basis operations per the RISE with SAP offering.
• GROW public cloud: subscription on the public cloud edition per GROW with SAP, fastest standardization, least flexibility.
• Hyperscaler hosted: perpetual licenses on AWS, Azure, or GCP infrastructure, keeping license and infrastructure negotiations separate.

The metric that does the work

Full User Equivalents price user types at different weights, and the FUE count, not the headline rate, sets the envelope. Sizing FUE from measured authorization usage rather than contracted named users cut envelopes materially in our engagements.

How does each licensing metric work per model?

Each model measures demand differently, so a fair comparison starts by normalizing all four to the same unit of consumption.

On premise contracts still recognize legacy named user categories and engine metrics, though new S/4HANA orders increasingly price on Full Use Equivalents. RISE and GROW price almost entirely on FUE. Hyperscaler hosted keeps whatever perpetual metric your existing agreement already carries.

How do Full Use Equivalents convert users?

An FUE is a weighted unit. Light users count as a fraction of one, and heavy users count as a full unit. The FUE total, not the per unit rate, sets the commercial envelope.

SAP groups authorizations into tiers and applies a published conversion ratio to each. Commonly referenced public ratios weight one Advanced Use user at 1 FUE, five Core Use users at 1 FUE, and thirty Self Service users at 1 FUE. Confirm the exact table on your own order form.

The user mix matters more than the raw headcount. A population contracted as Advanced Use but working at Core Use level inflates the FUE envelope before any discount applies.

Measure real authorization usage first, then challenge the tier split SAP proposes. The classification argument happens once, and it compounds across every renewal of a subscription model.

Where does Digital Access sit across the models?

Digital Access, SAP’s document based license for indirect use, applies under all four models and is quoted separately from FUE.

SAP counts nine document types, including sales, invoice, purchase order, and financial documents. Interfaces from third party systems that create these documents trigger the charge. The Digital Access evaluation service helps size the count, but the baseline itself is negotiable.

How do the models compare on cost and lock in?

Subscription models trade capex for embedded lock in: at term end, stopping payment stops the system. Perpetual models keep usage rights through any dispute. That asymmetry is the negotiation context for every other term.

Lock in is not automatically bad; it can buy simplicity and a single accountable vendor. The error is paying for it without pricing the alternative that keeps rights and leverage in your hands.

The conversion credit question

Moving from perpetual to RISE surrenders bought assets for subscription credits. Credit treatment varied by double digit percentages across comparable 2024 to 2025 deals, which makes the credit line a negotiated term, not a formula.

Where the common advice on S/4HANA models is wrong

The standard advice is that RISE is the strategic default and on premise is legacy thinking. We disagree. In roughly 25 to 35 engagements we advised in 2024 to 2025, the customers with the strongest decade economics were the ones who priced all four models against their own infrastructure strategy and made SAP win the comparison. Several closed hyperscaler hosted perpetual deals at materially better ten year cost than the RISE proposal, with leverage intact at every renewal. The buyer side move is to make the model choice a competition, not a conversion.

25+

S/4HANA engagements advised 2024 to 2025

4

Commercial models to price every time

2027

ECC mainstream maintenance horizon

Source: Redress Compliance advisory engagement file, 2024 to 2025.

RISE is a fine answer and a terrible default. Make SAP win the model comparison against your own numbers.

What does each model cost over five years?

Over five years the models diverge less on sticker price than on who absorbs infrastructure, basis operations, and renewal uplift.

On premise front loads capital on licenses and hardware, then runs on annual maintenance of roughly 22 percent of net license value. The rights are yours to keep once paid.

RISE and GROW fold software, infrastructure, and basis operations into one recurring fee. That fee resets at each renewal, and the reset is usually upward unless a cap is written in.

Hyperscaler hosted keeps the perpetual license line separate from a cloud infrastructure contract you negotiate directly with AWS, Azure, or Google Cloud.

Which cost lines does SAP tend to understate?

Two lines drive most of the surprises: renewal uplift on subscriptions and basis labor on self managed estates.

Subscription proposals rarely show the year six renewal step, so a five year quote can hide a double digit percentage increase that lands the moment leverage is gone.

Self managed models understate the internal basis and infrastructure headcount you carry, which is real cost even when it never appears on an SAP invoice.

How do you normalize the comparison?

Put every model on one spreadsheet with the same assumptions and the same horizon before you read any SAP number.

A model that wins on year one price often loses on year five once uplift, hosting, and exit are added. The only comparison SAP cannot reframe is one you build yourself on shared assumptions.

1. Same horizon: model all four across a full five year window, not a single year.
2. Same scope: add hosting and basis labor to perpetual models so the comparison is honest.
3. Same renewal: apply a modeled uplift to subscription years six and beyond.
4. Same exit: price the cost of leaving each model at the end of the term.

What contract terms change by deployment model?

The deployment model rewrites the contract, not just the price, because subscription and perpetual agreements protect the buyer in opposite ways.

Perpetual on premise gives you a standing usage right and a fresh negotiation at every maintenance renewal. Subscription concentrates all leverage at the single signature that starts the term.

Which subscription clauses should you fix at signature?

On a subscription model, the terms below are far cheaper to secure before signature than to claw back at renewal.

• Renewal cap: a fixed ceiling on the percentage increase at each renewal.
• FUE elasticity: the right to reduce the committed FUE count, not only to add.
• Exit assistance: a defined period of data extraction support at term end.
• Digital Access lock: a fixed document baseline so indirect use does not reprice mid term.

How should a CIO sequence the decision?

Run the model comparison before the migration architecture locks, because the ECC maintenance deadlines set the clock and SAP negotiates hardest against customers who have already chosen.

1. Baseline: measure actual usage and authorization data; size FUE honestly.
2. Model pricing: price all four models over ten years including exit scenarios.
3. Credit negotiation: treat conversion credits as a negotiated term with benchmarks.
4. Signature: concentrate protections at signature on subscription models; that is where the leverage lives.

The indirect access overlay

Digital access pricing follows the deployment model into every option. Settle the document based position before conversion, because unresolved indirect access exposure prices into the RISE envelope at SAP's number, not yours. See the ECC to S/4HANA migration playbook for the sequencing.

Bring a measured document count and a defensible interpretation to the table. A quantified baseline turns an open ended indirect use liability into a line item you can cap and forecast.

Anchor the whole decision to your own numbers rather than the reference architecture SAP presents. The customers who keep leverage are the ones who arrive with a costed model already built.

How should migration sequencing differ by model?

Sequence the licensing decision ahead of the technical migration, because the model you pick determines which contract you are negotiating.

A move to RISE or GROW is a commercial conversion first and a technical project second. A move that keeps perpetual licenses on a hyperscaler is mostly a technical project with the contract left intact.

What does a model aware sequence look like?

The order below keeps leverage on your side of the table through the whole program.

1. Entitlement baseline: reconcile owned licenses and measured usage before any quote.
2. Model shortlist: price all four models against the same five year assumptions.
3. Indirect access cleanup: settle Digital Access exposure before it prices into a subscription.
4. Credit and cap negotiation: lock conversion credits and renewal caps in the same signature.
5. Technical migration: begin the system conversion only after the commercial model is fixed.

Reversing this order is the common and costly mistake. Once the architecture assumes RISE, the comparison is effectively over and SAP prices accordingly.

Keep a credible second model funded and staffed until signature day. A live alternative is the single most reliable source of discount, and it costs nothing to hold open. SAP negotiates hardest against buyers who have already decided, so stay undecided on paper until the ink is dry.

SAP commits to support S/4HANA through 2040 under its maintenance strategy, so the model choice, not the platform end date, is the real deadline.

What to do next

1. Measure actual SAP usage and authorization data before any model conversation.
2. Price all four deployment models over a ten year horizon including exit.
3. Model the conversion credit as a negotiated range, benchmarked against comparable deals.
4. Resolve indirect access exposure before it prices into a subscription envelope.
5. Concentrate contractual protections at signature on any subscription model.
6. Keep a credible second model alive until signature day.

Start with the SAP practice or the SAP knowledge hub. Model the RISE numbers in the RISE TCO calculator.

Frequently asked questions

What are the SAP S/4HANA deployment model options?

Four: on premise perpetual licensing, RISE with SAP private cloud subscription, GROW with SAP public cloud subscription, and perpetual licenses hosted on hyperscaler infrastructure. Each carries different metrics, lock in, and negotiation leverage.

Is RISE with SAP always the best S/4HANA option?

No. RISE fits some infrastructure strategies, but in our 2024 to 2025 engagements several customers closed hyperscaler hosted perpetual deals at better ten year economics with leverage intact at every renewal. Price all four models and make SAP win the comparison.

What is an FUE in S/4HANA licensing?

A Full User Equivalent, the S/4HANA metric that weights user types differently against a total count. The FUE number drives the envelope, so size it from measured authorization usage rather than contracted named users.

What happens to perpetual licenses when converting to RISE?

They are surrendered for conversion credits against the subscription. Credit treatment varied by double digit percentages between comparable deals we benchmarked, which makes the credit a negotiated term, not a fixed formula.

How does indirect access affect the S/4HANA model decision?

Digital access exposure follows you into every model, and unresolved exposure prices into a RISE envelope at SAP preferred number. Settle the document based position before any conversion negotiation.

What is the difference between RISE and GROW with SAP?

RISE with SAP is the private cloud edition for customers that need configuration and single tenant control, while GROW with SAP is the public multi tenant edition for standardized adoption. RISE allows deeper customization; GROW trades flexibility for faster, cheaper standardization.

How are FUE conversion ratios structured?

FUE ratios weight users by authorization tier, with commonly referenced public ratios of one Advanced Use user to 1 FUE, five Core Use users to 1 FUE, and thirty Self Service users to 1 FUE. Confirm the exact table in your order form.

Does Digital Access licensing apply to RISE and GROW?

Yes. Digital Access is quoted separately from FUE and applies under all four deployment models. Document creation through third party interfaces triggers the charge, so settle the document baseline before any conversion.

How long is SAP ECC supported before I must move?

SAP mainstream maintenance for ECC runs to the end of 2027, with extended maintenance available to 2030. SAP S/4HANA itself is committed to support through 2040, so the model decision drives the timing, not the platform.

Can I run S/4HANA on a hyperscaler with my own licenses?

Yes. Perpetual S/4HANA licenses can run on AWS, Azure, or Google Cloud infrastructure, keeping the license contract and the infrastructure contract separate. That separation preserves renewal leverage that RISE concentrates at signature.