SAP S/4HANA Private Cloud Edition (PCE) sits at the heart of most RISE with SAP contracts. It's the managed S/4HANA instance that SAP hosts, operates, and maintains on hyperscaler infrastructure — and it's where RISE pricing gets complicated. SAP markets RISE as a simplified, all-in subscription. The reality is a multi-layered commercial structure where the S/4HANA PCE licence, infrastructure, support, BTP entitlements, and enhancement packages are priced, contracted, and measured separately — even when they appear on a single order form.
What Is SAP S/4HANA Private Cloud Edition?
Private Cloud Edition (PCE) is the managed, single-tenant deployment of S/4HANA within RISE with SAP. Unlike S/4HANA Public Cloud (GROW with SAP), PCE preserves customer-specific customisations and runs on dedicated infrastructure managed by SAP. SAP operates the environment on Microsoft Azure, Google Cloud, or AWS — but the customer selects the hyperscaler and region at contract time.
The term "private" is important: each customer gets their own isolated tenant, as opposed to the multi-tenant public cloud model. This makes PCE the natural migration path for existing SAP ECC customers with complex landscapes, industry-specific add-ons (IS-Retail, IS-Mill, IS-Utilities), or regulatory requirements that prevent multi-tenant hosting.
PCE includes:
- Managed S/4HANA system landscape (production + pre-production systems)
- SAP Basis operations managed by SAP
- Quarterly system updates on a managed release cycle
- Hyperscaler infrastructure (compute, storage, networking)
- SAP Enterprise Support (embedded in the RISE fee)
PCE does not include:
- Application customisation or development
- Data migration or cutover
- Interface development and testing
- Business transformation consulting
- Third-party integrations above BTP bundle threshold
How PCE Is Licensed and Priced
S/4HANA PCE pricing under RISE is based on a PSPD metric — Professional, Starter, Professional Digital, and other named user categories — combined with functional scope. The headline "per-user per-month" framing from SAP's marketing materials is a simplification. Actual pricing depends on:
1. Named User Types
Professional users (full access) cost 3–5x more than Starter or Employee users. The user count at contract signing becomes the baseline for annual true-up calculations.
2. Functional Scope Packages
Core ERP modules are included; industry-specific add-ons (SAP for Retail, SAP for Utilities, S/4HANA Finance advanced capabilities) are licensed as enhancements that add to the base price.
3. Infrastructure Size
RISE PCE contracts include defined compute resource allocations (CPU, RAM, storage). Enterprises that underestimate their infrastructure requirements at contract time face significant uplift when requesting additional capacity.
4. Contract Term
Standard RISE terms are 3–5 years. Longer terms provide better per-unit pricing but increase lock-in risk.
Typical RISE PCE contracts for a mid-market enterprise (1,000–5,000 named users) range from €1.5M to €8M per year, depending on scope, user count, and deal leverage. Global enterprises with 20,000+ users regularly see annual RISE fees exceeding €20M.
What RISE Actually Bundles
RISE with SAP PCE includes, within the contracted scope:
- S/4HANA Private Cloud Edition licence (named user and package)
- SAP Enterprise Support (the 22% maintenance equivalent embedded as a fixed uplift)
- Infrastructure hosting on the selected hyperscaler
- SAP Basis operations (patching, backups, monitoring)
- SAP Business Technology Platform entitlements (see BTP bundle caveats)
- SAP Integration Suite (standard tier, SAP-to-SAP integrations only)
- SAP Build Work Zone (standard edition)
- SAP Signavio Process Insights (limited edition in most deals)
- Defined number of BTP credits per year
RISE does NOT include (common misconception items):
- The perpetual licence value of existing SAP software — RISE is a subscription, not a conversion
- SAP Analytics Cloud beyond basic embedded analytics
- SAP SuccessFactors, Ariba, Concur, or Fieldglass
- Customisation development services
- Data migration tooling beyond SAP-supplied DTRT
- Third-party cloud infrastructure costs outside the managed tenant (e.g., customer-controlled Azure subscriptions for extensions)
⚠️ Cloud Conversion Credit Trap: SAP routinely quotes RISE using 'Cloud conversion credits' that reduce Year 1 pricing significantly. These credits — typically 50–80% of existing maintenance — disappear in Years 2–5, creating a step-up cost structure that finance teams discover only after signing.
Infrastructure and Hosting Costs
Unlike a traditional on-premise licence, RISE PCE includes infrastructure. This creates a pricing complexity: SAP marks up hyperscaler infrastructure costs before passing them to customers. Independent benchmarking consistently shows RISE infrastructure charges running 20–35% above comparable hyperscaler list prices for equivalent compute and storage.
Key Infrastructure Cost Factors
Compute Sizing: SAP uses T-shirt sizing (S, M, L, XL) based on SAPS (SAP Application Performance Standard). Undersizing creates performance issues; oversizing wastes budget.
Storage Tiers: HANA in-memory storage is expensive. PCE contracts include defined storage allocations; additional storage is available at per-GB uplifts that compound over multi-year terms.
System Landscape: Production systems are typically sized at 2–3x more resources than pre-production. SAP includes a defined number of non-production systems in the base RISE contract; additional development or QA systems are purchasable add-ons.
Disaster Recovery: SAP offers tiered DR options. Most RISE base contracts include a warm-standby DR arrangement; active-active HA requires negotiation and uplift.
The 5-Year Lock-In Risk
RISE with SAP is a long-term commitment. Once migrated to PCE, technical exit costs include: re-platforming the ERP to on-premise or another cloud, rebuilding integrations that assumed SAP-managed BTP, re-licensing previously perpetual software as new subscriptions, and potential back-licence claims if SAP conducts an audit during or after transition.
The commercial lock-in mechanisms within a typical RISE PCE contract include:
Early Termination Fees: Standard RISE contracts include penalties of 50–75% of remaining contract value for early exit
No Perpetual Licence Reversion: RISE subscription fees do not accumulate toward perpetual licence ownership
Annual Price Escalation Clauses: Most RISE contracts include 3–5% annual price escalators tied to inflation indices or at SAP's discretion
Scope Change Restrictions: Reducing named user counts mid-term typically requires renegotiation; expansion is automatically charged at then-current rates
Comparing PCE vs Public Cloud Edition
| Factor | S/4HANA Private Cloud (PCE) | S/4HANA Public Cloud (Grow) |
|---|---|---|
| Tenancy | Single-tenant, dedicated | Multi-tenant, shared |
| Customisation | Full ABAP, customer-specific | Limited to cloud-ready extensions |
| Update Cycle | Quarterly (managed) | Continuous (mandatory) |
| Migration from ECC | Feasible with brownfield approach | Greenfield only |
| Typical Deal Size | €1.5M–€20M+/year | €300K–€3M/year |
| Contract Term | 3–5 years | 1–3 years |
| Infrastructure | SAP-managed hyperscaler | SAP multi-tenant cloud |
| Lock-in Risk | Very high | Moderate |
| Negotiation Leverage | Moderate (longer cycle) | Limited |
Negotiation Priorities for RISE PCE
1. Demand a Credit Utilisation Audit Before Signing
Request SAP's internal sizing report for your SAPS requirement, not SAP's recommended configuration
2. Challenge the Cloud Conversion Credit Structure
Model the 5-year total cost with and without the Year 1 credit, and negotiate for Year 2–5 discounts rather than front-loaded credits
3. Negotiate BTP Credit Carryover
Unused annual BTP credits should roll over, not expire
4. Cap Annual Price Escalators
Remove open-ended inflation clauses; fix maximum annual increases at 2–3%
5. Secure Exit Provisions
Negotiate a clean exit clause at 24-month notice with no early termination penalty after Year 3
6. Audit the Infrastructure Pricing
Request a hyperscaler cost passthrough model with transparent markup disclosure
7. Protect Perpetual Licence Value
If converting from ECC, negotiate contractual credit for existing perpetual licence maintenance paid
Before signing a RISE with SAP contract, an independent commercial review can identify 20–40% in overpayment. Our RISE with SAP advisory service has reviewed over 50 RISE proposals and regularly identifies six-figure savings in Year 1 alone.
Frequently Asked Questions
No. RISE is a pure subscription model. Once the contract ends, you have no perpetual licence rights to S/4HANA or any bundled software. Your subscription fees do not accumulate toward future perpetual licence ownership. This is a critical distinction from traditional SAP perpetual licensing and a primary source of lock-in risk for long-term customers.
Technically, yes — but it is expensive. Standard RISE contracts include early termination fees of 50–75% of the remaining contract value. For a €5M/year, 5-year contract, early exit in Year 2 could cost €12–18M. Some deals allow exit at 24-month notice after Year 3 with no penalty, but this must be explicitly negotiated and documented in the master agreement.
Your perpetual ECC licences remain valid unless you explicitly trade them in. SAP offers cloud conversion credits for perpetual maintenance paid in the preceding 12 months, typically 50–80% of that maintenance cost. However, these are Year 1 discounts only. You should separately negotiate credits for perpetual licence value itself — a distinction many enterprises miss until post-signature.
Not in standard commercial practice. SAP positions S/4HANA Private Cloud Edition as exclusively available under the RISE with SAP umbrella contract. There is no standalone "PCE licence" offering outside RISE. If you require single-tenant S/4HANA hosting, you must commit to a RISE contract, typically for 3–5 years.
RISE list pricing is opaque — SAP rarely publishes standard rates. Enterprises typically negotiate 15–35% discounts off initial proposals, depending on contract length, user count, and competitive pressure. Very large deals (€10M+/year) can achieve 40%+ reductions. Discounts are more accessible in the out-years (Years 2–5) when enterprises are willing to commit longer. Always model the 5-year total cost, not just Year 1, to evaluate true deal economics.
Want an Independent View of Your SAP Position?
Our advisors are former SAP insiders who now work exclusively for enterprise buyers. A free 30-minute discovery call will tell you whether independent advisory would materially change your commercial outcome.
Book a Free Consultation → Download Free SAP Audit Guide →Independent SAP Licensing Advisory
We are former SAP insiders working exclusively for enterprise buyers. Our advisory services cover audit defence, contract negotiation, licence optimisation, RISE advisory, and S/4HANA migration — all buyer-side, no SAP affiliation.
Book a Free Consultation →