Key Takeaways
- RISE with SAP includes a limited "RISE BTP Bundle" consisting mainly of Integration Suite Starter and modest Cloud Foundry memory
- 70% of customers never fully consume their included BTP capacity, yet SAP markets BTP as "fully included"
- Enterprise-grade services like Datasphere, SAC, and advanced AI/ML capabilities require significant additional investment
- Most organisations exceed their included BTP capacity within 12-18 months of going live
- Negotiating expanded BTP entitlements at contract signature is 30-40% cheaper than purchasing overages post-go-live
Understanding the RISE with SAP BTP Included Bundle
When SAP sells RISE with SAP contracts, the marketing materials emphasize comprehensive cloud platform inclusion. The reality, however, is that RISE with SAP bundles a very specific subset of BTP services under the label "RISE Bundle." This bundle is designed to be sufficient for basic cloud integration and limited extension scenarios—not for enterprise-scale digital transformation. For a comprehensive breakdown of how the different SAP BTP extension scenarios consume credits and interact with RISE bundles, see our complete enterprise guide.
The RISE Bundle typically includes:
- Integration Suite Starter Edition: Basic capabilities for connecting SAP ERP to cloud applications using pre-built connectors. This covers simple point-to-point integrations but lacks advanced features like API Management or advanced transformation logic available in Integration Suite Premium.
- Cloud Foundry Runtime (Limited): Usually 4-8 GB of memory for running custom applications. This is adequate for development and testing environments but insufficient for production workloads at scale.
- Core Database Services: HANA Cloud and PostgreSQL connectivity at standard configurations, but with storage and processing limits.
- Basic Identity Services: Single sign-on and identity management sufficient for small deployments.
- Standard Monitoring & Logging: Application Performance Monitoring and basic alerting for system health.
This is where SAP's marketing diverges from operational reality. SAP sales teams frequently present this bundle as if it covers all BTP needs "for most customers." In practice, 70% of RISE customers discover within 12-18 months that they've outgrown these baseline allocations.
What BTP Services Are NOT Included in RISE
The critical services absent from the RISE Bundle are the ones that drive real business value and, consequently, where SAP captures additional revenue:
1. Datasphere (Enterprise Data Mesh)
Datasphere is SAP's enterprise data platform for building cloud-native data meshes. It's essential for analytics, data governance, and insights. Datasphere is explicitly not included in RISE. Every connection, workspace, and data object incurs separate licensing charges. For a mid-market organisation integrating data from 5-10 systems, annual Datasphere costs easily exceed EUR 200,000 on top of your RISE investment.
2. SAC (Analytics Cloud)
SAP Analytics Cloud (SAC) is the modern analytics and planning platform. While basic Analytics Cloud functionality exists within some RISE tiers, advanced features like predictive analytics, integrated planning, and real-time dashboarding require separate SAC licensing. This is where many organisations face unexpected costs after discovering they need predictive capabilities for their digital transformation.
3. Advanced Integration Suite Packs
The Integration Suite Starter included in RISE covers basic scenarios. Premium capabilities—API Management, advanced process integration, B2B integrations, and event-driven architecture—require upgrading to Integration Suite Premium or purchasing additional packs. Each additional capability pack costs EUR 5,000-15,000 annually per entitlement.
4. AI and Machine Learning Services
BTP's AI and ML services, including SAP AI Core and generative AI capabilities, are separately licensed and consume significant CPEA credits. Training custom models, deploying inference endpoints, or integrating OpenAI/third-party LLMs through BTP incurs substantial variable costs on top of your RISE contract.
5. Advanced Cloud Foundry Memory and Services
Beyond the baseline 4-8 GB, additional memory, persistent storage, and premium runtime environments require purchasing additional Cloud Foundry capacity in 4 GB or 8 GB increments at EUR 1,200-2,000 per increment annually.
6. Kyma Runtime (Serverless Extension)
Kyma is SAP's serverless runtime for event-driven extensions. While available on BTP, Kyma capacity and consumption are separately metered and billed. For organisations building event-driven architectures or composable applications, Kyma costs often exceed baseline RISE allocations.
7. Advanced Security & Compliance
Standard identity management and basic encryption are included. However, advanced security services—Key Management Service, advanced threat detection, compliance automation frameworks—are either unavailable or require separate licensing and implementation services.
The Capacity Reality: When You'll Exceed Included BTP Allocations
A typical RISE contract includes Cloud Foundry memory sufficient for perhaps 2-3 test environments and lightweight production workloads. Here's where customers typically hit capacity limits:
| Scenario | Included Capacity | Typical Need (12 Months) | Overage Cost |
|---|---|---|---|
| Basic Cloud Foundry Usage | 4-8 GB Memory | 20-30 GB | EUR 2,400-3,000/year |
| Integration Scenarios | Integration Suite Starter | Integration Suite Premium + Packs | EUR 15,000-25,000/year |
| Data Platform Usage | Basic HANA, No Datasphere | Datasphere + Advanced HANA | EUR 150,000-300,000/year |
| Analytics & Planning | Basic reporting | SAC + Predictive capabilities | EUR 80,000-150,000/year |
| Event-Driven Extensions | Cloud Foundry only | Cloud Foundry + Kyma | EUR 10,000-20,000/year |
For a mid-size manufacturing organisation, discovering mid-contract that they need Datasphere integration alongside their RISE investment creates a situation where the original "fully included cloud" promise dissolves into separate negotiated agreements and unexpected costs.
RISE BTP Bundle vs Market Positioning: The Gap
SAP's positioning of RISE with SAP emphasizes that "all cloud capabilities are included." This messaging is technically accurate for a specific subset of services but fundamentally misleading about scope. Here's the positioning vs. reality:
SAP's Marketing Message: "RISE with SAP includes comprehensive BTP capabilities for digital transformation and cloud-native extension."
Operational Reality: "RISE with SAP includes a limited integration and runtime sandbox sufficient for basic proof-of-concept scenarios, with production-grade data, analytics, and advanced integration capabilities sold separately."
This gap creates predictable contract friction. Organisations sign RISE expecting cloud transformation; within 6-12 months, they discover they're negotiating expensive add-ons or facing significant unbudgeted overage charges.
Avoid the RISE BTP Trap
Our contract negotiation specialists help organisations expand BTP entitlements at signature, locking in 30-40% better pricing than negotiating overages post-go-live. Get clarity on what your business actually needs before signing.
Negotiate Better TermsHow to Negotiate BTP Capacity Into Your RISE Contract Before Signing
The leverage to expand BTP entitlements is highest before contract signature. Once you sign, SAP's negotiating position hardens significantly. Here's how to approach pre-signature negotiations:
Step 1: Conduct a BTP Capacity Assessment
Before engaging SAP sales, perform an internal assessment of what BTP services you'll actually need. This requires collaboration between architecture, data, and integration teams. Key questions:
- How many integration points will you need between SAP and non-SAP systems?
- What's your data volume requirement for analytics and reporting?
- Will you build custom applications on Cloud Foundry, and if so, how many environments?
- Do you need AI/ML or predictive analytics capabilities within the contract term?
- What's your real-time event processing and Kyma requirement?
Step 2: Request Expanded Baseline Entitlements
Rather than purchasing overages post-go-live, request that SAP build expanded BTP capacity into your contract baseline. Specifically request:
- Increased Cloud Foundry memory (20-30 GB for production-grade deployments vs. baseline 4-8 GB)
- Integration Suite Premium or additional packs instead of Starter Edition
- Datasphere entitlement if analytics and data governance are priorities
- Kyma capacity if you're building event-driven extensions
- Reserved SAC licenses instead of per-use consumption
Step 3: Establish a Growth Clause
If you can't agree on fixed expanded capacity, negotiate a growth clause that allows annual increases in BTP allocation at contracted rates (typically 10-15% annually at a locked-in discount vs. list price). This prevents future overage shock.
Step 4: Lock in Pricing for Overages
Even if you can't negotiate baseline increases, always negotiate overage pricing as part of the Order Form. SAP's standard list price for overages is 2-3x the contracted rate. Lock in overage pricing at contracted rates or request a volume discount tier if you exceed baseline allocations.
The difference between negotiating expanded BTP at contract signature vs. paying overages post-go-live is substantial. A customer who negotiates an additional EUR 50,000 in annual BTP capacity at signature might pay EUR 40,000. The same capacity purchased as overage 18 months later could cost EUR 75,000-100,000.
Case Study: How Mid-Contract BTP Overage Derailed a RISE Implementation
A mid-size pharmaceutical company signed a EUR 2.2M three-year RISE contract with baseline Cloud Foundry and Integration Suite Starter. During implementation planning, they realised they needed Datasphere for master data management and quality compliance across 12 manufacturing facilities.
Rather than request at signature, they negotiated post-go-live. SAP's response was a standalone Datasphere implementation agreement at list price. They ended up paying EUR 540,000 (3 years) for services that would have cost EUR 300,000 if negotiated pre-signature. The lesson: BTP scope must be locked in before signing to avoid expensive mid-contract surprises.
Comparison Table: Included vs. Extra Across Common Scenarios
| Service/Capability | Included in RISE? | Baseline Allocation | Typical Additional Cost |
|---|---|---|---|
| Cloud Foundry Memory | Yes (Limited) | 4-8 GB | EUR 300-400/GB/year |
| Integration Suite Starter | Yes | Basic Scenarios | EUR 10K-15K Premium Upgrade |
| HANA Cloud Database | Partial | 32 GB Standard | EUR 2,000-5,000/additional 32GB |
| Datasphere | No | Not Included | EUR 150K-300K+/year |
| SAP Analytics Cloud | Minimal | Basic Analytics | EUR 80K-150K+/year |
| Kyma Runtime | Yes (Minimal) | Baseline Events | EUR 10K-20K/year |
| SAP AI Core | No | Not Included | CPEA Credits + Implementation |
| API Management | Limited | Integration Suite Starter | EUR 5K-10K Premium Add-on |
Real Cost Consequences When You Exceed Included BTP Allocation
The cost impact of discovering mid-contract that you've outgrown your included BTP allocation is significant. Here's what actually happens:
Scenario 1: Cloud Foundry Memory Overage
You signed with 8 GB Cloud Foundry memory. By month 14, you've deployed development, staging, and production environments for 3 custom applications. You need 24 GB total. The additional 16 GB costs EUR 4,800-6,400 annually for the remaining contract term—money not budgeted and requiring approval from finance.
Scenario 2: Integration Complexity Explosion
Integration Suite Starter covers your initial 2-3 integration scenarios. As you onboard vendors and expand to new business units, you need API Management, advanced transformation, and B2B capabilities. Integration Suite Premium costs EUR 15,000-20,000 more annually. Multiply by remaining contract years, and you're looking at EUR 45,000-80,000 in unexpected integration costs.
Scenario 3: Data Platform Emergency
Six months into go-live, compliance and audit teams demand a data governance platform for traceability and audit trails. Datasphere becomes non-optional. A standard Datasphere implementation adds EUR 200,000+ to your annual spend for the remainder of your contract term.
These scenarios aren't hypothetical. They're the standard path for 80% of RISE implementations. By negotiating BTP scope comprehensively before signing, you lock in costs and avoid the negotiating disadvantage of being mid-contract when requirements clarify.
Frequently Asked Questions
Technically yes, but with significant caveats. SAP includes a defined BTP bundle in RISE consisting primarily of Integration Suite Starter and baseline Cloud Foundry memory. However, most enterprise-grade capabilities—Datasphere, SAC, advanced integration packs, and AI/ML services—are separately licensed and billed. The "fully included" claim is misleading because it refers only to a baseline bundle that 70% of customers outgrow within 12-18 months.
This depends entirely on your use case, but our recommendation is to build in 50-100% headroom beyond your initial projected need. If you project needing 12 GB Cloud Foundry memory, negotiate for 18-24 GB at baseline. For integration complexity, default to Integration Suite Premium rather than Starter. The cost of negotiating expanded capacity at signature is 30-40% less than buying overages post-go-live, making this an ROI-positive investment in contract flexibility.
BTP services purchased as part of your RISE contract baseline are typically priced 30-40% below SAP's list price due to enterprise volume discounts. Overages—services purchased mid-contract when you've exceeded baseline allocation—are billed at list price, which can be 2-3x your contracted rate. For example, additional Cloud Foundry memory at baseline might cost EUR 300-400 per GB annually; as an overage, it could cost EUR 600-800 per GB. This pricing gap makes pre-signature negotiation crucial.
The BTP Cockpit does provide billing and consumption dashboards, but many organisations report that alerts are either too late, too generic, or difficult to action. By the time you receive an alert that you're approaching your limit, your development teams have often already deployed applications consuming the excess resources. This creates a reactive billing situation rather than proactive capacity management. This is another reason to negotiate adequate baseline capacity upfront rather than rely on real-time alerts to prevent overages.
Yes. While SAP defaults to list price for overages, you can negotiate capped overage rates or discount tiers as part of your Order Form. For example, you can request that any overages to Cloud Foundry memory be priced at your contracted rate (often called "protective caps") or request volume discount tiers (e.g., 10% discount on overage consumption above a certain threshold). This negotiation requires clear contractual language in your Order Form and should be a standard part of RISE contract discussions.
Need Help Negotiating Your BTP Allocation?
Our licensing specialists work with finance and procurement teams to ensure your RISE contract includes the BTP capacity and services you'll actually need. We've helped customers save 30-40% by negotiating smarter baseline allocations before signing.
Contract Negotiation
Expand your BTP baseline before signing and lock in better overage pricing.
Learn More →RISE with SAP Advisory
Strategic guidance on RISE scope, BTP requirements, and total cost planning.
Learn More →License Optimisation
Audit your RISE investment for unused services and renegotiate better terms.
Learn More →