S/4HANA Public Cloud vs Private Cloud vs on premise.
Edition selection is the single largest commercial decision in any S/4HANA programme — and it is irreversible without a full data migration. Public Cloud lists $80–$130 per FUE per month; Private Cloud via RISE runs $190–$360; on premise carries a perpetual fee plus 22% maintenance. For a 5,000-user estate the 10-year cost gap across paths exceeds $36M. This note sets the 2026 reference on pricing, functional limits, fit, and switching cost.
There is no single "best" S/4HANA edition. Public Cloud wins on TCO and speed for vanilla, low-customisation estates; Private Cloud (RISE) fits regulated, industry-add-on and heavy-custom estates that want SAP-managed operations; on premise remains the lowest 10-year cost for stable, sovereign estates with strong internal Basis capability. Fit is functional first and priced afterwards — test it before accepting SAP's RISE anchor.
01 Key findings
Three operating models, not three price points of one product. Public Cloud is multi-tenant and opinionated; Private Cloud is single-tenant inside the RISE bundle; on premise is the perpetual, customer-controlled model. The decision is about control and cadence, not just cost.
The headline cost gap is real but conditional. Public Cloud models to ~$27.3M over 10 years versus ~$63.6M for Private Cloud on a 1,700-FUE estate — a $36M gap only available to estates that fit Public Cloud's fixed functional envelope. Most enterprise estates do not.
Customisation appetite decides eligibility. If more than 15% of current ECC custom development is core process modification, Public Cloud is eliminated regardless of price — Clean Core remediation erases the subscription saving inside three years.
Private Cloud only ships via RISE. Since 2022 the sole path to Private Cloud is the RISE Master Subscription Agreement. The bundle is not optional; its composition — AMS tier, BTP credits, Integration Suite — is where the negotiation lives.
Switching editions later costs a full re-implementation. Public-to-Private runs $8M–$14M and 18–30 months; Private-to-Public is harder at $12M–$22M. On premise license rights persist indefinitely, giving on-prem estates the strongest exit protection.
02 Deployment scorecard
Relative commercial and operating strength across the dimensions that decide an S/4HANA edition. Five dots = strongest on that dimension; scoring reflects deployment posture, not absolute product capability.
03 Reference pricing
Pricing across all three editions is anchored on the Full Use Equivalent (FUE), a weighted count aggregating Advanced Use (1.0), Core Use (0.2) and Self-Service (0.033) users. A 5,000 named-user estate with a typical 20% Advanced mix counts to roughly 1,700 FUEs. List figures are from SAP price-book entries in early-2026 proposals; negotiated bands assume a three-year term, a meaningful existing maintenance base and an advisor-led process.
| 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 (via RISE) | $360 / FUE / month | $190 to $290 | RISE Base, Premium, or Premium Plus |
| On premise (perpetual + maint.) | $4,200 / FUE + 22% | $2,400 to $3,400 + 18–22% | Direct license plus Standard/Enterprise Support |
| Private Cloud (Customer Data Center) | $310 / FUE / month | $175 to $260 | RISE CDC option, capped to 31 Dec 2028 |
04 Edition profiles
- Lowest 10-year TCO (~$27.3M model)
- Fastest implementation, opinionated config
- Quarterly innovation, embedded AI first
- No ABAP modification; BTP side-by-side only
- Fixed SSCUI scope, partial industry catalog
- Mandatory quarterly upgrade discipline
- Full industry add-on catalog supported
- ABAP extensibility under Clean Core
- SAP-managed infra, BTP credits bundled
- Highest subscription cost per FUE
- RISE bundle lock-in; whole-bundle renewal risk
- Two-yearly upgrade effort borne by customer
- Lowest long-run TCO for stable estates
- Full control of release cadence to 2040
- License rights persist; TPM leverage
- Full infra and support responsibility
- Lags SAP cloud-led AI innovation
- High five-yearly upgrade effort
Two traps sit either side of the middle option. Public Cloud caps customisation at BTP side-by-side extensions — any core process modification above ~15% of the ECC custom base eliminates it. Private Cloud removes that limit but only inside the RISE bundle: a single Master Subscription Agreement means every renewal reopens infrastructure, AMS, BTP credits and managed services at once, doubling the surface area for SAP to push price. Read the bundle clause by clause, not at the headline tier.
05 10-year TCO for a 5,000-user estate
Per-FUE pricing hides the real gap. The comparison that matters is 10-year all-in TCO — license, infrastructure, hyperscaler consumption, support and one-off conversion or migration. The model below assumes a 5,000 named-user estate (~1,700 FUEs) at mid-market negotiated rates.
| Cost component (10-yr, 1,700 FUE) | Public Cloud | Private (RISE) | On premise |
|---|---|---|---|
| License or subscription | $20.4M | $48.8M | $5.6M |
| SAP support / maintenance | Included | Included | $12.3M |
| Hyperscaler infrastructure | Included | Included | $8.2M |
| Implementation or conversion | $6.5M | $11.2M | $13.8M |
| Upgrade / release effort | $0.4M | $3.6M | $5.4M |
| 10-year TCO | $27.3M | $63.6M | $45.3M |
Integration middleware is the most common overrun. SAP Integration Suite at full standalone pricing adds $0.6M–$1.4M per year for a mid-market estate. Some RISE Premium configurations include it, some do not — and on premise carries it as a customer-chosen cost. Model it net, per bundle, before comparing headline per-FUE rates.
06 Functional fit by edition
The functional gap between Public Cloud and the other two editions is the deciding factor in most 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) | Partial | Yes, full catalog | Yes, full catalog |
| Customer ABAP modifications | No (BTP side-by-side only) | Yes (Clean Core governed) | Yes (no governance) |
| Third-party add-on installation | No | Yes | Yes |
| Release cadence | Quarterly (mandatory) | Two-yearly (within RISE) | Five-yearly (customer scheduled) |
| Configuration scope | Limited to SSCUI catalog | Full SPRO + extensibility | Full SPRO + extensibility |
07 The cost of switching editions later
Edition selection is presented as a commercial decision. It is also an architectural commitment. Switching later carries a data-migration cost equal to a fresh S/4HANA implementation plus a license restructuring with SAP. Current advisor-observed costs for an enterprise estate:
| Switch direction | One-off cost | Timeline | Driver |
|---|---|---|---|
| Public Cloud → Private Cloud | $8M to $14M | 18–30 months | Data extraction and re-implementation |
| Private Cloud → Public Cloud | $12M to $22M | 24–36 months | Custom code and add-ons must be removed |
| On premise → Private Cloud (RISE) | $4M to $9M | Commercial true-up | Existing licenses valued at 30–50% credit |
| Public Cloud → on premise | Not observed | — | No published SAP conversion path |
The asymmetry has commercial consequences. Public Cloud customers who pick wrong discover the gap inside 24 months and bear a multi-year cost to escape. Private Cloud customers who pick wrong usually retreat to on premise, where existing license rights provide commercial protection.
08 Our recommendation
Core process modification is under 15% of the ECC custom base, no unsupported industry add-ons are live, and speed plus lowest TCO matter more than control. Ideal for mid-market and IPO-horizon carve-outs — often via GROW with SAP.
You run industry add-ons, a full ECC custom estate, or a regulated workload and want SAP-managed operations. Anchor on RISE Premium, then negotiate the bundle clause by clause and force explicit Clean Core scope.
Data residency, classified workloads or existing infrastructure at marginal cost, plus strong internal Basis depth and a stable user count. Lowest long-run TCO — but you own release effort, and must choose a path before the 2027 ECC deadline.
09 The decision framework
The selection process advisors run on enterprise S/4HANA programmes. Fit is established first; SAP's commercial proposal comes last.
Inventory custom development
Categorise into core process modification, reporting, integration, UX and side-by-side. If core modification exceeds 15% of total, Public Cloud is eliminated.
Inventory industry add-ons
If any add-ons not on the Public Cloud roadmap are in active use, Public Cloud is eliminated regardless of price.
Model 10-year TCO
Include license, infrastructure, support, conversion and ongoing release effort for remaining options. Use negotiated rates, not list.
Test fit and exit terms
Assess operating-model fit and termination provisions, then run a commercial benchmark — a credible alternative shifts SAP by 12–25%.
Choose the edition that fits the business
We model Public, Private and on premise against your actual functional footprint and 10-year TCO before SAP sets the anchor.
The Licensing Edge
Weekly SAP and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.