SAP Cloud Licensing Models | Redress Compliance

SAP sells under five cloud models. RISE, GROW, public cloud edition, private cloud edition, and the BTP plus SaaS line. The metric, audit posture, and renewal lever differ by model. The buyer side response maps the estate to the right model, prices the trade offs, and locks the FUE math before signing.

Pair this article with the RISE vs on premise comparison, the S/4HANA migration paths reference, and the digital access article before opening the next SAP cloud call.

Key Takeaways

What a CIO needs to know in 90 seconds

Five cloud models. RISE, GROW, public, private, BTP and SaaS.
FUE is the unifying metric. Full User Equivalent math drives RISE and GROW pricing.
Digital access still applies. Document counts move in the cloud as well.
RISE bundles services. Hyperscaler, basis, and support are inside.
GROW is fixed scope. Mid market public cloud with limited customization.
Private edition keeps the customization. At a higher per FUE price.
BTP carries its own metric. Capacity Units and consumption.

Why five models exist

SAP collapsed its catalog into a small set of named cloud models around 2023 and 2024. The intent was to simplify the buy. The result for enterprise customers is a model choice that drives every later commercial conversation.

The three buying axes

Customization appetite. Highly customized estates favor private edition.
Operating model. RISE shifts operations to SAP, private keeps them with the customer.
Scale and scope. GROW fits mid market, RISE and private fit large enterprise.

RISE with SAP

RISE is the bundled subscription that wraps S/4HANA Cloud private edition, hyperscaler infrastructure, basis operations, and SAP support into one line. The metric is FUE.

RISE composition

Layer	What is included	Buyer side note
Application	S/4HANA Cloud private edition	Same code as on premise S/4HANA
Hyperscaler	AWS, Azure, GCP, or SAP	Choice belongs to the customer
Basis	SAP managed	OS, DB, basis operations
Support	SAP standard plus optional premium	Match to existing support tier
Tooling	BTP credits, SAP Build, Signavio process	Often part of the bundle, value varies

RISE leverage points

FUE conversion ratio. Negotiate the conversion from named users to FUE.
Hyperscaler choice. Keep optionality across AWS, Azure, GCP.
BTP credits. Documented value, not a generic credit dump.
Escalator cap. Three to five percent fixed.

GROW with SAP

GROW is the fixed scope public cloud edition for mid market. The scope is narrower and the customization headroom is constrained. The price per FUE is lower than RISE.

The GROW fit test

GROW fits companies that accept the standard process model with limited customization. The fit test asks three questions. Does the standard scope cover the operating model. Will the company adapt to the standard. Are the integrations supported in the public edition. Three yes answers point to GROW. Anything less points back to RISE or private edition.

Public cloud editions

Public cloud editions sit alongside GROW for specific lines of business. SuccessFactors, Ariba, Concur, Customer Experience, and Field Service all run as named SaaS subscriptions with their own metrics.

SaaS metric examples

SaaS line	Primary metric	Buyer side note
SuccessFactors	Per employee per module	Bundle the modules, lock the headcount
Ariba	Spend under management or document volume	Document the spend baseline
Concur	Per active user	Watch the active user definition
Customer Experience	Per named user per module	Map sales, service, and commerce separately
Field Service	Per technician per month	Often consolidated into FSM bundle

Private cloud edition

Private cloud edition keeps the customization headroom of on premise S/4HANA inside a managed environment. It is the route for highly customized estates that need cloud economics without giving up the code.

Private edition leverage points

Customization headroom. Negotiate the extension framework explicitly.
Operating model. Customer led, partner led, or SAP managed.
Add on certification. Document which add ons remain in scope.
Renewal anchor. Five year picture across application and infrastructure.

BTP and SaaS lines

SAP Business Technology Platform sits underneath the application portfolio. It carries its own commercial metric, Capacity Units, plus consumption based services.

BTP is the underpriced line in the first SAP cloud quote and the overpriced line at year three. Lock the capacity unit conversion and the consumption rates before signing the bundle.

BTP commercial levers

Capacity Unit conversion. Lock the dollar per CU rate.
Consumption ceiling. Cap the year over year consumption growth.
Bundle vs standalone. Compare bundled BTP credits against standalone BTP pricing.
Build and Signavio. Both ride on BTP with separate scope.

What to do next

The seven step checklist below moves an SAP cloud decision from model confusion to a defended commercial picture.

Map the application portfolio. S/4HANA, line of business SaaS, BTP.
Pick the lead model. RISE, GROW, public, private, or hybrid.
Run the FUE conversion. Named users to FUE with documented rules.
Price each SaaS line. Per metric, per module, per term.
Lock the BTP rate. CU conversion and consumption ceiling.
Build the anchor. Five year picture across model and SaaS.
Close on terms. Escalator cap, hyperscaler choice, audit waiver.

Frequently asked questions

What is an FUE and how is it calculated?

FUE stands for Full User Equivalent. SAP uses FUE as a unifying metric for RISE and GROW. Each named user role converts into a fractional FUE per a documented table. Five Developer users might equal one FUE, ten Self Service users might equal one FUE. The conversion ratios are the negotiating lever and they vary by contract and by year.

Does digital access apply in RISE?

Yes. Digital access counts the indirect document creation by third party systems against the S/4HANA core. The metric applies regardless of deployment model. RISE customers face the same document count exposure as on premise S/4HANA customers. The Digital Access Adoption Program is one path to bring the documents into a managed line.

Can we choose our hyperscaler under RISE?

Yes. RISE supports AWS, Azure, Google Cloud, and SAP Hyperscaler. The choice belongs to the customer. The chosen hyperscaler should match the existing cloud strategy and any existing committed spend agreements. Switching hyperscalers under RISE later is possible but disruptive, so the initial choice carries weight.

Is GROW limited to mid market?

GROW is positioned as the mid market public cloud edition. The boundary is more about scope than headcount. Companies that can run the standard process model fit GROW. Companies that need significant customization, complex integrations, or non standard add ons fit RISE private edition. Some larger companies adopt GROW for a single subsidiary or a green field business unit.

How do BTP capacity units work?

BTP Capacity Units are a credit pool that funds different BTP services at different rates. One service might consume one CU per hour, another might consume five. The CU conversion table is the lever. Capacity Units that sit unused at year end typically expire, so the buyer side ceiling matters as much as the floor.

What is the typical RISE escalator?

Three to five percent fixed is the defensible range on enterprise RISE deals. Open ended escalators are negotiable on every deal above three million dollars annual spend. The escalator should be in the contract not a side letter. The escalator interacts with the FUE conversion ratio, so both need to be locked together at signing.

How Redress engages on SAP cloud decisions

Redress runs SAP cloud as a model decision engagement. The work covers the application portfolio map, the FUE math, the BTP rate, and the multi model anchor table. Engagements close in twelve to sixteen weeks across a full SAP estate.

Vendor Advisory

Cloud & Emerging

Programs

Assessments

Research

Knowledge Hubs

Assessment Tools

SAP cloud. Decoded.