SAP Private Cloud vs DIY on Hyperscaler: Licence and Cost Considerations

The Two Models Defined

Before comparing the models, it is important to be precise about what each one entails. The terminology shifts frequently as SAP rebrands its offerings, so clarity at the outset prevents misunderstanding.

SAP Private Cloud (RISE with SAP / SAP Cloud ERP Private Edition): SAP acts as a single-contract provider that bundles the S/4HANA Cloud Private Edition licence, infrastructure hosting on a hyperscaler chosen from a SAP-approved list, SAP's Technical Managed Services for system administration, SAP Business Technology Platform (BTP) starter entitlements, SAP Signavio, SAP LeanIX, and SAP Business Network Starter Pack. The customer pays SAP a unified subscription, and SAP contracts directly with the underlying hyperscaler on the customer's behalf. As of 2025, the commercial packaging was further restructured as "SAP Cloud ERP Private Edition," with individual components priced as separate SKUs rather than fixed tiers, though the economic structure remains essentially the same.

DIY on Hyperscaler (Bring Your Own Licence / Self-Managed): The customer contracts independently with a hyperscaler for infrastructure. SAP licences — either on-premise licences with mobility rights, or cloud licences purchased directly from SAP — are brought to the hyperscaler environment. The customer or its system integrator manages the technical operations, with SAP providing software support under the standard RISE support terms or traditional Premium/Standard Enterprise Support. This model is often called "Bring Your Own Licence" (BYOL) in hyperscaler marketplaces.

The critical implication of these definitions is that the SAP Private Cloud model inserts SAP as a commercial and operational intermediary between the customer and the hyperscaler, while the DIY model removes that intermediary. The commercial consequences of this intermediary role are the central subject of this analysis.

How SAP's Private Cloud Pricing Is Constructed

SAP's RISE with SAP subscription price bundles three cost components that are priced separately in the DIY model: the S/4HANA software licence, the hyperscaler infrastructure, and the managed services layer. Understanding how SAP prices each component is essential for evaluating whether the bundle delivers value relative to the sum of the parts.

The Software Licence Component

The S/4HANA Cloud Private Edition licence in RISE is a subscription licence charged on a per-FUE (Full Use Equivalent) or per-user basis depending on the commercial structure. For organisations migrating from ECC on-premise, the migration resets the licence baseline. This is a critical point: the S/4HANA migration changes the licence baseline, and the RISE subscription structure does not automatically preserve the value of existing on-premise licence investments. SAP offers migration incentives — historically up to 90% of the Annual Contract Value for on-premise to RISE migrations — but these incentives are time-limited, negotiable, and require careful analysis to verify that the post-incentive subscription cost genuinely reflects a favourable conversion of the existing entitlement.

In the DIY model, organisations with existing on-premise S/4HANA licences can exercise mobility rights to run those licences on a hyperscaler without additional licence cost (subject to hyperscaler infrastructure fees). This preserves the existing licence investment, continues the legacy maintenance structure at approximately 22% of net licence value per year, and provides architectural flexibility that the RISE subscription does not. However, it also means continued exposure to the on-premise support cost increase trajectory and eventual migration pressure as SAP phases out extended ECC support by 2027 and directs attention to cloud-first development.

The Infrastructure Component

This is where the most commercially significant difference between RISE and DIY emerges. In the RISE model, SAP procures infrastructure from the chosen hyperscaler at SAP's enterprise rate and includes it in the RISE subscription at a mark-up. Independent analysis of RISE subscription costs relative to equivalent direct hyperscaler infrastructure pricing consistently indicates a mark-up of 15 to 25 percent on the infrastructure component.

The consequence of this mark-up is compounded by three factors. First, the customer cannot directly negotiate with the hyperscaler to reduce infrastructure costs during the RISE contract term — all infrastructure negotiations go through SAP. Second, the customer cannot independently right-size or optimise infrastructure consumption on an ongoing basis, as SAP manages the infrastructure layer. Third, the customer loses access to hyperscaler commit discounts, reserved instance pricing, and savings plans that are available to direct customers committing multi-year workloads at scale.

In the DIY model, large enterprises can negotiate directly with hyperscalers for committed use discounts, enterprise discount programmes, and innovation credits. AWS, Azure, and GCP all offer organisations significant financial incentives — including investment credits, migration support, and architectural reviews — to bring SAP workloads to their platforms directly. These incentives are not available through the RISE model because the customer is not the direct hyperscaler customer.

The Managed Services Component

SAP's Technical Managed Services (TMS) included in RISE covers basis administration, OS and database patching, backup management, system monitoring, and high availability configuration. For organisations that do not have strong in-house SAP basis capabilities, this managed services layer provides genuine operational value and can reduce the total cost of internal staffing for system administration.

However, SAP's TMS has a defined scope that excludes application-level support, business process configuration changes, security role management at the application level, and custom development and transport management in many configurations. Customers that sign RISE expecting comprehensive system management frequently discover that day-to-day operational support — beyond the infrastructure layer — still requires their own internal resources or an external managed service provider at additional cost. This gap between marketed scope and delivered scope is a consistent finding in post-migration assessments.

S/4HANA Migration Licence Baseline Reset: The Critical Risk

For organisations currently running SAP ECC, the migration to S/4HANA — whether through RISE or DIY — resets the licence baseline in ways that can increase total licence cost significantly. This is one of the most important financial considerations in the choice between RISE and DIY, and it receives insufficient attention in SAP's sales narrative.

