The decision rule is fit-to-standard: if your processes can run SAP’s delivered scope with extensions kept outside the core, Public Edition’s multi-tenant SaaS buys you vendor-run operations and a simpler contract; if your landscape carries customizations, industry solutions or isolation requirements it cannot shed, Private Edition’s single-tenant model is the only cloud destination that will hold them. Everything else — release cadence, extensibility rules, migration path, contract shape — follows from that one architectural fork.
Published 9 April 2026 · Last reviewed 9 April 2026
S/4HANA Cloud Public Edition is SAP’s multi-tenant SaaS ERP: one shared platform that SAP operates, on which every customer runs the same code line with standardized business processes, configured — not modified — within the delivered scope. S/4HANA Cloud Private Edition is a single-tenant landscape dedicated to one customer: its own system, hosted on a hyperscaler nominated in the contract, running a code line the customer can extend more deeply and upgrade on a planned schedule. The names share a product family; the architectures share almost nothing operationally.
It helps to keep the product/program distinction clean, because the marketing names sit one layer up. Private Edition is sold through the bundled subscription known as RISE with SAP (newer paper says SAP Cloud ERP Private after the 2025 consolidation); Public Edition is reached through GROW with SAP. This guide compares the editions as operating models — tenancy, extensibility, cadence, migration — and leaves the commercial wrappers to the sibling guide on RISE vs GROW. Both editions are subscribed in FUEs, the blended user metric whose ratios and classification traps have their own guide.
This guide is general information about SAP’s S/4HANA Cloud editions as they stand in 2026, not licensing, technical or legal advice for your situation; SAP packaging and release practice change, and your contract governs. It names no firms; the firm directory lists SAP-capable advisors with balanced pros and cons, listed, not ranked.
Both editions speak the language of clean core — keeping the ERP’s digital heart unmodified and pushing custom logic to the edges — but they enforce it differently, and the difference is the practical heart of this comparison. In Public Edition, clean core is a rule: there is no mechanism to modify the core at all. Configuration happens inside SAP’s delivered processes; anything further is built as a side-by-side or on-stack extension on the Business Technology Platform (BTP) through released APIs, and survives upgrades precisely because it never touched the core. Legacy ABAP modifications do not come along; they are rebuilt or retired.
In Private Edition, clean core is a goal: the single-tenant landscape tolerates carried-over custom ABAP, modifications within agreed limits, and industry solutions that the shared platform cannot host. That tolerance is why brownfield conversions from ECC land here — and it carries a quiet cost, because every carried-over modification is a liability against future upgrades and a step away from the clean-core posture SAP increasingly assumes in its tooling and AI roadmap. The honest framing: Public Edition forces the discipline up front; Private Edition lets you defer it, with interest.
The migration paths follow directly. Public Edition is effectively a greenfield destination — processes are re-implemented to standard, data is migrated, custom code is left behind. Private Edition supports brownfield conversion, bringing configuration and custom code across from ECC or on-premise S/4HANA. Which path your estate can survive is usually settled by the state of your ABAP inventory before any commercial conversation begins — the ECC vs S/4HANA licensing guide covers the contractual side of that journey.
Public Edition runs on SAP’s calendar. Every tenant is upgraded on a mandated half-yearly cycle — the major releases have landed around February and August in recent years — with no opt-out and, in fairness, no upgrade project either: SAP does the work, and the customer’s job is regression-testing its BTP extensions and absorbing process changes. New capability, regulatory updates and AI features arrive automatically. The trade is control for currency: you are never behind, and you are never allowed to be.
Private Edition runs on a negotiated calendar. Upgrade timing is planned with SAP inside its maintenance policy — typically an annual or slower major-upgrade rhythm — and the customer owns the project: testing carried-over customizations, sequencing downtime, coordinating the managed-services provider. Infrastructure choice (which hyperscaler, which regions), sizing and the managed-services boundary are all contract terms rather than platform facts. For estates with regulatory isolation requirements or integration webs that need a fixed landscape, that control is the point; for everyone else it is overhead that the public edition has automated away.
Operationally, then: Public Edition behaves like SaaS — you administer a service; Private Edition behaves like managed hosting of your own ERP — you govern a landscape that someone else operates. Most disappointment with either edition traces to buying one while expecting the behaviour of the other.
| MECHANIC | PUBLIC EDITION | PRIVATE EDITION |
|---|---|---|
| Tenancy | Multi-tenant; one shared platform, one code line | Single-tenant; dedicated, customer-specific landscape |
| Commercial wrapper | GROW with SAP; standardized terms, published tiers | RISE / SAP Cloud ERP Private; bespoke negotiated bundle |
| Core modification | Impossible by design; configuration only | Tolerated within limits; classic ABAP can carry over |
| Extensions | Clean-core only, via BTP and released APIs | BTP encouraged; in-stack custom code also possible |
| Upgrade cadence | Mandated half-yearly releases (recently February / August) | Customer-planned within SAP’s maintenance windows |
| Migration path | Greenfield; fit-to-standard re-implementation | Brownfield conversion or selective re-build |
| Infrastructure | Invisible; SAP operates the shared platform | Hyperscaler, regions and sizing are contract terms |
| Metric | FUE pool; a FUE buys a seat on shared SaaS | FUE pool; a FUE buys access plus infrastructure plus services |
Read the table bottom-up if procurement is your seat: the shared FUE metric is the trap row. Two quotes can carry identical FUE counts and describe profoundly different purchases, because the private-edition FUE has infrastructure and managed services priced into it. Compare scope per FUE and total annual cost of the operating model — never the unit counts.
Public Edition suits organisations that can adopt standard processes as a feature rather than fight them as a constraint: mid-market firms without decades of ABAP, new subsidiaries and carve-outs, two-tier deployments where headquarters runs something heavier, and ERP-first programs that want the vendor to own operations. The test is process humility plus extension discipline — if every department insists its workflow is special, the half-yearly releases will feel like weather rather than a feature.
Private Edition suits the large installed base it was built to move: ECC and on-premise S/4HANA estates with customizations, industry solutions and integration webs that the shared platform cannot hold, and organisations whose regulators or risk functions require landscape isolation and named infrastructure. For many of those buyers the genuine alternative is not Public Edition at all but staying on-premise — a separate decision with its own guide, RISE vs on-premise S/4HANA.
Two-tier estates use both: private at the core, public in the subsidiaries. Legitimate architecture, two contracts — two cadences, two renewal calendars, and a vendor that models the whole group’s trajectory even when the group does not. Walk in with the group picture or inherit the vendor’s version of it.
The edition choice writes the negotiation agenda. Choosing Private Edition means constructing a bespoke bundle — FUE ramp, infrastructure sizing, managed-services boundary, renewal caps, exit and data-egress assistance, add-on scope after the 2025 repackaging — where every default favours the drafter and signature-time is the only time protections can be priced in. Choosing Public Edition means buying standardized paper where leverage concentrates on ramp schedules, multi-year price protection and the add-on catalogue, and where what the standard terms say about suspension, data return and renewal notice deserves a closer read precisely because little of it will be redrafted. In both cases the user-classification exercise that sets the FUE count is the largest single commercial variable, and it is settled before discounting begins.
The recurring traps: comparing FUE counts across editions as if they priced the same scope; letting the sizing exercise classify users on defaults instead of usage data; choosing Public Edition on price and discovering the constraints — fit-to-standard is a governance commitment, and fighting it shows up later as BTP extension sprawl; carrying every ABAP modification into Private Edition because conversion tolerated it, deferring a clean-up that compounds; and treating the editions as interchangeable later — there is no in-place switch, and private-to-public means rebuilding extensions clean-core. Modelling these consequences before the vendor’s framing arrives is the work, and choosing who does that modelling is its own decision; the negotiation itself is the territory of SAP license negotiation firms, with licensing advisory covering the sizing and classification groundwork.
The commercial programs above the editions →
The prior fork: subscription or perpetual →
The metric both editions are sold in →
How to pick the firm for this work →
Firms that negotiate these contracts →
Every field guide on the site →
Public Edition is a multi-tenant SaaS ERP: SAP operates one shared platform, all customers run the same code line on standardized processes, and upgrades arrive for everyone on a fixed half-yearly rhythm. Private Edition is a single-tenant landscape dedicated to one customer, hosted on a hyperscaler chosen in the contract, where classic ABAP customization can be carried over and upgrade timing is planned with the customer within SAP’s maintenance windows. The first is a product you adopt; the second is a landscape you migrate.
Private Edition is the product; RISE with SAP — sold on newer paper as SAP Cloud ERP Private since the 2025 rebrand — is the commercial bundle it is sold through, wrapping infrastructure, the HANA database and a managed-services layer into one negotiated subscription. Likewise Public Edition is reached commercially through GROW with SAP. This guide compares the editions as operating models; the commercial programs are compared separately.
Within strict boundaries. Public Edition permits no modifications to the core: configuration happens within SAP’s delivered scope, and anything beyond it must be built as a clean-core extension on the Business Technology Platform (BTP) through released APIs. Classic ABAP modifications and legacy custom code do not carry over. Private Edition is the edition that tolerates carried-over ABAP and deeper landscape-specific customization, within agreed limits.
Public Edition tenants are upgraded by SAP on a mandated half-yearly cycle — in recent years the major releases land around February and August — with no customer opt-out, and no customer effort beyond regression-testing extensions. Private Edition customers plan upgrades with SAP inside its maintenance policy, typically running major upgrades annually or less often, which buys control at the cost of owning the upgrade project.
Yes — both are subscribed in Full User Equivalents, the blended unit that converts advanced, core, self-service and developer users into one pool at fixed ratios. But a FUE does not buy the same scope in each edition: the private-edition subscription bundles dedicated infrastructure and managed services, while the public-edition subscription prices a seat on a shared SaaS platform. Identical FUE counts on two quotes are not comparable offers.
There is no in-place conversion in either direction; a move between editions is a re-implementation. Public to private is commercially easy but technically a new project. Private to public is harder, because carried-over customizations and ABAP extensions must be rebuilt clean-core before the shared platform will accommodate them. Choose the edition on a ten-year reading of your landscape, not on this year’s procurement convenience.
Deciding between a shared SaaS platform and a dedicated managed landscape — and pricing what each FUE actually buys — is exactly what an SAP licensing advisor is for. The directory lists the firms that do this work, with balanced pros and cons, listed, not ranked.
Tell us the vendor, the service you need and where things stand, and we will route your brief to firms that genuinely cover that combination. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.