BTP Licensing & Commercial Models
Complete guide to SAP BTP commercial models — PAYG, CPEA, and Subscription. Understand how services are metered, how to optimise spend, and how to plan entitlements for BTP's major services.
Executive Summary
SAP BTP offers three commercial models: PAYG (pay-as-you-go, credit card based), CPEA (prepaid annual credit bundle, most common for enterprise), and Subscription (flat-fee per service). Most enterprise customers use CPEA — a prepaid bundle of BTP credits consumed across all services. Understanding the consumption model of each service is critical for cost planning and avoiding year-end overages.
Commercial Models Explained
PAYG (Pay-As-You-Go)
- Available for trial, sandbox, and small-scale BTP adoption
- No upfront commitment — pay monthly based on actual consumption
- Billed via credit card or monthly invoice
- Limited to services with PAYG pricing available
- Not recommended for production workloads — no SLA cost predictability
- PAYG rates are 3–4× more expensive than equivalent CPEA rates
CPEA (Cloud Platform Enterprise Agreement)
- Annual prepaid credit bundle (e.g., 100,000 BTP credits/year)
- Credits consumed by all enabled services: runtime, AI, integration, data
- Burndown tracked in BTP Cockpit → Cost Center reporting
- Overage: additional credits purchased at PAYG rates if annual bundle exhausted
- Most cost-effective for enterprises with consistent BTP usage (>$100k/year)
- Multi-year discounts: 15–30% reduction on 3-year commitments
- Some services included at no additional credit cost within CPEA (CF Runtime)
Subscription (Fixed Fee)
- Fixed fee per service per month or year — completely predictable cost
- Common for Integration Suite (Enterprise Agreement), Joule, SAP Build Apps
- No consumption anxiety — unlimited use within defined tier
- Usually chosen for mission-critical services with guaranteed high usage
- Cannot be combined with CPEA for the same service (one or the other)
BTP Service Licensing Matrix
Commercial model availability and recommended enterprise choice for the eight most commonly deployed BTP services. Rates are approximate list prices — negotiate with SAP for actual CPEA contract rates.
| Service | PAYG | CPEA Rate | Subscription | Metering Unit | Enterprise Choice |
|---|---|---|---|---|---|
| HANA Cloud | Yes | ~0.10 credits/GB-hr | No | GB RAM × hour | CPEA |
| AI Core | Yes | ~0.05 credits/unit | No | Inference units | CPEA |
| CF Runtime | Yes | Included | No | GB memory × hour | CPEA |
| Kyma | Yes | Yes | No | Node instance hours | CPEA or PAYG |
| Integration Suite | Limited | Yes | Enterprise Agreement | Messages/month | Subscription |
| SAP Joule | No | Limited | With S/4HANA tenant | Conversations | Subscription with S/4 |
| SAP Build Apps | Trial only | Yes | Per user | Active users | Subscription |
| Build Process Automation | Yes | Yes | No | Process run instances | CPEA |
CPEA Budget Planning Example
A TypeScript model for calculating annual CPEA credit consumption across core BTP services. Use this as a starting template for your own sizing exercise — add a 20% buffer before finalising the CPEA contract amount.
1// BTP CPEA credit planning — annual budget calculation
2const btpServices = [
3 {
4 service: 'SAP HANA Cloud',
5 plan: 'hana-cloud (30GB RAM)',
6 monthlyCredits: 216, // 30 GB × 24h × 30d × 0.01 credits/GB-hr
7 count: 3, // 3 production instances
8 annualTotal: 7776,
9 },
10 {
11 service: 'Cloud Foundry Runtime',
12 plan: 'standard (8GB memory)',
13 monthlyCredits: 58, // 8GB × 24h × 30d × ~0.01
14 count: 3,
15 annualTotal: 2088,
16 },
17 {
18 service: 'SAP AI Core',
19 plan: 'extended',
20 monthlyCredits: 400, // estimated based on inference volume
21 count: 1,
22 annualTotal: 4800,
23 },
24 {
25 service: 'HANA Cloud (non-prod, stop/start)',
26 plan: 'hana-cloud (16GB RAM)',
27 monthlyCredits: 46, // ~8h/day × 22 working days × 30d savings
28 count: 3,
29 annualTotal: 1656,
30 },
31 // Estimated total: ~25,000 credits/year for core services
32]
33
34// Recommendation: purchase 30,000 CPEA credits/year (20% buffer)
35// At SAP list price: ~$150,000/year CPEA contract
36// Stop/start non-prod HANA saves ~45,000 credits/year at scaleCost Optimisation Tactics
Enterprise Example (DEWA)
DEWA's annual BTP CPEA contract: 150,000 credits/year. Services in scope: 3 HANA Cloud instances (S/4 Extensions, Integration Hub, Smart City), CF Runtime (6 apps across 3 environments), AI Core (Generative AI Hub, model training jobs), and Business Application Studio (development). Integration Suite is on a separate Subscription contract (Enterprise Agreement). Monthly burndown is reviewed by the CTO and BTP admin team in the monthly IT governance meeting. Stop/start automation for non-production HANA Cloud instances saves approximately 45,000 credits/year — 30% of the total annual entitlement.
Governance
Best Practices
Use BTP Cockpit Cost Center reporting to track CPEA credit consumption weekly. Monthly reviews are too infrequent to catch anomalies before they become overages.
Configure budget alerts at 70%, 90%, and 100% of annual CPEA entitlement in BTP Cockpit. Alerts give time to act before overage charges kick in.
Automate HANA Cloud and CF app shutdown outside business hours (7pm–7am, weekends). Saves up to 60% of non-production credit consumption.
Multi-year CPEA contracts attract 15–30% discounts over list price. Volume tiers reduce per-credit cost at 100k, 250k, and 500k+ annual credit thresholds.
SAP provides free QBR sessions for enterprise customers — includes license optimisation recommendations, upcoming CPEA contract review, and early renewal pricing.