What's Actually Included in RISE Infrastructure: IaaS, Managed Services, BTP Credits and What Costs Extra

SAP markets RISE with SAP as a "complete solution." One contract, one price, everything included. The reality is more complicated — and more expensive. Understanding exactly what's in your RISE infrastructure bundle, what SAP marks up, and what will generate additional invoices is the foundation of any intelligent RISE negotiation.

Most enterprises sign RISE agreements without mapping the true total cost of ownership (TCO). They assume the monthly recurring charge covers infrastructure, managed services, and platform capabilities. Then, six months in, they discover that critical capabilities are missing or cost extra. By then, your negotiating position has evaporated.

The RISE Infrastructure Stack — What SAP Actually Provides

RISE infrastructure runs on AWS, Azure, or Google Cloud Platform. SAP provisions and manages the environment on your behalf, but this arrangement comes with important boundaries.

Here's what SAP's infrastructure entitlement typically covers:

• IaaS provisioning and management: SAP creates virtual machines, storage, and networking in your chosen hyperscaler region. You don't select hardware directly — SAP determines instance sizing based on your system specifications.
• SAP BASIS managed services: SAP BASIS engineers monitor system health, apply kernel patches, and manage database administration. This is a critical service component, and SAP often uses it as a pricing lever during negotiations.
• OS patching and infrastructure monitoring: SAP keeps operating systems and hypervisor layers current. You receive 24/7 infrastructure monitoring with defined SLA response times (typically 1-4 hours depending on severity).
• Disaster recovery and backup: SAP provides backup and restore capabilities within defined Recovery Point Objective (RPO) and Recovery Time Objective (RTO) parameters. Standard RISE includes daily backups with 24-hour RPO and 4-hour RTO.
• Standard network connectivity: Basic connectivity between your on-premises environment and the RISE cloud infrastructure. Dedicated ExpressRoute/Direct Connect circuits often cost extra.

This is substantial, but it is not the full story. SAP's infrastructure scope is narrowly defined. It covers the RISE production and one non-production environment. Anything beyond that scope generates additional costs.

What the BTP Credit Allocation Actually Covers

Business Technology Platform (BTP) credits are bundled into RISE contracts, but the initial allocation is almost always insufficient for meaningful extension work.

Initial BTP credit allocations in RISE typically cover:

• Basic integration services: Cloud Integration (CPI) at minimal consumption levels — enough for standard EDI and API connectivity, not for high-volume data flows.
• Limited identity and access management: SAP Identity Authentication Service (IAS) for basic provisioning scenarios.
• Development and test environments: Minimal compute for sandboxes, often with throttled performance.
• Analytics on SAP data: A small allocation of SAP Analytics Cloud (SAC) capacity, though most enterprises quickly exhaust this.

The critical gap: most enterprises exceed their initial BTP credit allocation within 12-18 months. Why? Because SAP grossly underestimates credit consumption for real extension scenarios. If you plan serious integration work — event-driven architecture, high-frequency API calls, large data migrations — you will need to purchase additional BTP capacity.

What RISE Does NOT Include

SAP's marketing materials often obscure what is explicitly out-of-scope. Here is the list of capabilities that will generate additional costs or are unavailable under standard RISE:

• Custom development environments: If you need more than one pre-production environment (development, UAT, performance testing), each additional system incurs separate infrastructure costs.
• Performance testing environments: Standard RISE does not include a dedicated performance testing sandbox. Load testing requires provisioning a full system.
• Additional sandbox systems beyond entitlement: RISE includes basic non-production capacity. Anything additional is billed separately.
• Data migration services: RISE infrastructure is provided, but data migration consulting and execution are separate services, often billed at high day-rates.
• Cutover support: SAP provides infrastructure; they charge separately for cutover support, hypercare, and post-launch stabilization.
• Custom network configurations: Non-standard network topologies, dedicated circuits, or high-bandwidth requirements incur additional fees.
• Premium storage above baseline: High IOPS or enhanced durability features above the baseline SLA cost extra.
• Business continuity beyond standard RTO/RPO: If you need faster recovery times, you'll negotiate add-on costs.

This is where TCO explodes. A typical RISE implementation with multiple custom development cycles, realistic data migration needs, and actual performance testing can easily cost 40-60% more than the base RISE monthly charge when you include all out-of-scope services.

The Hidden Mark-Up on Infrastructure

SAP does not disclose the underlying hyperscaler costs embedded in your RISE pricing. This is by design.

SAP sources IaaS from AWS, Azure, or GCP at enterprise rates and applies a mark-up before billing you — we estimate 15-30% depending on your contract leverage and region. You have zero visibility into the hyperscaler costs SAP negotiates. You cannot apply your own cloud commitments (Reserved Instances, Savings Plans, Azure commitments) to reduce net spend. You are entirely dependent on SAP's hyperscaler relationships.

This creates several problems:

