S/4HANA Public Cloud lists between $80 and $130 per Full Use Equivalent per month. Private Cloud via RISE lands $190 to $360 per FUE. On premise S/4HANA carries a one off license fee of roughly $4,200 per FUE plus 22 percent annual maintenance. For a 5,000 user estate the 10 year cost gap between the cheapest and most expensive path exceeds $42M. Edition selection is the single largest commercial decision in any S/4HANA programme, and it is irreversible without a full data migration. This page sets the 2026 reference: list and negotiated pricing, functional limits per edition, deployment fit by industry, and the conversion mathematics if the first choice turns out wrong.
The three S/4HANA editions in one paragraph
Public Cloud is multi tenant S/4HANA running on SAP managed hyperscaler infrastructure. Quarterly innovation cycles. Opinionated configuration. Limited custom code, no ABAP modification of standard objects, side by side extensions only via SAP Business Technology Platform. Private Cloud Edition is single tenant S/4HANA running on a customer dedicated hyperscaler footprint, sold inside the RISE with SAP bundle. Two yearly release cycle. Full ABAP extensibility. Industry add ons supported. On premise S/4HANA is the traditional perpetual license model. Customer owned infrastructure or a customer chosen hyperscaler. Five yearly release cadence with the option to remain on a fixed release for the full Mainstream Maintenance window. Full extensibility, full control, full responsibility.
2026 reference pricing per edition
Pricing for all three editions is anchored on the Full Use Equivalent (FUE), a weighted count that aggregates Advanced Use users (1.0), Core Use users (0.2), and Self Service users (0.033). A 5,000 named user estate with a typical 20 percent Advanced mix counts to roughly 1,700 FUEs.
| Edition | List per FUE | Negotiated band | Commercial vehicle |
|---|---|---|---|
| Public Cloud (subscription) | $130 / FUE / month | $80 to $115 | Direct subscription or GROW with SAP |
| Private Cloud Edition (via RISE) | $360 / FUE / month | $190 to $290 | RISE Base, Premium, or Premium Plus |
| On premise (perpetual + maintenance) | $4,200 / FUE one off + 22% | $2,400 to $3,400 + 18 to 22% | Direct license plus Standard or Enterprise Support |
| Private Cloud (Customer Data Center, HEC legacy) | $310 / FUE / month | $175 to $260 | RISE Customer Data Center option, capped to 31 Dec 2028 |
The list figures above come from SAP price book entries circulating in early 2026 commercial proposals. Negotiated bands assume a three year initial term, an existing SAP maintenance base of meaningful scale, and an advisor led commercial process. Smaller estates without an existing relationship pay closer to list. Estates above 5,000 FUEs with competitive pressure achieve the low end of each band.
10 year total cost for a 5,000 user estate
Per FUE pricing hides the cost gap. The comparison that matters is 10 year all in TCO including license, infrastructure, hyperscaler consumption, support, and one off conversion or migration. The table below models a 5,000 named user estate (roughly 1,700 FUEs) with mid market negotiated rates.
| Cost component (10 year, 1,700 FUE) | Public Cloud | Private Cloud (RISE) | On premise |
|---|---|---|---|
| License or subscription | $20.4M | $48.8M | $5.6M + maintenance |
| SAP support / maintenance | Included | Included | $12.3M |
| Hyperscaler infrastructure | Included | Included | $8.2M |
| Implementation or conversion | $6.5M | $11.2M | $13.8M |
| Quarterly upgrade or release effort | $0.4M | $3.6M | $5.4M |
| 10 year TCO | $27.3M | $63.6M | $45.3M |
The headline gap of $36M between Public Cloud and Private Cloud is real, but only available to estates that fit Public Cloud's functional envelope. Most enterprise estates do not.
Functional fit by edition
The functional gap between Public Cloud and the other two editions is the deciding factor in most edition selections. Public Cloud ships a fixed scope, governed by the Service Center Catalog. Industry specific add ons available on Private Cloud and on premise are not all available on Public Cloud.
| Capability | Public Cloud | Private Cloud | On premise |
|---|---|---|---|
| Standard Finance, Sales, Purchasing | Yes | Yes | Yes |
| Industry add ons (Retail, Utilities, Insurance, Defence, Public Sector) | Partial | Yes, full catalog | Yes, full catalog |
| Customer specific ABAP modifications | No (side by side only via BTP) | Yes (governed by Clean Core principles) | Yes (no governance) |
| Third party add on installation | No | Yes | Yes |
| Release cadence | Quarterly (mandatory) | Two yearly (mandatory within RISE) | Five yearly (customer scheduled) |
| Configuration scope | Limited to SSCUI catalog | Full SPRO + extensibility | Full SPRO + extensibility |
Functional fit test: if more than 15 percent of current ECC custom development is core process modification rather than reporting, integration, or UX, Public Cloud is the wrong answer regardless of price. The Clean Core remediation cost erases the subscription saving inside three years.
Decision matrix by industry and customisation appetite
The selection is not a price decision. It is a functional and operating model decision priced afterwards. The matrix below reflects fit observed across 40 plus advisor led S/4HANA edition selections during 2024 to 2026.
| Customer profile | Best fit edition | Rationale |
|---|---|---|
| Mid market, vanilla Finance, no industry add ons, under 1,000 users | Public Cloud (often via GROW) | Lowest TCO, fastest implementation, opinionated configuration matches process appetite |
| Enterprise, regulated industry, heavy industry add ons, full ECC custom base | Private Cloud (RISE) | Industry add ons supported, ABAP extensibility preserved, SAP managed operations |
| Enterprise, manufacturing or utilities, on premise data residency, sovereign requirements | On premise | Data residency, control over release cadence, no hyperscaler dependency |
| Enterprise, financial services, heavy custom code, planning Clean Core over five years | Private Cloud (RISE) with explicit Clean Core programme | Bridges current custom estate to a smaller, supported S/4HANA footprint |
| Carve out of a Fortune 1000 division, 200 to 2,000 users, three year IPO horizon | Public Cloud or GROW | Speed to value, lower fixed cost, exit clarity for IPO |
| Public sector, defence, classified workload | On premise (often sovereign hyperscaler) | Classification requirements eliminate multi tenant options |
The cost of switching editions later
Edition selection is presented as a commercial decision. It is also an architectural commitment. Switching editions later carries a data migration cost equal to a fresh S/4HANA implementation, plus a license commercial restructuring with SAP. The current advisor observed cost for an enterprise estate to switch editions:
- Public Cloud to Private Cloud: $8M to $14M one off, plus 18 to 30 month migration. Driven by data extraction and re implementation cost.
- Private Cloud to Public Cloud: $12M to $22M one off, plus 24 to 36 month migration. The harder direction because custom code and industry add ons must be removed or replaced.
- On premise to Private Cloud (RISE): $4M to $9M one off, plus a SAP commercial true up that values existing licenses at conversion credit rates that often discount by 30 to 50 percent.
- Public Cloud to on premise: not observed. SAP does not publish a conversion path for this direction.
The exit cost asymmetry has commercial consequences. Public Cloud customers who pick the wrong edition discover the gap inside 24 months and bear a multi year cost to escape. Private Cloud customers who pick the wrong edition usually retreat to on premise, where existing license rights provide commercial protection.
Private Cloud via RISE versus Private Cloud direct
Private Cloud Edition is no longer sold standalone. The only commercial path to Private Cloud since 2022 is the RISE with SAP bundle, which includes infrastructure, SAP managed services, BTP credits, and standard tools. The bundling is not negotiable, but the bundle composition is. RISE pricing tiers in 2026:
| RISE tier | 2026 price band per FUE | Inclusions |
|---|---|---|
| RISE Base | $190 to $235 | S/4HANA Private Cloud, infrastructure, basic AMS, 2,200 BTP CPEA credits per FUE |
| RISE Premium | $235 to $290 | Base plus enhanced AMS, Signavio Foundation, Analytics Cloud entitlements |
| RISE Premium Plus | $290 to $360 | Premium plus Datasphere, Signavio full suite, Joule access, accelerated AI features |
For most enterprise estates RISE Premium is the right starting point. Premium Plus pays back only when the included Datasphere and Signavio entitlements would have been bought standalone. See RISE Premium Plus pricing for the payback test. For the full RISE vs alternative bundle comparison see RISE vs GROW vs HEC.
Contract mechanics differ by edition
The three editions are sold under different contractual instruments, and the differences matter at renewal. Public Cloud is sold under a SAP Cloud Service Agreement with a Service Description per workload, typically on a three year term with one year auto renew thereafter unless terminated with 90 days notice. Private Cloud (RISE) is sold under a single RISE Master Subscription Agreement that includes the S/4HANA subscription, infrastructure, BTP credits, and SAP managed services as a bundled deliverable, typically on three or five year initial terms. On premise is sold under a perpetual license agreement with separate Standard Support or Enterprise Support attached and renewing annually at the customer's option.
The renewal economics are different across the three. Public Cloud renewals are exposed to SAP's standard 3 to 5 percent annual increase on the published list rate per FUE, with negotiating room limited to the term extension. RISE renewals carry the same risk plus the renegotiation of every bundled component, which doubles the surface area for SAP to push price. On premise renewals are bounded by the Maintenance fee structure, which has its own annual increase exposure documented in SAP 2026 price increase. The Maintenance fee structure is the most predictable of the three and the most negotiable through Third Party Maintenance alternatives.
Hidden costs that change the comparison
Headline per FUE pricing is the visible cost. The hidden costs that show up later determine the actual TCO winner.
| Hidden cost | Public Cloud | Private Cloud (RISE) | On premise |
|---|---|---|---|
| Mandatory upgrade testing effort | Quarterly, low effort, included scope | Two yearly, high effort, customer cost | Five yearly, very high effort, customer cost |
| Side by side BTP consumption | Higher (only extension model) | Lower (in app extensibility available) | Lowest (full in app extensibility) |
| Sandbox or non production environments | Included up to a limit, overage charged | Included per RISE tier, overage charged | Customer provisioned, customer cost |
| Integration middleware | SAP Integration Suite extra unless bundled | Often included in Premium and above | Customer chosen, customer cost |
| Disaster recovery | Included with limits | Included with stated RPO and RTO | Customer designed, customer cost |
| Indirect or Digital Access exposure | Same calculation as on premise | Same calculation as on premise | Same calculation, often higher visibility |
The most common hidden cost overrun is the integration middleware. SAP Integration Suite at full standalone pricing adds $0.6M to $1.4M per year for a mid market estate. Some RISE Premium configurations include it, some do not. The bundle composition needs to be read clause by clause, not summarised at the headline tier level.
Does on premise still make sense in 2026
SAP has been clear that S/4HANA Public Cloud and Private Cloud are the strategic direction. On premise S/4HANA continues to be sold under perpetual license and remains the lowest 10 year TCO for estates with stable user counts, existing infrastructure investment, and strong internal Basis capability. The on premise case is strongest when three conditions hold: the customer already operates the underlying hyperscaler or data center capacity at marginal cost, the customer values control over release cadence, and the customer has a five year horizon where SAP led innovation in cloud editions does not deliver business value over a self managed estate.
The on premise case is weakest when SAP innovation matters (embedded AI through Joule, Datasphere integrations, Signavio process intelligence), when the customer lacks internal Basis depth, or when the existing ECC estate is heavily customised and ready for a Clean Core programme. The decision is bounded by the ECC 2027 end of life deadline, which forces every on premise customer to choose a path before 31 December 2027.
The decision framework
The selection process used by advisors on enterprise S/4HANA programmes:
- Inventory current custom development. Categorise into core process modification, reporting, integration, UX, and side by side. If core process modification exceeds 15 percent of total, Public Cloud is eliminated.
- Inventory industry add ons in use. If any add ons not on the Public Cloud roadmap are in active use, Public Cloud is eliminated.
- Model 10 year TCO for remaining options. Include license, infrastructure, support, conversion, and ongoing release effort. Use negotiated rates not list.
- Assess operating model fit. Public Cloud requires quarterly mandatory upgrade discipline. Private Cloud requires SAP managed operations. On premise requires internal Basis depth.
- Test commercial exit terms. Public Cloud and Private Cloud subscription terms include termination provisions. On premise license rights persist indefinitely.
- Run a commercial benchmark. The realised pricing in the negotiated band depends on competitive pressure. Modelling a credible alternative shifts SAP by 12 to 25 percent.
Edition selection trap: SAP commercial teams steer toward Private Cloud (RISE) as the default for enterprise accounts because RISE carries the highest revenue per FUE. The right answer is determined by functional fit and operating model, not by SAP's commercial preference. Test fit independently before accepting the RISE anchor.
Where to start
Edition selection is the most consequential decision in any S/4HANA programme. The right starting point is a 20 page functional fit assessment that maps current custom development, industry add on usage, and operating model preferences against the three editions. Pricing comes second. SAP's commercial proposal comes third. The combination produces a defensible edition recommendation that survives commercial pressure.
For the full S/4HANA commercial framework see SAP Licensing Complete Guide, S/4HANA Negotiation, and the SAP vendor intelligence hub. For active SAP commercial work see Software Licensing Advisory. For deadline planning across ECC retirement and S/4HANA conversion see SAP ECC 2027 End of Life Strategy and S/4HANA Conversion Credits.