The choice between cloud subscription (RISE with SAP or S/4HANA Cloud SaaS) and traditional on-premise perpetual licensing affects cost structure, user licensing metrics, infrastructure responsibilities, upgrade control, customisation flexibility, contract terms, and long-term vendor lock-in. This guide compares both models across every dimension that matters to CIOs, CTOs, and CFOs, providing the analysis needed to select the optimal S/4HANA licensing approach.
The on-premise model involves purchasing a perpetual licence for S/4HANA, a one-time capital expenditure that grants the right to use the software indefinitely, supplemented by annual maintenance fees (typically 22% of net licence value). The organisation manages infrastructure, performs upgrades, applies patches, and controls the entire technical landscape.
The cloud subscription model (RISE with SAP or S/4HANA Cloud public edition) involves subscribing to S/4HANA as a service with periodic fees that represent operating expenditure. The subscription includes the software licence for the contract term, cloud infrastructure, basic support, and system maintenance including upgrades and patches. The organisation does not own the software. If the subscription ends, the right to use S/4HANA ends.
The organisation purchases S/4HANA licences measured by Named Users (Professional, Limited Professional, Employee, Developer) and required engine or package licences. Annual maintenance under SAP Enterprise Support runs at 22% of net licence value. If the organisation stops paying maintenance, it retains full ownership and can continue operating at the last supported version. This exit option provides meaningful long-term negotiating leverage that does not exist in cloud. See SAP Licensing Guide.
The organisation pays annual or quarterly subscription fees calculated based on Full User Equivalents (FUEs) or named users by type. The subscription is all-inclusive: S/4HANA software licence for the contract period, HANA database licence, cloud infrastructure, standard support and system administration, and automatic upgrades. Contracts are typically 3 to 5 years with committed user volumes. Early termination typically requires paying the remainder of the committed subscription.
Provides a private cloud S/4HANA environment, either single-tenant or customer-specific landscape, managed by SAP with more flexibility for customisation through SAP's clean-core extensibility model and BTP-based side-by-side extensions. RISE is SAP's primary commercial vehicle for moving existing ECC customers to S/4HANA in the cloud.
Multi-tenant SaaS offering with standardised processes and configurations. Less customisable than RISE (no classic ABAP modifications, limited extensibility options), but typically less expensive and faster to deploy. Well-suited for organisations willing to adopt SAP's standard business processes with minimal deviation. Upgrades applied automatically on SAP's schedule.
SAP commonly uses Full User Equivalents (FUEs) in cloud contracts. FUEs convert different user categories into a single point-based metric: a Professional user might equal 1.0 FUE, a Limited Professional 0.5 FUE, and a Self-Service user 0.1 FUE. The organisation commits to a total FUE count with some flexibility to allocate across user types. This model provides user-mix flexibility but can obscure true per-user cost if not carefully analysed during negotiation. See S/4HANA Licensing Complete Guide.
| Cost Element | On-Premise (Perpetual) | Cloud/RISE (Subscription) |
|---|---|---|
| Software licence | High upfront CapEx (one-time perpetual purchase). Amortised over many years. | No upfront licence. Annual OpEx subscription. Lower initial outlay but continuous payments. |
| Infrastructure | Separate cost: data centre, hardware, hosting. CapEx or IaaS monthly fees managed by IT. | Included in subscription. SAP provides and manages cloud infrastructure. |
| Annual maintenance/support | 22% of net licence value per year. Predictable but grows with licence additions. | Basic support included. No separate maintenance fee. Premium support costs extra. |
| Upgrades | Customer-funded projects: internal effort plus system integrator costs. Customer controls timing. | Included. SAP handles technical upgrades. Customer bears testing effort but no upgrade project cost. |
| 5-year TCO | Licence + (5x maintenance) + infrastructure + upgrade projects. Higher initial cost but decreasing marginal cost. | 5x annual subscription. Lower initial cost but constant annual expenditure. |
| 10-year TCO | Same licence cost + (10x maintenance) + infrastructure. Licence already paid. Marginal cost is maintenance and infrastructure only. | 10x annual subscription (with potential 3 to 5% annual escalators). Cumulative cost continues to grow linearly or faster. |
TCO crossover typically occurs between years 4 and 7. Cloud is often more cost-effective initially due to lower upfront investment, but on-premise becomes cheaper over longer horizons because the perpetual licence is already paid. For a $5 million licence base with $1.1 million annual maintenance, the on-premise 10-year TCO is approximately $16 million (licence + 10x maintenance + infrastructure). The cloud equivalent at $2.5 million annual subscription with 3% escalation reaches approximately $28.7 million over the same period. The difference widens further beyond 10 years.
On-premise S/4HANA provides maximum flexibility for customising the system: full access to ABAP code, unlimited extensibility options, and complete control over the modification landscape. The organisation determines the upgrade schedule, choosing when to adopt new versions based on business readiness. For organisations with highly differentiated business processes requiring deep system customisation, or in industries where change management must be tightly controlled, on-premise provides control that cloud models restrict by design.
Cloud and RISE shift infrastructure management, security patching, backup operations, disaster recovery, and technical upgrade execution to SAP and its hyperscaler partners. This reduces internal IT operations burden, eliminates hardware refresh cycles, and provides SLA-backed availability guarantees. For organisations with limited IT infrastructure teams or pursuing a cloud-first strategy, cloud deployment reduces operational complexity significantly.
On-premise provides stronger long-term negotiating position: the organisation owns the licences, can continue operating without maintenance, can engage third-party support alternatives, and has no contract expiry that forces renewal. Cloud creates deeper lock-in: committed payments regardless of usage, no software ownership at term end, early termination requires paying the full remaining commitment, and renewal negotiations occur where SAP knows switching cost is enormous. Pre-negotiating exit provisions (data export guarantees, on-premise conversion rights, renewal price caps) is essential for cloud contracts.
On-premise uses traditional Named User licensing: each individual is assigned a specific licence type based on access requirements. The metric is straightforward: count users, assign types, purchase accordingly.
Cloud and RISE commonly use Full User Equivalents (FUEs). A Professional user might equal 1.0 FUE, a Limited Professional 0.5 FUE, and a Self-Service user 0.1 FUE. The organisation commits to a total FUE count rather than fixed quantities of each type. This provides more flexibility to adjust the user-mix within the committed total.
The FUE model can obscure per-user costs if not carefully analysed. A 1,000-FUE commitment at $3,000 per FUE per year might seem like $3 million, but the actual user population could be 300 Professional users (300 FUE), 400 Limited Professional users (200 FUE), and 5,000 Self-Service users (500 FUE), totalling 5,700 users at an effective average of approximately $526 per user. Understanding the FUE conversion ratios and modelling the actual user population against the FUE commitment is essential for accurate cost comparison with on-premise Named User pricing. See SAP Limited Professional Licence Guide.
The choice between cloud and on-premise is not always binary. Many organisations adopt hybrid approaches.
Deploy S/4HANA on-premise for the primary global instance (where customisation, control, and long-term cost efficiency matter most) and S/4HANA Cloud public edition for smaller subsidiaries or newly acquired companies (where rapid deployment and standardised processes are priorities). This approach optimises each deployment for its specific requirements but requires managing two licensing structures.
Start with on-premise S/4HANA to maintain control during initial implementation, with a planned migration to RISE at a future contract event when the organisation has validated its business processes. This avoids rushing into a cloud commitment before the organisation understands its S/4HANA requirements fully.
Keep the core ERP on-premise while deploying SAP cloud solutions (SuccessFactors, Ariba, Concur, Analytics Cloud) around the core. This provides cloud benefits for functions well-suited to standardised SaaS delivery while retaining full control over the core transactional system. See SAP Cloud and Hybrid Compliance.
Hybrid deployments create dual licensing structures: perpetual licences for on-premise components and subscriptions for cloud components. This requires careful management to avoid double-licensing, ensure entitlements are correctly allocated, and maintain compliance across both models. Negotiate the overall SAP relationship holistically. Use total SAP spend as leverage. Ensure conversion credits are available if moving workloads between models over time.
In the short term (1 to 4 years), RISE is often cheaper due to lower upfront investment and included infrastructure. Over longer horizons (7 to 10+ years), on-premise typically becomes cheaper because the perpetual licence is already paid and marginal cost is limited to maintenance and infrastructure. The TCO crossover typically occurs between years 4 and 7. The answer depends entirely on your time horizon, discount levels negotiated, and whether you value CapEx versus OpEx accounting treatment.
If you do not renew at term end, you lose the right to use S/4HANA entirely and must export your data and transition to an alternative system. You do not own the software. Converting from RISE to on-premise perpetual licensing at contract end requires specific negotiation and may involve additional fees unless pre-negotiated as a contractual exit provision. Always negotiate exit terms (data export guarantees, on-premise conversion rights, renewal price caps) before signing.
RISE with SAP provides a private cloud (single-tenant or customer-specific) environment with more customisation flexibility through clean-core extensibility and BTP extensions. S/4HANA Cloud public edition is multi-tenant SaaS with standardised processes, less customisation (no classic ABAP modifications), but typically lower cost and faster deployment. RISE is SAP's primary vehicle for ECC customers; public edition suits organisations willing to adopt SAP standard processes.
Full User Equivalents (FUEs) convert different user categories into a single point-based metric: a Professional user might equal 1.0 FUE, a Limited Professional 0.5 FUE, and a Self-Service user 0.1 FUE. You commit to a total FUE count with flexibility to allocate across user types. The FUE model provides user-mix flexibility but can obscure true per-user cost. Model your actual user population against the FUE commitment before signing. See S/4HANA Licensing Guide.
SAP periodically offers conversion credit programmes that allow on-premise licence value to be credited toward RISE subscriptions, sometimes at 1:1 but more often at a discount. This must be explicitly negotiated during the RISE contract discussion. Do not assume conversion credits are automatic. The credit amount, terms, and applicability vary by deal. Leverage your existing licence investment as negotiation currency when moving to RISE.
Yes. Many organisations deploy S/4HANA on-premise for the primary global instance and S/4HANA Cloud for subsidiaries, or keep the core ERP on-premise while using SAP cloud solutions (SuccessFactors, Ariba, Concur) for peripheral functions. Hybrid requires managing dual licensing structures and ensuring no double-licensing. Negotiate the overall SAP relationship holistically for maximum leverage. See Cloud and Hybrid Compliance.
Essential negotiation points: FUE pricing and conversion ratios, annual escalation caps (0 to 3% vs uncapped), exit provisions (data export, on-premise conversion rights), renewal price guarantees, conversion credits for existing on-premise licences, BTP credits and inclusions, SLA commitments with financial remedies, and flexibility to adjust FUE allocation annually without penalty. Start preparation 6 to 12 months before signing. See SAP Contract Negotiation Playbook.
Redress Compliance provides independent SAP advisory for S/4HANA licensing decisions: TCO modelling, FUE analysis, RISE contract negotiation, on-premise licence optimisation, hybrid strategy design, and migration planning. We help enterprises evaluate both models with their actual data and negotiate the optimal licensing structure. Complete vendor independence. No SAP partnerships, no resale commissions.
SAP Advisory ServicesIndependent SAP advisory helping enterprises evaluate RISE vs on-premise S/4HANA, model TCO accurately, negotiate FUE pricing, and secure optimal contract terms. Fixed-fee engagement models.