• If you have existing AWS Reserved Instances or Azure Reserved Instances from other workloads, you cannot use them to offset RISE costs.
• You pay SAP's negotiated hyperscaler rate, not your own.
• If hyperscaler pricing drops (it periodically does), you do not see the benefit — SAP captures it in margin.
• If hyperscaler pricing spikes in your region, SAP has flexibility to allocate you to alternative regions without your consent.

Managed Services Tiers — What SAP Charges Extra For

SAP BASIS managed services are included in standard RISE, but they come in tiers with escalating costs.

Standard RISE includes what SAP calls "Preferred Success" basics — monitoring, patching, and incident response. But if you want enhanced support, SAP offers premium tiers:

• SAP Preferred Success: Enhanced SLA response times, 24/7 support availability, proactive system optimization, and dedicated BASIS capacity. This is a separate line item, typically 8-15% of your RISE infrastructure cost.
• Custom BASIS staffing: If you need 24/7 BASIS coverage in multiple geographies or languages, you negotiate bespoke BASIS capacity and SLA terms.
• Cloud connector and network appliances: Advanced network features, including dedicated SAP Cloud Connector instances and high-availability configurations, add cost.

The trap: SAP positions these premium services as "optional," but then designs your implementation to require them. For example, if you negotiate tight cutover timelines, SAP will argue that enhanced Preferred Success is necessary to meet those timelines.

What to Demand in Your RISE Negotiation

Effective RISE negotiations require pushing back on SAP's cost assumptions. Here is a checklist of items to explicitly address in your contract:

• IaaS cost transparency clause: Require SAP to disclose the underlying hyperscaler cost component and your right to audit. Include price adjustment terms if hyperscaler pricing changes significantly.
• BTP credit allocation floor with step-up rights: Negotiate a defined BTP credit entitlement and step-up rights for additional capacity without contract renegotiation. Specify the step-up pricing formula in advance.
• Additional sandbox environment entitlements: Include explicit provisioning of development, UAT, and performance testing environments at no additional infrastructure cost. Specify system sizing and resource allocations.
• Defined out-of-scope services list: Force SAP to create a negative list of services explicitly excluded from RISE. This prevents SAP from claiming surprise out-of-scope costs later.
• Infrastructure refresh commitments: RISE is a managed service, but SAP must commit to regular infrastructure refresh cycles (typically 3-5 years) to ensure technology currency.
• Cutover support inclusion: Negotiate cutover support, hypercare staffing, and post-launch stabilization within the RISE scope, not as separate billable services.

How to Model True RISE TCO

Building a defensible RISE total cost of ownership requires modeling multiple cost streams:

1. Base infrastructure cost: The monthly RISE charge for production and non-production environments as stated in the contract.
2. Additional non-production environments: Number of additional development, UAT, and testing systems multiplied by the per-system monthly cost.
3. BTP credit overage costs: Estimate your annual BTP consumption based on integration scenarios. Calculate the cost of credits beyond your initial allocation at the negotiated rate.
4. Managed services premium tier: If you require Preferred Success or enhanced SLA support, add the premium surcharge.
5. Network connectivity: Calculate the cost of dedicated circuits, ExpressRoute/Direct Connect, or other advanced network configurations.
6. Professional services: Separate from RISE, but factor in: data migration, cutover support, hypercare, and performance optimization consulting.
7. Contingency (15-20%): Add a buffer for unplanned out-of-scope services and cost overruns.

A typical 3-year RISE total cost of ownership looks like this:

Most enterprises discover that their true 3-year RISE TCO is 35-45% higher than the base contract number. This is not due to hidden fees from SAP — it's due to incomplete infrastructure scoping and underestimated professional services costs.

You can reduce this through aggressive negotiation: pushing back on additional environment costs, securing BTP step-up rights at favorable rates, and ensuring that cutover support and hypercare are included in scope.

Push Back on SAP's Infrastructure Assumptions

SAP's sales teams are incentivized to minimize the upfront RISE quote. They do this by:

• Undersizing systems (forcing you to request expansions later at unfavorable rates).
• Underestimating BTP credit needs (setting you up for overage purchases).
• Leaving infrastructure components out of the quote and billing them as "post-signature discoveries."
• Building in premium support tiers by default and offering minimal discounts to remove them.

Counter this with forensic rigor. Before signing, demand detailed infrastructure specifications, including system sizing, resource allocations, backup configurations, and network topology. Compare SAP's quote against your hyperscaler's published pricing for equivalent resources. Identify discrepancies and use them as leverage.

Final Word: Get Your RISE Contract Reviewed

RISE with SAP is a powerful platform, but the infrastructure costs are structured to favor SAP's margin. The moment you sign, your negotiating position weakens dramatically. Most cost overruns happen in Year 2 and Year 3, when you're locked into the agreement and have limited leverage.

Invest in independent technical and commercial review before signature. The cost of an expert review (typically $15K-$30K) is trivial relative to the TCO impact. An effective review identifies 8-12% cost reduction opportunities on average.