Under ECC, the legacy named user licence model uses Professional User, Limited Professional, and Employee Self-Service categories. Under S/4HANA, the licence model introduces new categories including Professional User, Functional User, and Self-Service User. The conversion mapping between ECC categories and S/4HANA categories is not one-to-one, and SAP's proposed conversion mapping in migration negotiations typically involves a reclassification of a portion of the user population to higher-cost categories.

In the RISE model, the licence conversion is performed as part of the RISE subscription agreement. Customers who accept SAP's initial conversion without independent validation may discover post-migration that their subscription cost includes more Professional User entitlements than their actual user roles require — a form of structural over-licensing that is difficult to reverse within a multi-year subscription commitment.

In the DIY model, the same licence baseline issue applies, but the negotiation is more transparent because the software licence and the infrastructure are priced and negotiated separately. The licence conversion can be challenged independently of the infrastructure negotiation, providing cleaner commercial visibility.

Total Cost of Ownership: A Five-Year Framework

A complete TCO comparison between RISE and DIY must account for all cost categories over the full contract term. The most relevant time horizon is five years, aligning with RISE contract lengths and hyperscaler reserved instance terms.

Year One Costs

Year one costs for both models include migration and implementation costs, which are broadly similar regardless of deployment model. For RISE, the year one subscription cost includes software, infrastructure, and managed services. For DIY, the year one cost includes direct hyperscaler infrastructure, ongoing SAP maintenance at approximately 22% of net licence value, and internal or outsourced managed services.

SAP's RISE incentive programme — which for organisations migrating from ECC has offered migration credits of up to 67.5% of the Annual Contract Value (capped at €3 million) — reduces the effective year one RISE cost substantially. This incentive makes the year one comparison strongly favourable to RISE when incentive credits are applied. The critical question is what happens in year two through five, when the incentive period has ended.

Years Two Through Five: Where RISE Costs Diverge

After the incentive period, the RISE subscription price is fixed or subject to annual escalation clauses (typically 3 to 5 percent per year) agreed at contract signature. Meanwhile, hyperscaler infrastructure costs for direct customers can be actively managed and reduced through right-sizing, reserved instance optimisation, and consumption efficiency measures. Direct customers routinely achieve 15 to 25 percent year-over-year infrastructure cost reductions as workloads stabilise and hyperscaler pricing evolves.

RISE customers cannot access these benefits directly. The infrastructure cost component of the RISE subscription is managed by SAP, and any efficiency savings accrue to SAP rather than to the customer. This structural difference compounds over the five-year term and is a primary driver of the financial cases made by enterprises that reject RISE in favour of DIY hyperscaler deployments.

Where RISE Delivers Genuine Value

RISE with SAP is not without merit. There are specific organisational contexts where RISE's bundled model delivers genuine value that is not easily replicated in the DIY model.

Organisations with limited internal SAP basis capability benefit from the TMS layer, which eliminates the need to hire and retain specialist infrastructure and basis administrators. In markets where SAP basis skills are scarce and expensive, the total cost of internal staffing can exceed the infrastructure mark-up in the RISE subscription.

Organisations with complex regulatory or data residency requirements benefit from SAP's pre-certified RISE deployment configurations, which are tested and supported for compliance with GDPR, industry-specific regulations, and SAP's own supportability requirements. Building equivalent certifications in a DIY deployment requires investment that may not be justified for smaller organisations.

Organisations seeking speed to value — particularly those under S/4HANA migration pressure with the 2027 ECC mainstream maintenance deadline approaching — benefit from RISE's pre-configured deployment infrastructure that reduces implementation timeline risk. The governance complexity of managing multiple vendor relationships in a DIY model adds implementation project risk that is avoided in the RISE model.

Key Decision Factors and Recommendations

The RISE versus DIY decision should be made on a five-year TCO basis that accounts for all cost components, not on the initial year subscription cost or on SAP's incentive-adjusted first-year pricing. The following factors should inform the decision.

Internal capability: Organisations with strong internal SAP basis teams and cloud infrastructure skills are better positioned to capture value in the DIY model. Those without these skills face significant hidden costs in self-managed deployments.

Hyperscaler relationship: Organisations with existing committed hyperscaler relationships that include SAP workload credits and discount agreements should evaluate whether the DIY model allows those benefits to be applied to the SAP workload. In many cases, pre-existing hyperscaler agreements make the DIY model significantly more cost-effective than RISE for the infrastructure component.

Migration incentives: SAP's time-limited migration incentives for RISE should be modelled carefully. The incentive makes the year one comparison look favourable for RISE, but the five-year comparison often tells a different story. Evaluate the post-incentive subscription cost against the DIY alternative before signing.

Contract flexibility: RISE contracts commit organisations to a specific infrastructure provider and managed services scope for three to five years. DIY deployments offer greater flexibility to change hyperscalers, adjust consumption, and renegotiate services on shorter cycles. For organisations with evolving architecture requirements, this flexibility has material commercial value.

Engage both SAP and the hyperscaler simultaneously: The most effective negotiating strategy is to engage the hyperscaler directly in parallel with RISE discussions. Hyperscalers provide investment credits, migration support, and architectural services to attract SAP workloads. Using the hyperscaler's offer as leverage against SAP's RISE pricing — and vice versa — consistently produces better commercial outcomes than engaging only one party.