An independent comparison of RISE with SAP (managed private cloud) vs self-managed SAP on AWS, Azure, or GCP. Covers licensing models, 5-year TCO analysis, flexibility and control trade-offs, SLA differences, migration dynamics, exit clause risks, and negotiation tactics, with cost tables, decision frameworks, and real-world case studies.
This article is a spoke in our RISE with SAP Negotiation Playbook series. For the complete negotiation playbook covering licensing, pricing, and strategy, start with the pillar guide.
The choice between SAP's managed private cloud (RISE with SAP or SAP HEC) and a self-managed deployment on a public hyperscaler (AWS, Azure, or GCP) is not a hosting decision. It is a business model decision that determines your licensing structure, cost trajectory, operational control, exit options, and long-term negotiation leverage with SAP for the next 5-10 years.
Under RISE, SAP bundles software licensing, infrastructure, and managed services into a single subscription. You rent the entire stack. Under a DIY hyperscaler model, you own your SAP licences (BYOL, bring your own licence), pay the hyperscaler directly for infrastructure, and manage operations yourself or through a partner. These are fundamentally different commercial relationships with materially different financial and strategic implications.
The RISE vs DIY decision is not about where your SAP systems run. It is about who controls your licensing, your costs, and your exit options for the next decade. Choose based on leverage, not convenience.
| Dimension | RISE with SAP (Subscription) | DIY on Hyperscaler (BYOL) |
|---|---|---|
| Software rights | Subscription: you rent the software for the contract term | Perpetual: you own the software indefinitely |
| What happens at contract end | Usage rights terminate; no software asset remains | Licences remain your property; can continue on any platform |
| Existing licence investment | Suspended or converted; value is absorbed into subscription | Fully retained; continues to deliver value |
| Renewal leverage | Limited: cannot easily leave without losing all software access | Strong: you own the licences and can switch infrastructure |
| Net asset position | Depreciating: every year is pure expense with no residual value | Stable: perpetual licences are a balance sheet asset |
The RISE lock-in mechanism. When you enter RISE, your existing perpetual licences are typically suspended or converted. If you leave RISE at contract end, you may need to repurchase licences or negotiate reinstatement, and SAP has no obligation to offer favourable terms at that point. This is the single largest hidden cost of RISE: the destruction of your licence asset as a negotiation lever.
The BYOL freedom. Under BYOL, your perpetual licences give you platform mobility. You can move from AWS to Azure, from Azure to on-premises, or from one managed service provider to another without losing your software rights. SAP cannot hold your software hostage because you already own it.
| Cost Component | RISE with SAP (5 yr) | DIY on Hyperscaler (5 yr) |
|---|---|---|
| SAP software | Included in subscription (~40-50% of total RISE fee) | Existing perpetual licences + annual maintenance (~22%/yr) |
| Infrastructure | Included in subscription (~30-40% of total RISE fee) | Hyperscaler IaaS: optimisable via reserved instances, autoscaling |
| Managed services / Basis | Included in subscription (~15-20% of total RISE fee) | Internal team, MSP partner, or combination: competitively sourced |
| Year 1 cost | Often lower (SAP incentivises entry) | May be higher (migration + infrastructure setup) |
| 5-year cumulative TCO | $8-12M (example: 3,000 users) | $5.5-8.5M (same scope, optimised) |
| Residual asset at Year 5 | $0: subscription rights terminate | Perpetual licences valued at $2-4M remain |
The DIY cost advantage comes from three levers RISE customers cannot access: hyperscaler volume discounts (enterprise agreements with AWS/Azure often deliver 30-50% below on-demand pricing), right-sizing and autoscaling (shutting down non-production systems off-hours), and competitive sourcing of managed services (choosing the most cost-effective Basis provider). Over 5 years, these levers compound to create the 20-40% TCO gap.
| Control Dimension | RISE | DIY |
|---|---|---|
| Cloud provider choice | SAP dictates; typically limited to SAP's contracted hyperscaler | Full choice: AWS, Azure, GCP, or multi-cloud |
| Infrastructure sizing | Pre-allocated by SAP; changes require approval | Customer-controlled; right-size and autoscale at will |
| Upgrade timing | SAP's schedule: mandatory upgrade windows | Customer decides when and how to upgrade |
| Custom configurations | Limited; must comply with SAP's managed standards | Unrestricted; full access to OS and infrastructure layers |
| Multi-cloud / hybrid | Not supported; RISE is a single-stack environment | Fully supported; integrate with any cloud or on-prem system |
| Exit mobility | Locked to RISE for contract term; exit requires relicensing | Move to any platform at any time with owned licences |
| Migration Factor | RISE | DIY |
|---|---|---|
| SAP migration incentives | Often substantial: maintenance credits, licence conversion discounts, bundled migration services | None from SAP; hyperscaler may offer $50-200K in migration credits |
| Timeline control | SAP-driven timeline; may be faster but less flexible | Customer-controlled; phased migration possible |
| Hidden commitments | Migration incentives typically require multi-year RISE commitment (5+ years) with limited exit options | No long-term lock-in; infrastructure commitment can be as short as 1 year |
| True cost of "free" migration | Embedded in subscription premium over contract term; total cost often exceeds a standalone migration | Transparent; migration cost is a one-time project expense |
SAP's migration incentives are not gifts. They are loans, repaid through subscription premiums over the contract term. A "free" migration that commits you to a 5-year RISE contract at above-market rates is more expensive than funding the migration yourself and maintaining BYOL flexibility.
RISE exit reality. When a RISE contract ends, your usage rights terminate. You do not retain any software. To continue running SAP, you must either renew RISE (at whatever terms SAP offers, with minimal leverage) or repurchase perpetual licences (at current list prices, typically 30-50% higher than what you originally paid). SAP has no obligation to offer a competitive renewal.
DIY exit reality. When a hyperscaler contract ends, you retain your SAP licences and can move them to any platform: another hyperscaler, an on-premises data centre, or a different hosting provider. Your SAP relationship continues independently of your infrastructure decision. Your negotiation leverage with both SAP and the hyperscaler remains intact.
Case study: Retail company exit analysis reveals $2.4M renewal trap. A 5,000-user retail company evaluated RISE at $1.6M/year (25% discount). Before signing, they modelled the exit: at contract end, repurchasing equivalent licences would cost $3.8M. Renewing RISE without the introductory discount would cost $2.1M/year ($10.5M over 5 years). The DIY alternative, retaining existing licences ($1.8M in perpetual assets) plus optimised Azure hosting, projected a 5-year TCO of $6.2M. Over 10 years: $12.4M (DIY) vs $18.5M (RISE initial + renewal at standard rates). The $6.1M difference made the decision unambiguous.
| Decision Factor | RISE with SAP | DIY on Hyperscaler |
|---|---|---|
| Licensing model | Subscription: rent software | BYOL: own software perpetually |
| 5-year TCO (3,000 users) | $8-12M | $5.5-8.5M |
| Infrastructure control | SAP-managed; limited customisation | Full control; any configuration |
| Operational complexity | Low: SAP manages everything | Higher: requires internal/partner capability |
| Exit options | Weak: relicensing or unfavourable renewal | Strong: licences follow you anywhere |
| Long-term vendor leverage | Minimal at renewal | Maximum: own the software, choose the platform |
Case study: Manufacturing enterprise saves $1.3M on RISE negotiation. An 8,000-user manufacturer decided RISE was the right strategic choice but commissioned a DIY benchmark first: a fully costed 5-year model for running the same landscape on Azure with a managed service partner. The DIY benchmark showed 5-year TCO of $9.2M vs SAP's initial RISE proposal of $12.8M. Armed with this data, SAP reduced RISE to $11.5M including a 4% renewal price cap, licence reinstatement rights, and $200K in BTP credits. The $25K benchmark investment saved $1.3M and secured critical exit protections.
Your existing perpetual licences are typically suspended or converted into the RISE subscription. You do not own the software during the RISE term. At contract end, your usage rights terminate. To continue running SAP, you must either renew RISE or repurchase perpetual licences. Negotiating explicit licence reinstatement rights is critical before signing.
Not always, but typically yes by 20-40% for organisations that optimise their DIY deployment. The DIY cost advantage comes from hyperscaler volume discounts, infrastructure right-sizing and autoscaling, and competitive sourcing of managed services. However, if your organisation lacks the capability to optimise these levers, the cost gap may narrow to within 10%.
Yes, and you absolutely should. A renewal price cap (3-5% maximum annual increase) written into the initial contract protects you from SAP resetting pricing at renewal when your leverage is at its minimum. This is one of the most important negotiation points in any RISE deal.
Licence reinstatement rights are a contractual provision that guarantees your suspended perpetual licences will be restored if you exit RISE. Without this clause, leaving RISE means you have no SAP software and must repurchase licences at current list prices (typically 30-50% higher than your original purchase). Reinstatement rights are your exit insurance.
AWS, Azure, and GCP commonly offer migration credits of $100-500K for significant SAP deployments. These credits can offset 30-60% of migration costs in a DIY scenario. The credits are negotiable and should be factored into your 5-year TCO comparison.
Absolutely. A detailed DIY cost estimate is the single most effective negotiation lever in any RISE discussion. Organisations that negotiate RISE without a DIY benchmark typically pay 15-25% more than those who bring a credible alternative to the table.
A pilot is highly recommended for organisations evaluating DIY for the first time. Running a small SAP workload on a hyperscaler for 3 months typically costs $15-30K and reveals real infrastructure costs, operational complexity, and performance characteristics. The insights validate your TCO model and give you credibility in negotiations.