📋 Executive Summary
The choice between S/4HANA Public Cloud, Private Cloud (RISE with SAP), or On-Premise directly influences total cost of ownership, agility, and license compliance risk. Each model has a distinct licensing approach — from subscription-based SaaS with FUE metrics to traditional perpetual licenses with named users — affecting budgeting (OpEx vs. CapEx), contract negotiations, and future flexibility.
CIOs must evaluate how each deployment option fits their enterprise's needs for scalability, customization, and financial model while ensuring compliance and formulating negotiation tactics that preserve flexibility — including the right to convert between models. Read the full SAP S/4HANA Licensing Complete Guide.
📑 Table of Contents
S/4HANA Deployment Options Overview
| Aspect | Public Cloud (SaaS) | Private Cloud (RISE/HEC) | On-Premise |
|---|---|---|---|
| Model | Multi-tenant SaaS | Single-tenant managed cloud | Self-managed (own DC or IaaS) |
| Customization | Limited (config + side-by-side extensions on BTP) | Full (ABAP modifications, industry modules) | Maximum (full code access, custom add-ons) |
| Updates | Automatic quarterly (SAP-controlled) | Coordinated with customer schedule | Customer-controlled timing |
| Infrastructure | SAP-managed shared | SAP/partner-managed dedicated (AWS, Azure, GCP) | Customer-managed |
| Licensing | Subscription per FUE (OpEx) | Subscription bundle: license + infra + support (OpEx) | Perpetual license + annual maintenance (CapEx + OpEx) |
| Best For | Standardized processes, mid-market, fast deployment | Large enterprises needing cloud + customization | Regulated industries, maximum control, stable environments |
☁️ S/4HANA Public Cloud (Multi-Tenant SaaS)
SAP hosts the ERP on shared infrastructure, delivering standardized S/4HANA with automatic quarterly updates and industry best practices. Limited to configuration and side-by-side extensions on SAP Business Technology Platform — no deep core code modifications.
All infrastructure, security, and operations managed by SAP. Faster deployment with pre-configured processes. Often favored by mid-market firms and divisions of larger companies where heavy customization is not required.
Licensing: Subscription-based FUE (Full User Equivalent) model. All-inclusive fee covers software, support, and cloud infrastructure. No traditional named-user licenses — compliance measured by staying within purchased FUE quota.
🔒 S/4HANA Private Cloud (RISE with SAP / HEC)
Single-tenant environment on dedicated resources (SAP data center or hyperscaler). Full scope of S/4HANA including industry-specific modules and customer-specific modifications. Essentially on-premise software deployed on managed cloud.
SAP/partner manages infrastructure, patches, and upgrades (coordinated schedule). Greater control over timing, security, and compliance postures. Classic ABAP extensions and modifications permitted. Chosen by large enterprises that need cloud benefits + customization breadth.
Licensing: Single contract bundle covering S/4HANA license + infrastructure + SAP Basis operations + BTP access + Business Network. FUE-based user counting. Infrastructure sizing (HANA memory, CPUs) also affects cost. Read our RISE with SAP Advisory for detailed guidance.
🏢 S/4HANA On-Premise (Self-Managed)
Enterprise runs S/4HANA in own data center or chosen IaaS under customer management. Maximum control over every aspect — upgrade timing, code modifications, custom add-ons, environment configurations. Customer-controlled update cycle.
IT department (or outsourced partner) handles all operations: installation, DB admin, backups, HA, security patches, performance tuning. Requires significant SAP technical expertise. Higher upfront costs but can be cost-effective over long horizons if well-managed.
Licensing: Traditional perpetual license + annual maintenance (20–22% of net license value). Named-user categories (Professional, Limited Professional, Employee Self-Service). HANA database licensed separately by memory capacity or CPU cores.
📋 Need help choosing the right S/4HANA deployment model? Our SAP-specialized advisors provide independent guidance.
SAP Advisory Services →Licensing Model Implications by Deployment
📊 Public Cloud Licensing — Subscription SaaS per FUE
Full User Equivalent (FUE): An abstract unit representing one fully active user. Companies purchase a block of FUEs distributed among user categories:
Advanced User = ~1.0 FUE (power user, broad access). Core User = ~0.2 FUE (limited, task-specific). Self-Service User = ~0.03 FUE (view reports, light tasks). Developer = ~2.0 FUEs (additional access). This tiered approach lets a larger number of light users be covered by a smaller FUE allocation.
Subscription covers software license, support, and cloud infrastructure — a single OpEx cost. No traditional named-user licenses to manage. Users can be swapped or re-categorized within FUE capacity. Minimum commitment typically ~15 FUEs, multi-year contracts.
Caution: Unused FUE capacity ("shelfware") still incurs costs. You generally cannot reduce FUE counts mid-contract — only at renewal. Carefully plan user counts and types to purchase the right FUE volume.
🔄 Private Cloud Licensing — RISE Subscription Bundle
RISE with SAP: Single contract covering S/4HANA license + infrastructure/hosting + Basis operations + BTP runtime + Business Network. Also measured in FUEs. Infrastructure sizing (HANA memory, system size) adds a cost component bundled into the subscription.
BYOL option: Enterprises with existing on-premise licenses can sometimes bring them to a hosted private cloud (HEC or partner-managed), paying only a hosting fee. Less common with RISE available, but offers flexibility for existing license owners.
Key implication: RISE shifts from CapEx to OpEx while preserving broad software scope. Simplifies vendor management (one contract) but makes cost breakdown less transparent. Once signed, you typically retire previous on-premises licenses for migrated systems — effectively trading them in.
Overprovisioning Risk: Careful FUE analysis needed — same as Public Cloud. If your contract expects 100 FUEs assuming a mix of core/self-service users, but all become heavy advanced users, SAP could claim you're exceeding capacity. See our RISE with SAP Case Studies.
🏛️ On-Premise Licensing — Perpetual + Maintenance
Named users: Professional, Limited Professional, Employee Self-Service — each granting specific access rights. Certain modules licensed by revenue, employee count, or system size. HANA database licensed separately by memory capacity or CPU cores.
CapEx model: Significant upfront purchase. Annual maintenance = 20–22% of net license value, granting support and upgrade rights. Over long periods, annual fees accumulate but are generally lower per year than equivalent subscription.
Shelfware risk: If you overestimate usage or downsize, purchased licenses become idle assets. Named-user licenses must be carefully assigned and managed. Any future cloud move requires contract conversion or new purchase — perpetual licenses cannot be simply ported to SaaS.
Audit exposure: If SAP audit finds usage beyond licensed amounts, company must purchase additional licenses + pay maintenance retroactively. An unexpected and expensive surprise. See our SAP Audit Defense Service.
📄 White Paper: 10 Proven Strategies to Cut SAP Licensing Costs — practical tactics for every deployment model.
Download White Paper →Compliance Considerations by Model
On-Premise Compliance
Customer tracks all usage. Each user/system accessing S/4HANA must have proper license. Indirect access (third-party apps using SAP data) is a major audit risk. SAP Digital Access model charges per document. SAP retains right to audit with 30 days' notice. Misclassifying users = non-compliance.
Public Cloud Compliance
System enforces limits — can't add users beyond FUE subscription. Shifts compliance to contractual level. Indirect use still applies via API calls. SAP often includes a Digital Access allowance but excess usage may require upgrade. Focus: manage user roles/counts against FUE contract.
Private Cloud Compliance
Hybrid approach. SAP audit rights apply. More freedom to customize = more risk of exceeding scope (extra sandboxes, more HANA memory). Indirect access rules still apply — negotiate coverage in RISE contract. FUE user classification must match actual usage patterns.
Cloud does not eliminate compliance management — it changes its nature. SAP's audit and enforcement stance remains rigorous across all deployment models. CIOs should ensure clear internal policies on user provisioning and integration architecture. In cloud contracts, clarify how metrics are measured and get commitments on how SAP will audit during the subscription term.
📌 Read our SAP Digital Access Advisory Service for guidance on indirect access compliance.
🛡️ Facing an SAP audit or compliance review? Our defense specialists have helped enterprises avoid millions in unexpected costs.
SAP Audit Defense Service →Cost Optimization Strategies
🏛️ On-Premise Cost Optimization
Reclaim & reassign: Periodically review user licenses. Reclaim from departed employees or changed roles. Optimize the mix — ensure heavy users have Professional licenses, casual users have limited/ESS types.
Negotiate shelfware: If you have excess licenses, negotiate license swaps or shelfware retirement with SAP. Sometimes SAP allows conversion of unused licenses into other products or credits during renegotiation.
Maintenance negotiation: Large customers can negotiate caps on yearly maintenance increases or credits for unused licenses. Some consider third-party support for savings (trade-off: lose SAP support/upgrade rights).
Infrastructure optimization: Rightsize HANA database footprint. Archive data to reduce memory requirements and lower HANA license tier. Use cost-effective hardware or cloud IaaS.
Case Study: See how enterprises have saved millions through SAP license optimization in our SAP Case Studies library.
☁️ Public Cloud Cost Optimization
Right-size FUE allocation: Not all users need "Advanced" (1.0 FUE). Many can be "Core" (0.2) or "Self-Service" (0.03). Correctly categorizing each role maximizes coverage of purchased FUEs.
Start small, scale gradually: Negotiate to begin with a lower commitment and add users at agreed pricing as needed. You generally can't reduce mid-contract — financially safer to slightly underestimate and add later than overcommit.
Leverage included services: Maximize ROI by using everything included in your subscription (analytics, mobile apps) instead of buying third-party tools. Monitor usage to inform renewal negotiations — if consistently under the limit, don't buy more.
🔄 Private Cloud (RISE) Cost Optimization
Optimize contract scope: RISE deals can bundle more than you need (Business Network, BTP credits, add-ons). Scrutinize each component — remove or scale down items you won't use near-term. Each bundled element has a cost.
Infrastructure right-sizing: Work with SAP to size systems appropriately. Archive legacy data to reduce HANA memory footprint. You can scale up later but may not easily scale down during contract.
Multi-year TCO analysis: Evaluate RISE vs. on-prem over 5+ years. Sometimes existing license owners pay a premium for RISE convenience. Ensure subscription cost is justified by benefits (reduced staff, faster innovation). Factor in that RISE includes maintenance — compare against separate on-prem maintenance costs.
Benchmark pricing: SAP cloud pricing can be opaque. Benchmark against similar companies or engage independent experts. Use competitive tension (third-party hosting with BYOL as an alternative). Negotiate: caps on annual increases, SLA credits, clear pricing for adding users/modules later.
Case Study: Learn how our clients have navigated RISE with SAP negotiations in our RISE with SAP Case Studies.
📋 Our SAP License Optimization Service has saved enterprises millions. Let us analyze your SAP licensing landscape.
SAP License Optimization →Strategic Negotiation Tactics for CIOs
🔄 Conversion & Hybrid Licensing Options
If running SAP ECC or S/4HANA on-premise, leverage SAP's Contract Conversion or RISE conversion programs that credit existing investment toward subscription. Negotiate explicit conversion rights — ability to convert unused on-premise licenses into cloud subscription credits at a later date.
Consider a "cloud extension policy" — maintain some perpetual licenses as a fallback while adding cloud subscriptions. Even if you don't move now, a clause allowing future swap at predetermined terms is valuable insurance.
🚪 Exit & Reversibility Options
Negotiate what happens at contract end or if you leave RISE:
Buy-out clause: Option to purchase perpetual license at discounted rate if exiting subscription after a certain term. Transition assistance: Reasonable period for data migration or read-only access. Retain minimal on-prem footprint: Keep small number of on-prem licenses active as insurance — negotiate reduced maintenance proportionally.
📐 Future Flexibility Clauses
SAP typically locks customers into 3–5 year contracts. Negotiate:
Growth & shrinkage: Right to adjust user quantities mid-term. Reduction options if divesting a business unit. Transfer subscriptions to other SAP products. Price protections: Cap renewal price increases (e.g., max 3%/year). Lock in pricing for additional users now. Model swap rights: Clause allowing transition between Public → Private or vice versa without complete re-licensing.
2027 Deadline Leverage: SAP knows customers must move from ECC. Use the time you have now to negotiate from a position of choice rather than last-minute desperation. The closer to 2027, the less leverage you have.
🎯 Leverage SAP's Strategic Goals
SAP is keen on moving customers to cloud. Use this:
Ask SAP for comparative TCO analyses or trial periods — can lead to improved financial terms. Be aware SAP may intentionally make on-prem deals less attractive (lower discounts, shorter support) to steer you to cloud. Demonstrate knowledge of this tactic to push for better on-prem terms as credible alternative.
If opting for cloud, negotiate value-added features: training credits, inclusion of SuccessFactors/Ariba at package rates, BTP credits. SAP often offers promotional bundling when customers make strategic S/4HANA moves.
📝 Indirect Access & Legal Protections
Address indirect use explicitly: Get written confirmation of what's included ("X documents/year of Digital Access included" or "indirect use by Salesforce front-end permitted under these conditions"). List all non-SAP front-ends and integrations — ensure coverage.
Legal counsel: Cloud contracts introduce new considerations (liability, data protection, SLA remedies). Have legal review. Engage SAP licensing specialists to identify hidden cost triggers. Ensure audit rights are reciprocal (can audit SAP's SLA compliance). Cap on indexation (inflation increases). Document everything — only the written contract governs.
Expert Guidance: Read our white paper on The Top 10 Pitfalls in SAP Digital Access Licensing for detailed indirect access strategies.
🤝 Preparing for a major SAP negotiation? Our team has negotiated hundreds of SAP contracts saving clients millions.
SAP Contract Negotiation →CIO Recommendations & Next Steps
✅ CIO Action Plan for S/4HANA Deployment & Licensing
- 1. Assess business requirements & IT strategy — map needs for flexibility, customization, and control. Standardized processes → Public Cloud. Industry-specific/regulatory → Private Cloud or On-Premise. Align with overall cloud strategy and digital transformation roadmap.
- 2. Build a multi-year TCO comparison — 5–10 year analysis for each model including software, infrastructure, internal support, implementation effort, and compliance/audit costs. Present to CFO/CEO with clear CapEx vs. OpEx trade-offs.
- 3. Engage early with SAP & independent advisors — discuss conversion programs and incentives. Validate SAP's claims with independent SAP licensing advisors or user groups (ASUG, DSAG). Informed perspective strengthens negotiations.
- 4. Strengthen license management governance — on-premise: maintain accurate user records, run SAP license measurement tools regularly. Cloud: monitor FUE consumption, track Digital Access documents, watch contractual limits. Proactive management avoids compliance firefights.
- 5. Negotiate with the future in mind — push for conversion rights, adjustment clauses, price locks, model swap options. Don't accept default contracts. Use the 2027 ECC deadline to negotiate from choice, not desperation.
- 6. Plan for organizational change — S/4HANA (especially cloud) changes operating model. Prepare IT teams and end-users for SaaS features, quarterly updates, new UIs. Invest in change management to adopt standard practices and avoid expensive custom development.
- 7. Stay informed on SAP's roadmap — RISE and GROW programs continue evolving. Engage with user groups and analyst updates. Knowledge of new options or licensing models provides ongoing renegotiation leverage. Read our SAP Licensing Knowledge Hub for the latest.
Key Takeaways
FUE Model = New Compliance Paradigm
Both Public and Private Cloud use Full User Equivalents. Right-size allocations by user category (Advanced 1.0, Core 0.2, Self-Service 0.03). Unused FUEs = wasted spend. Can't reduce mid-contract.
RISE Shifts CapEx → OpEx
RISE bundles license + infrastructure + support into a single subscription. Simplifies vendor management but makes cost breakdown less transparent. Once signed, you typically retire on-prem licenses for migrated systems.
Audit Risk Doesn't Disappear in Cloud
SAP retains audit rights across all models. Indirect access, user misclassification, and scope creep are risks everywhere. Negotiate clear metrics, Digital Access allowances, and audit procedures in every contract.
2027 Deadline = Negotiate Now
SAP ECC end-of-support creates urgency. The closer to 2027, the less leverage you have. Use time now to negotiate conversion rights, price protections, exit clauses, and model flexibility while you still have options.
SAP Advisory Services
Frequently Asked Questions
Related SAP Resources
RISE with SAP Case Studies
How we help enterprises slash costs and avoid traps in RISE negotiations.
SAP Audit Defense Case Studies
Real-world examples of how we've defended enterprises against SAP audit claims.
10 Proven Strategies to Cut SAP Licensing Costs
Practical cost reduction tactics for every SAP deployment model.
10 SAP Negotiation Tactics You Should Know
Field-tested strategies for getting better terms from SAP.
Is RISE with SAP Right for You?
A 10-step evaluation framework for assessing RISE readiness.
Top 10 Pitfalls in SAP Digital Access
Avoid the most common indirect access licensing traps.
SAP Audit Readiness: 10-Step Strategy
Prepare your organization before SAP comes knocking.
SAP S/4HANA Licensing: The Complete Guide
Deep dive into every aspect of S/4HANA licensing models and metrics.
CIO Playbook: Migrating from SAP ECC 6.0 to S/4HANA
Step-by-step migration planning including licensing conversion guidance.
SAP Digital Access Adoption Program (DAAP)
How to evaluate, negotiate, and avoid cost traps in SAP's DAAP.
Related SAP Articles
Explore more articles in this topic area:
CIO Playbook Migrating from SAP Ecc 6 0 to SAP S 4hana
SAP Guide
CIO Playbook Navigating Licensing for New SAP S 4hana Embedded Features
SAP Guide
How to Negotiate SAP S 4hana Licensing Conversions Discounts and Migrati...
SAP Guide
Mapping Legacy SAP ERP Licenses to S 4hana User Roles
SAP Guide
Negotiating Btp in Your SAP Deal Securing Free or Discounted Credits wit...
SAP Guide
On Premise vs Cloud for SAP S 4hana Total Cost of Ownership Compared
SAP Guide
Optimize Your SAP S/4HANA Licensing Strategy
Our independent SAP advisors help enterprises navigate deployment decisions, negotiate contracts, defend against audits, and optimize licensing costs across every S/4HANA model.
📚 Explore our full SAP knowledge base with articles, white papers, and case studies.
SAP Knowledge Hub →Fredrik Filipsson
Fredrik Filipsson brings 20+ years of enterprise software licensing expertise, including experience working directly for IBM, SAP, and Oracle. He has helped hundreds of organizations — including numerous Fortune 500 companies — navigate SAP S/4HANA deployments, optimize license portfolios, negotiate RISE with SAP contracts, and defend against SAP audits that protect budgets against escalating enterprise software costs.