RISE with SAP: Private vs. Public Cloud – Which Fits Your Enterprise?

The Two Paths Within RISE with SAP

RISE with SAP is not a single product. It is a commercial wrapper around SAP's cloud ERP offering that can contain one of two fundamentally different deployment architectures: S/4HANA Cloud Private Edition (the rebranded successor to RISE with SAP Premium) or S/4HANA Cloud Public Edition (more commonly associated with SAP's GROW with SAP motion for mid-market). Understanding the distinction is essential before entering any commercial discussion with SAP.

Following SAP's mid-2025 packaging overhaul, the private cloud path is now formally called SAP Cloud ERP, Private Edition. The public cloud path — S/4HANA Cloud, Public Edition — remains distinct and is typically sold under the GROW with SAP banner rather than RISE, though the boundary has blurred as SAP's field sales seek to apply RISE branding broadly. Buyers must clarify in writing which edition applies to their contract before signing.

Private Cloud: Dedicated Infrastructure, Maximum Flexibility

The private cloud option provides a single-tenant, dedicated S/4HANA environment hosted on your chosen hyperscaler (AWS, Azure, or Google Cloud) or in an SAP-operated data centre. The defining commercial characteristic is that you retain the ability to run ABAP custom code, maintain proprietary industry-specific processes, and preserve integrations with non-SAP systems that would be incompatible with the public cloud's clean-core requirement.

Who Private Cloud Is For

Private cloud is the appropriate choice for organisations that have invested significantly in SAP customisation — industry-specific processes, complex financial structures, heavily modified supply chain logic — and for whom the clean-core public cloud requirement would necessitate a fundamental process transformation before migration. In the 2025 DSAG survey of DACH-region enterprises, 33 percent were using S/4HANA in a private cloud model, up from 11 percent the prior year, reflecting a significant shift towards the private path as organisations conclude that process standardisation is not feasible at their scale or complexity.

Industries with historically high SAP customisation — automotive, chemicals, utilities, and regulated financial services — are disproportionately represented in the private cloud population. For these organisations, the cost of decommissioning custom code and redesigning processes to meet public cloud standards exceeds any subscription cost savings from choosing the cheaper public edition.

Licensing in the Private Cloud Model

Private cloud pricing is based on the FUE (Full Use Equivalent) metric. The annual subscription cost incorporates the S/4HANA licences, infrastructure, and SAP Enterprise Support. The support cost is embedded in the subscription — customers do not pay a separate 22 percent annual maintenance fee as they would under on-premise perpetual licensing. This is one of the genuine structural advantages of RISE: the maintenance obligation is bundled and fixed as a proportion of the subscription, eliminating the annual maintenance escalation dynamic that characterises on-premise SAP support contracts.

However, the FUE baseline for private cloud is typically higher than for public cloud due to the customisation licensing requirements. Custom code that interfaces with S/4HANA processes may trigger DDLC (Digital Documents Licence Charge) obligations — the metric SAP uses to assess indirect access charges. The DDLC metric counts documents processed by the S/4HANA system via non-named-user interfaces. Private cloud environments with extensive third-party integrations must audit their DDLC exposure before finalising the contract baseline.

Public Cloud: Standardisation, Speed, and Lower Entry Cost

The public cloud — S/4HANA Cloud, Public Edition — operates on a multi-tenant basis, where all customers share the same SAP infrastructure and receive quarterly updates on SAP's universal release schedule. The commercial proposition is lower cost per user, faster implementation, and access to SAP's latest innovations embedded in the standard processes.

Who Public Cloud Is For

Public cloud is the appropriate choice for organisations whose SAP processes are, or can feasibly be moved to, SAP's standard process library. This typically means organisations with relatively low levels of existing customisation, businesses implementing SAP for the first time, subsidiaries or carve-outs that can be implemented on a greenfield basis, and mid-market organisations whose process complexity is within the scope of SAP's best-practice configurations.

The public cloud's clean-core constraint — no custom ABAP code modifications — is its most significant limitation for enterprises with legacy SAP estates. Any custom logic must be externalised to BTP (Business Technology Platform) as side-by-side extensions. This requires additional BTP consumption, which incurs incremental cost beyond the base subscription. Organisations that underestimate their extension requirements when moving to public cloud face cost overruns driven by BTP consumption top-ups.

