SAP Business Technology Platform has over 1,000 services across dozens of categories — and the pricing model is deliberately opaque. Some services are free. Some consume BTP credits. Some require separate subscriptions. And some that appear free in your RISE with SAP bundle are quietly capped at usage thresholds that trigger overage charges. Understanding what you actually have access to — and what will trigger unexpected costs — requires navigating a service catalogue that SAP redesigns frequently.
What Are BTP Service Plans?
Every service in SAP BTP is accessed through a "service plan" — essentially a pricing and capability tier. The same service (e.g., SAP Integration Suite) may have multiple plans at different price points with different feature sets. Enterprise licence agreements typically specify which plans you're entitled to use, but the BoM (Bill of Materials) rarely maps clearly to the BTP service catalogue. The result: teams spin up services they believe are covered, only to find at contract review that they've been consuming from the wrong plan tier.
Service plans fall into four commercial categories:
Want an Independent View of Your SAP Position?
Our advisors are former SAP insiders working exclusively for enterprise buyers. A free 30-minute discovery call will tell you whether independent advisory would materially change your commercial outcome.
Book a Free Consultation → Download Free SAP Audit Guide →- Free plans — zero cost, usually dev/test tier with hard limits
- Free for production — full-featured but limited to specific use cases within RISE or GROW bundles
- Consumption-based — charged against your BTP credit balance
- Subscription-based — flat fee regardless of usage (negotiated separately)
Free Tier vs Free for Production — They Are Not the Same
SAP markets two types of "free" access that enterprises routinely confuse:
Free Tier Plans
Free Tier plans are sandboxed, capacity-limited versions intended for exploration and learning. They cannot be used for productive workloads and are typically capped at 1 instance per global account. For development teams evaluating BTP services before commitment, Free Tier is appropriate. For finance teams counting on it to support business processes, it's not.
Free for Production Plans
Free for Production plans (sometimes labelled "Standard" within RISE/GROW bundles) include BTP services that SAP packages as part of your RISE or GROW subscription at no incremental credit cost — but only for specific use cases within the contracted scope. Examples include SAP Integration Suite (for core ERP integrations), SAP Build Work Zone (for the standard digital workplace experience), and a set of SAP AI services provided at minimum viable capacity. The catch: the moment you extend beyond the bundled use case — adding third-party integrations, building custom extensions, or scaling document processing volumes — you move into consumption territory.
Consumption-Based Service Plans
Most of the BTP service catalogue operates on consumption pricing. Services are priced in "SAP BTP service units" or simply debited from your cloud credit balance. The challenge enterprises face is forecasting: consumption rates vary by transaction volume, data volume, and user activity — and SAP provides conservative reference consumption values that rarely match real-world usage.
Key consumption-based services to monitor:
- SAP Integration Suite (beyond bundled integrations): billed per integration flow execution and per GB of data processed
- SAP Analytics Cloud: story licences and planning capacity both consume credits above bundle thresholds
- SAP AI Core / AI Launchpad: inference calls consume credits at rates that scale with model complexity
- SAP Document Information Extraction: billed per document page processed
- SAP HANA Cloud (BTP-hosted): compute capacity units billed hourly; pausing instances when not in use is critical
Without real-time usage dashboards configured in the BTP cockpit, enterprises routinely discover overages at contract review rather than during normal operations. Each service has different consumption metrics — understand your baseline before moving to production.
Subscription-Based Service Plans
A subset of BTP services are available only as fixed-term subscriptions, separate from the credit model. These include:
- SAP Integration Suite (Enterprise Agreement tier with guaranteed capacity)
- SAP Build Apps (per-user subscription model)
- SAP Datasphere (capacity-based subscription)
- SAP SuccessFactors extensions (charged per employee per year, separate from the core SF contract)
Subscription plans often offer better commercial predictability but require upfront commitment. Enterprises that negotiate BTP subscriptions separately from their ERP contract frequently pay more than customers who embed BTP commitments into an ELA negotiation.
RISE with SAP BTP Entitlements — What's Actually Included
RISE with SAP includes a defined set of BTP services and credit allocations, but the specifics depend on your edition and the size of your deal. SAP publishes a generic "RISE with SAP — Included Services" list, but actual entitlements are defined by your Order Form addendum, not the marketing documentation.
Typical RISE BTP Inclusions
- SAP Integration Suite (standard plan, limited to SAP-to-SAP integrations)
- SAP Build Work Zone (standard edition)
- SAP Business Application Studio (basic capacity per developer)
- SAP Joule (at basic tier, where available)
- BTP credits allocation (typically €10K–€50K equivalent per year depending on deal size)
What RISE Does NOT Include Without Separate Purchase
- Integration Suite at enterprise scale (third-party connections, high-volume APIs)
- SAP Analytics Cloud stories beyond basic embedded analytics
- SAP HANA Cloud at production scale
- SAP AI services beyond minimum viable thresholds
- Datasphere data warehousing
Request a detailed BTP Services Entitlement matrix from SAP during your initial setup. This document, usually maintained by the SAP Customer Success team, maps your specific Order Form to service plans and credit allocations. Without it, you're estimating rather than managing.
Cloud Credits vs Service-Specific Quotas
Not all BTP entitlements are credits. Some services have quota-based entitlements — a fixed number of instances, tenants, or activations — that don't deplete a credit balance but do impose hard caps. Running into a quota limit typically causes service activation to fail silently, which is how development teams discover they've reached a limit only when a deployment breaks.
Credit-based entitlements are more flexible but harder to govern. Without real-time usage dashboards and alert thresholds configured in the BTP cockpit, enterprises routinely discover overages at contract review rather than during normal operations.
| Service Model | Entitlement Type | Governance Challenge |
|---|---|---|
| Free Tier | Instance quota | Typically 1 instance per global account — breach is immediate and visible |
| Free for Production | Usage quota | Thresholds are service-specific and hidden in service documentation |
| Consumption-based | Credit balance | Rates vary by service; without alerts, overage discovery happens at invoice time |
| Subscription-based | Entitlement per contract term | Requires manual tracking; auto-renewal can occur without governance awareness |
Managing SAP BTP entitlements requires visibility that most enterprises don't have at contract time. Our SAP license optimisation service includes a full BTP audit that maps your service plans to costs and identifies optimisation opportunities before your next renewal.
Optimisation Strategies
- Map every active service plan in your BTP cockpit to a cost owner and business case. A service with no clear business justification should be desubscribed.
- Configure monthly credit alerts at 70%, 85%, and 100% of budget in BTP Cost Centre. Reactive discovery of overage is the most expensive form of governance.
- Pause HANA Cloud instances outside business hours using scheduled jobs. The cost savings from pausing a single 4-CPU instance can fund a dedicated governance resource.
- Audit Free Tier instances — if they're running productive workloads, you're violating terms and creating audit risk. Move them to appropriate production plans or deactivate them.
- Negotiate a credit carryover provision in your next contract — SAP standard terms expire unused credits at year-end. A carryover clause preserves capital investment across fiscal years.
- Before renewing RISE, request a credit utilisation report from SAP for Me covering the full prior contract term. Use actual consumption data to right-size your next commitment.
- Separate dev/test environments into their own global accounts with independent credit allocations. This prevents test consumption from masking production overage.
- Implement service entitlement approval workflows that require business justification before BTP subscriptions are activated. Subscription sprawl is the fastest path to budget overruns.
Frequently Asked Questions
Free Tier plans are sandboxed environments for exploration, capped at 1 instance per global account and not suitable for productive workloads. Free for Production plans are full-featured BTP services included in RISE or GROW bundles at no incremental credit cost, but only for specific use cases. The moment you exceed the bundled scope (e.g., adding third-party integrations to Integration Suite), you move into consumption-based billing.
Under SAP's standard contract terms, unused BTP credits expire at the end of your contract term and do not roll over. However, you can negotiate a credit carryover provision if you have significant spare capacity. This is a common point of negotiation in RISE renewals — include it in your contract if you want preservation of unused capital.
Yes. BTP credits are negotiable. Your baseline allocation depends on your RISE edition and deal size, but SAP will often increase allocations in exchange for longer contract terms or higher ERP commitments. Request a usage report for the prior 12 months from SAP for Me, compare it to your allocation, and propose an uplift based on actual consumption patterns.
If you exceed your BTP credit allocation, SAP will typically suspend service activation for consumption-based services until the overage is resolved. Subscription-based services continue to operate (they're not credit-dependent). Overage costs are billed at the end of the contract period and can be substantial. Proactive monitoring with alert thresholds prevents this scenario.
Shadow services are billed from the same credit balance as the primary service but are not visible in your subscriptions list. They're automatically activated when other services are deployed. SAP Credential Store, SAP Service Manager, and Alert Notification are common examples. Your only visibility into shadow service consumption is the BTP Cost Centre usage dashboard — configure it early.
Independent SAP Licensing Advisory
We are former SAP insiders working exclusively for enterprise buyers. Our advisory services cover audit defence, contract negotiation, licence optimisation, RISE advisory, and S/4HANA migration.
Book a Free Consultation →