SAP markets RISE as a simplified path to S/4HANA cloud. The reality is more complex — a long-term contractual commitment with significant pricing, SLA, BTP, and exit provisions that deserve careful independent analysis before you sign.
RISE with SAP, launched in January 2021, is SAP's bundled cloud transformation offering designed to simplify the commercial and operational complexity of moving large SAP ECC estates to S/4HANA cloud. Rather than asking customers to manage separate contracts for software licences, cloud infrastructure, application management, and support, RISE bundles all of these under a single subscription agreement with SAP as the prime contractor.
The core platform within RISE is S/4HANA Cloud Private Edition — a single-tenant, customer-specific deployment of S/4HANA, hosted on the hyperscaler of the customer's choice (AWS, Azure, or GCP) and managed by SAP's cloud services team. This is distinct from S/4HANA Cloud Public Edition, which is a multi-tenant SaaS deployment with significantly less customisation capability.
This review is part of our comprehensive SAP license negotiation guide. For the migration negotiation context that surrounds most RISE decisions, see also our S/4HANA migration negotiation guide.
SAP's RISE marketing presents it as an all-inclusive transformation package. The reality is more nuanced — RISE has a defined scope that covers several key components but excludes others that customers frequently assume are included.
Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.
The standard RISE package includes S/4HANA Cloud Private Edition software licences (including all mandatory base modules), SAP Business Technology Platform (BTP) with a standard credit entitlement, cloud infrastructure (compute, storage, networking on the chosen hyperscaler), basic application management services (system monitoring, patching, backups), SAP support (access to SAP experts and the support portal), SAP Business Network Starter Pack, and access to SAP's Digital Access model for applicable document types.
RISE does not include implementation or migration services — the project to migrate from ECC to S/4HANA is a separate cost, typically delivered by a systems integrator partner. It does not include third-party system integrations or middleware beyond the standard SAP Integration Suite credits in the BTP entitlement. RISE does not cover SAP add-on products that run alongside S/4HANA (such as SAP Fieldglass, SAP Ariba, SAP Concur) — these are separately licensed. It does not include hyperscaler-specific services beyond the baseline compute (e.g., advanced AI/ML services, data lakes, specialist networking). And the default BTP credit entitlement is often insufficient for organisations planning significant integration or extension development.
Many enterprise buyers enter RISE discussions assuming that SAP is responsible for the full transformation project. SAP's account teams sometimes reinforce this impression. In practice, RISE covers the software and managed infrastructure only — the implementation project (which can cost 2–5x the annual RISE subscription) remains entirely the customer's responsibility.
SAP does not publicly publish RISE list prices — pricing is based on a per-user model calibrated against named user type mix, organisation size, module scope, and infrastructure region. The per-user price for RISE is higher than the equivalent S/4HANA perpetual licence plus maintenance, reflecting the managed service, BTP inclusion, and infrastructure bundling. However, the total cost of ownership comparison with RISE versus self-managed alternatives requires careful modelling.
Based on market observations from negotiations involving specialist SAP advisors, RISE pricing is typically discounted 20–40% from SAP's initial proposal for large enterprises (2,000+ users). The discount level depends on the strength of your competitive evaluation, the term length you commit to, and the degree to which your account team is under pressure to close the migration. List prices are rarely what informed, advisor-supported buyers pay.
A rigorous RISE TCO comparison must account for: RISE subscription cost, migration project cost (not in RISE), additional BTP consumption beyond the included entitlement, any separately licensed SAP products, and the cost of managing cloud infrastructure versus the RISE managed service cost. When modelled fully, RISE is typically 10–25% more expensive over five years than a self-managed S/4HANA cloud deployment — the premium for the managed service element. Whether that premium is justified depends on your internal IT capability and appetite for managing hyperscaler relationships.
| Cost Component | Included in RISE | Additional Costs to Budget |
|---|---|---|
| S/4HANA software subscription | Yes | — |
| Cloud infrastructure (compute/storage) | Yes | — |
| SAP application management | Yes (basic) | Advanced managed services extra |
| SAP BTP credits | Partial | Additional BTP if integration-heavy |
| Migration/implementation project | No | Major cost — typically 2–5x annual RISE |
| SAP add-on products (Ariba, Concur, etc.) | No | Separately licensed per-product |
| Digital Access document entitlement | Base only | Additional document packs if high volume |
| SAP support | Yes (standard) | Premium/Enhanced support extra |
RISE is one of four primary paths to S/4HANA. Understanding the commercial and operational differences between them is essential before entering any RISE negotiation.
Get the IT Negotiation Playbook — free
Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.
On-premises S/4HANA involves purchasing perpetual licences with 22% annual maintenance, and running the software on your own or co-located infrastructure. It offers maximum control and customisation, avoids the hyperscaler dependency, and can be economically superior over a 10–15 year horizon if your infrastructure estate is well-managed. The financial model is capital expenditure rather than operating expenditure, which may or may not align with your organisational preferences and balance sheet treatment requirements.
Self-managed S/4HANA on AWS, Azure, or GCP gives you the cloud infrastructure benefits (elasticity, global reach, managed hardware) without the RISE managed service premium. You manage the application tier yourself and take separate contracts with the hyperscaler. This is more complex commercially but offers greater transparency, better infrastructure pricing (hyperscaler direct rates versus RISE embedded rates), and more flexibility to leverage cloud-native services beyond what SAP bundles. Organisations with mature cloud engineering capability consistently find self-managed approaches 10–20% cheaper than equivalent RISE agreements.
S/4HANA Cloud Public Edition is a multi-tenant SaaS offering with standardised processes, quarterly release cycles, and significantly constrained customisation capability. It is typically the right choice for organisations implementing SAP for the first time in simpler business environments, or for divisional implementations where a clean-sheet approach is feasible. For organisations migrating complex, heavily customised ECC landscapes, Public Cloud is generally not a viable path — the customisation and interface constraints are too significant.
RISE agreements are long-term, complex commercial contracts. The standard terms contain several provisions that enterprise buyers frequently overlook — and that create significant financial or operational exposure.
The BTP credit entitlement included in RISE is calibrated for minimal BTP usage — typically sufficient for basic SAP Integration Suite flows and a limited set of extension applications. Organisations that plan to use BTP substantively (as a primary integration platform, for ABAP Cloud development, or for AI and analytics workloads) will find the default entitlement insufficient and face overage charges at standard list rates. Negotiate BTP credit levels specifically against your integration architecture plan, with roll-over rights for unused credits and capped overage rates.
RISE default SLAs typically target 99.5% availability with service credits that are capped at a small percentage of monthly subscription fees. For business-critical ERP workloads, 99.5% represents approximately 43 hours of downtime per year — which may be acceptable for some organisations but not others. Negotiate specific availability targets (99.9%+), recovery time objectives, and meaningful service credit mechanisms that reflect the business impact of SAP unavailability, not just a token monthly credit.
Standard RISE agreements include annual price escalation clauses tied to CPI or a fixed percentage (typically 3–5%). Over a 5-year agreement, this compounds significantly. Negotiate price caps or fixed-price terms for the full agreement duration, or at minimum ensure that any escalation is limited to the software component and does not apply to infrastructure costs (which should be separately transparent and contestable).
Price escalation caps are one of the highest-value items to negotiate in a RISE agreement but one of the least commonly addressed by buyers without specialist support. A 5% annual escalation on a $5M/year RISE agreement adds over $1.3M to the total five-year cost versus a price-capped equivalent. This is pure negotiation value with no trade-off.
One of the most significant long-term risks of RISE is the exit complexity. Moving your SAP landscape to a different deployment model — or to a different ERP vendor — at the end of a RISE agreement requires careful planning that must be specified in the original contract.
Before signing any RISE agreement, negotiate explicit provisions covering: data export rights (the right to extract all your business data in standard, usable formats at any point during and at the end of the agreement), data portability timelines (SAP must provide data export assistance within a defined period of notice), transition support obligations (SAP provides reasonable support for migrating to a new environment at contract end), and licence portability (the right to continue operating S/4HANA on different infrastructure after the RISE agreement ends).
Standard RISE terms are often silent or vague on these provisions. SAP's commercial incentive is to make exit as difficult as possible to prevent contract non-renewal. Your commercial incentive is the opposite. Negotiate these terms explicitly before signing.
RISE agreements specify the hyperscaler region where your SAP data is processed. For organisations with data sovereignty requirements (GDPR, healthcare regulations, financial services data localisation), verify that the specified region and hyperscaler meet your regulatory obligations. Changes to data residency post-signature are complex and expensive under standard RISE terms. For organisations operating across multiple jurisdictions, the data residency provisions may require bespoke negotiation with SAP's cloud services team.
RISE negotiation follows the same principles as any large enterprise SAP negotiation — with a few RISE-specific considerations. The starting point is always to establish your BATNA (Best Alternative to a Negotiated Agreement) and ensure SAP's account team understands you are evaluating it credibly.
Specifically for RISE: get a detailed cost comparison against self-managed cloud before entering RISE discussions; engage an independent advisor who has reviewed multiple RISE agreements and can benchmark your SAP proposal against market; separate the commercial discussion from the technical architecture discussion so that infrastructure decisions do not drive the commercial negotiation; and sequence the negotiation so that migration incentives, BTP entitlement, SLAs, price escalation, and exit rights are all addressed before signature rather than deferred to "future discussions."
For the full RISE negotiation context, see our S/4HANA migration negotiation guide and the comprehensive SAP license negotiation pillar guide. For cloud hosting economics, see our guide on SAP on AWS vs Azure.
Evaluating RISE or reviewing an existing RISE proposal?
RISE delivers strongest value for organisations that want operational simplicity above commercial optimisation — that is, those who are willing to pay a managed service premium to avoid managing the hyperscaler relationship and S/4HANA infrastructure directly. Organisations with limited cloud engineering capability, those who want a single escalation point for SAP issues, and those whose finance teams strongly prefer opex to capex are typically the strongest RISE candidates.
Organisations with mature cloud operations, strong internal SAP technical capability, and a preference for commercial transparency and flexibility are typically better served by self-managed S/4HANA on their preferred hyperscaler — accepting more operational complexity in exchange for lower cost and greater control.
RISE is a 5+ year commitment. The terms you agree to now define your SAP costs and flexibility for a decade. Get independent commercial review before you sign.