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.

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 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.

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.

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

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.

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.