Public Cloud Licensing Economics

Public cloud subscriptions are priced at a lower per-user rate than private cloud, reflecting the economies of multi-tenancy. The standard update cadence means SAP manages all upgrade activities, eliminating the customer-side testing and change management costs associated with major private cloud upgrades. Over a three-year horizon, the public cloud typically delivers 15 to 25 percent lower blended infrastructure and subscription cost compared to an equivalent private cloud deployment.

The caveat is implementation cost. Public cloud implementations require the organisation to conform its processes to SAP's standard model, which for organisations with established SAP estates means a transformation programme that often costs more than the subscription savings over the initial contract term. The TCO equation shifts in favour of public cloud only when the implementation premium is amortised across a multi-year horizon — typically five to seven years for organisations migrating from ECC.

Head-to-Head: Key Decision Factors

Customisation and Process Preservation

Private cloud permits ABAP custom code and process modifications. Public cloud requires a clean core — all custom logic must be externalised to BTP extensions. For organisations with significant custom code investment (typically more than 15,000 customer-developed ABAP objects in ECC), private cloud is the only viable migration path without a fundamental transformation programme running in parallel.

Update Control and Change Management

Private cloud customers control their upgrade schedule — major releases can be absorbed on a timeline aligned with business planning cycles. Public cloud customers receive quarterly updates from SAP automatically, which reduces upgrade management burden but can disrupt business processes if the quarterly cycle introduces breaking changes to integrated systems or custom extensions.

Data Sovereignty and Security

Private cloud deployments can be configured for specific data residency requirements — critical for organisations subject to GDPR, sector-specific data localisation regulations, or national security clearance requirements. Public cloud multi-tenancy, while logically isolated, may not satisfy the most stringent data sovereignty requirements without additional sovereign cloud options, which carry a licensing uplift relative to standard public cloud pricing.

DDLC and Indirect Access Exposure

Both deployment models are subject to the DDLC metric for indirect access. However, private cloud environments typically have more complex integration landscapes — more non-SAP systems communicating with the core SAP environment — which increases the DDLC document volume and the associated licence exposure. Before committing to either deployment model, organisations must conduct an independent DDLC audit that maps all system-to-system interfaces and estimates annual document volumes across each integration pathway.

Cost Comparison Over Five Years

A representative five-year TCO comparison for a 2,000 FUE enterprise: Private cloud subscription (including infrastructure) typically runs at €2.2 million to €3.0 million annually. Public cloud subscription runs at €1.6 million to €2.2 million annually. The subscription gap of approximately €600,000 per year appears to favour public cloud. However, the implementation differential — where public cloud transformations for legacy SAP organisations cost €3 million to €8 million more due to process redesign — means the five-year TCO is often comparable or slightly higher for public cloud in migration scenarios.

The SAP Fiscal Year Dynamics

Whether choosing private or public cloud, the timing of your RISE negotiation relative to SAP's fiscal year (which ends December 31) materially affects the commercial outcome. SAP's regional sales teams carry annual targets that reset each January. Deals signed in Q4 — particularly October through December — attract the highest discounts and migration credits as SAP pushes to close revenue before year-end. Organisations that can align their decision timeline with this window typically achieve 10 to 18 percent better pricing than those who sign in Q1 or Q2.

Five Questions to Answer Before Choosing

1. What is your custom code inventory? Run an SAP licence audit and quantify the number of custom ABAP objects. If the count exceeds 10,000 to 15,000, private cloud is almost certainly the more practical path unless you are willing to invest in a parallel transformation programme.

2. What are your data sovereignty requirements? Regulatory, security clearance, and data residency obligations may rule out multi-tenant public cloud regardless of cost considerations.

3. What is your DDLC exposure? Map all non-SAP system integrations and estimate annual document volumes to understand the DDLC baseline for either deployment model.

4. What is your five-year TCO? Model both options across a five to seven year horizon, including implementation costs, BTP extension costs, and the cost of change management for quarterly public cloud updates.

5. What is your migration timeline? If the SAP ECC maintenance deadline (end of 2027 for EHP 6–8) is creating pressure, private cloud typically offers a faster technical migration path for organisations with complex ECC estates. Public cloud requires the additional transformation investment that extends timelines.