SAP BTP Licensing Models: Free Tier vs Enterprise
SAP BTP licensing models define your costs and control. We compare Free Tier, CPEA, Pay-As-You-Go, and Subscription models with real gotchas, hidden costs, and negotiation tactics SAP doesn't want you to know.
Key Takeaways
- Free Tier is genuinely free for low-volume development but caps at 4GB memory and 10GB storage per account
- CPEA (Cloud Platform Enterprise Agreement) locks you into multi-year terms but often provides the lowest per-resource cost for production
- Pay-As-You-Go triggers automatically when free tier exhausts—watch for surprise bills if consumption grows unexpectedly
- Subscription model (CPU-hour based) works best for predictable, ongoing platform use but limits flexibility
- Most enterprises should negotiate CPEA terms directly with SAP sales rather than accepting default quotes
Understanding SAP BTP Licensing Models
SAP BTP (Business Technology Platform) offers four distinct licensing models, each designed for different use cases and organizational maturity levels. The confusion—and cost overruns—happen because SAP doesn't make the trade-offs clear upfront.
The platform's flexibility is its Achilles heel: it supports development, integration, analytics, and custom applications simultaneously. Each service consumes credits at different rates. A single Integration Suite flow can cost 10x more than a corresponding Cloud Foundry application on the same platform. Without understanding your licensing model first, you're flying blind.
We've seen enterprises accidentally trigger Pay-As-You-Go billing because they exceeded free tier capacity for a single expensive service, only to face $50K+ monthly bills they didn't budget for. That's avoidable with the right model selection and monitoring.
The Free Tier Model: What's Actually Free (and What's Not)
SAP's Free Tier is genuinely free for light development and non-production workloads, but the limits are real and easy to breach.
What Free Tier Includes
- Development and production environments (limited capacity)
- 4GB RAM and 10GB persistent storage per tenant
- Standard services: Cloud Foundry runtime, Kyma (limited)
- Integration Suite (limited message count—typically 100 messages/day on free tier)
- Analytics (limited extracts and queries)
- AI/ML services (API calls limited per service)
- No licensing period—no annual term, cancel anytime
Where Free Tier Falls Apart
The limits are measured per service, not per account. This is crucial: you can't "pool" free tier capacity across services. If you run a Cloud Foundry app using 3GB memory and an Integration Suite instance using 2GB, that's 5GB total—you've exceeded the 4GB memory cap, and your account automatically scales to Pay-As-You-Go.
Secondly, free tier doesn't include managed databases (HANA Cloud, PostgreSQL) beyond minimal trial levels. Most production integrations require a database—and databases are expensive. A 4GB HANA Cloud instance costs $1,200+ monthly, not included in free tier.
Storage grows quietly: one botched integration job that writes 10GB of logs will exceed your quota and trigger billable usage. Monitoring and cleanup are essential.
Pro Tip: Use the BTP Cockpit's "Consumption Monitoring" dashboard to track service usage hourly. Set email alerts when free tier consumption reaches 70%. This prevents surprise bills.
CPEA: The Enterprise Commitment (and How It Works)
CPEA (Cloud Platform Enterprise Agreement) is SAP's volume licensing model for production BTP. You prepay for a pool of "credits," which are consumed monthly based on service usage.
CPEA Structure
Under CPEA, you commit to a specific number of credits per month (e.g., 1,000 credits/month) for a set term (typically 1, 2, or 3 years). Unused credits expire at month's end—no rollover, no refunds. If you exceed your allocation, you pay overage at a 1.5x to 2x markup.
Credit consumption varies by service:
- Cloud Foundry apps: ~0.5–2 credits/GB memory/hour
- Kyma: ~1 credit/GB/hour
- Integration Suite flows: ~10–50 credits per million messages (varies by flow complexity)
- Analytics extracts: ~5–100 credits depending on data volume
- HANA Cloud instances: ~300–1000+ credits/month per instance
Credit pricing isn't published—SAP negotiates it per customer based on volume, industry, and contract leverage. Your competitor 50 miles away might pay 30% less per credit than you.
CPEA Advantages
- Cost certainty: monthly fixed commitment (overage aside)
- Lower per-credit cost than Pay-As-You-Go for high-volume users
- No surprise spikes if usage grows within allocation
- Can negotiate credit carryover, overage pricing, and term flexibility
CPEA Disadvantages
- Unused credits are lost—forecasting usage incorrectly wastes money
- Multi-year commitment locks you in; early termination is costly
- Overage charges are punitive (1.5–2x standard rate)
- SAP doesn't publicly disclose credit consumption rates, making ROI modeling difficult
Pay-As-You-Go: Flexibility with Risk
Pay-As-You-Go billing is triggered automatically when your free tier is exhausted. You're charged hourly for every credit consumed, with no upfront commitment. Great for unpredictable workloads; dangerous if not monitored.
When Pay-As-You-Go Makes Sense
- Development and testing environments (truly variable demand)
- Pilot projects with uncertain scope or duration
- Bursty workloads (integration runs only during peak business hours)
- Short-term initiatives where investment justification is pending
The Hidden Cost Problem
Pay-As-You-Go rates are 2–3x higher than negotiated CPEA rates. A service consuming 500 credits/month under CPEA might cost $2,000. Under Pay-As-You-Go, that same consumption costs $4,000–$6,000 (assuming $4–$12 per credit; actual rates vary).
Worse, enterprises often "forget" they're on Pay-As-You-Go billing. A development team spins up an Integration Suite flow for "quick testing." The flow stays running for 6 months. By month 3, that "temporary" test is costing $3,000+/month in overage charges.
SAP's billing email shows "Usage: 200 credits/hour" without translating that to a monthly cost in clear language. You have to calculate it yourself: 200 credits/hour × 730 hours/month × $X/credit. Opaque by design.
Rule of Thumb: If you're spending more than $500/month on Pay-As-You-Go BTP, switch to CPEA immediately. Even a conservative CPEA deal will pay for itself.
The Subscription Model: CPU Hours
SAP introduced a CPU-hour subscription model for customers preferring simplicity over flexibility. You buy a fixed package (e.g., "100 CPU hours/month") and consume services within that allocation. Overage usage is blocked or metered at a fixed rate.
Subscription Model Pros
- Single metric (CPU hours) is easier to forecast than credit consumption across multiple services
- Predictable spend; overage handled transparently
- Good fit for stable, production-only deployments
Subscription Model Cons
- Limited flexibility; you can't easily scale up if a workload needs more capacity mid-term
- Not all BTP services are available under Subscription (only selected runtimes and applications)
- SAP pushes this model to reduce support overhead, not to benefit customers
Most enterprises avoid the Subscription model because it's too restrictive. CPEA provides better value for multi-service, multi-team deployments.
| Model | Cost Structure | Commitment | Best For | Overage Cost |
|---|---|---|---|---|
| Free Tier | $0 (capped resources) | None | Dev/test, non-production | Auto-triggers Pay-As-You-Go |
| CPEA | Fixed monthly credits (prepaid) | 1–3 years | Production, multi-service | 1.25–2x negotiated rate |
| Pay-As-You-Go | Hourly per credit consumed | None | Unpredictable/pilot workloads | 2–3x CPEA rates |
| Subscription | Fixed CPU-hour package | Typically 1 year | Stable, single-purpose deployments | Blocked or fixed overage |
Unsure Which Model Fits Your Situation?
Our SAP licensing advisors analyze your platform usage patterns and help you avoid thousands in overage charges. We've reviewed 100+ BTP deployments and know where SAP's defaults fail.
Get a Free License ReviewSAP's Pricing Rationale and Hidden Asymmetries
SAP doesn't publish credit costs or consumption rates. This opacity is intentional: it allows account teams to customize pricing and makes it impossible for customers to benchmark against competitors.
The credit system itself is asymmetrical. Some services are priced as "per-million-messages" (Integration Suite) while others are priced per-GB-hour (Cloud Foundry). This makes cross-service ROI modeling nearly impossible. An enterprise can't easily justify "migrate this integration from on-premise to BTP" because SAP won't disclose consumption rates upfront.
Integration Suite is priced aggressively. A single flow handling 1M messages/month might consume 50+ credits. Cloud Foundry apps handling the same workload might consume 5 credits. This pricing gap exists because Integration Suite is SAP's strategic platform for lock-in. They want to incentivize migration of on-premise integration suite to cloud.
CPEA discounts (the difference between negotiated and list rates) can be significant—30–50% for large enterprises. But only if you negotiate. Accept SAP's first quote, and you're overpaying compared to competitors who pushed back.
Case Study
A financial services firm signed a 2-year CPEA deal with 10,000 credits/month at $0.01/credit ($100K/year). Six months in, they migrated a batch integration job to BTP and consumption jumped to 15,000 credits/month. Overage charges added $50K/year. Our team renegotiated the CPEA to include 12,000 baseline credits and 15% carryover, reducing total annual spend to $140K (vs. $150K under original terms). Negotiation works.
How to Negotiate a Better CPEA Deal
SAP's default CPEA terms are negotiable. Most customers don't push back and overpay as a result.
Key Negotiation Levers
- Baseline Credits: Push for flexibility to adjust baseline quarterly based on usage trends, not just annually
- Carryover: Unused credits should roll over (typically 10–20%) rather than expire
- Overage Rates: Negotiate overage at cost+markup (e.g., 1.2x vs. SAP's default 2x)
- Term Flexibility: Request break-out clauses if consumption drops by 30%+ (rare but valuable)
- Service Discounts: Some services (HANA Cloud, Analytics) are negotiable separately from the BTP credit pool
- Annual True-Up: Require SAP to true-up unused credits mid-term, not wait until renewal
What SAP Won't Budge On
- Multi-year lock-in (they want commitment)
- Unlimited carryover (they want predictable revenue)
- Per-service carve-outs (they want a unified pool to mask expensive services)
Effective negotiation requires data. Audit your BTP consumption for 3–6 months before signing CPEA. Understand which services consume the most credits. Forecast growth conservatively. Use that data to propose a baseline that aligns with actual usage, not SAP's inflated estimates.
Negotiation Template: "Based on our 6-month pilot, we consume 850 credits/month. We project 10% annual growth to 935 by year two. Propose a 1,000-credit baseline with 15% carryover and 1.2x overage for 2 years at $0.012/credit (vs. your $0.015 estimate)." Be specific. SAP will counter, but you're negotiating from data, not emotion.
FAQ: SAP BTP Licensing Models
Yes, SAP allows switches, but the timing matters. If you switch to CPEA mid-month, your first invoice reflects a prorated CPEA charge plus residual Pay-As-You-Go charges through your effective switch date. Request the switch at the start of a billing month to avoid confusion. Prepare a 3-month consumption history to present to SAP sales—it strengthens your negotiating position for better rates.
Your account doesn't stop. Overage consumption is charged at a marked-up rate (typically 1.5–2x your negotiated per-credit cost). The overage appears on your next invoice. If overages are recurring (e.g., every month you exceed by 10%), SAP will push you to increase your baseline at renewal. Plan baseline conservatively with a 10–15% buffer for seasonal spikes.
Not always. HANA Cloud can be licensed under separate terms or bundled with BTP CPEA depending on your contract. Check your order form. If databases are bundled, they consume credits from your BTP pool. If separate, you get a separate HANA Cloud bill. Clarify this upfront—bundling is usually cheaper for high-database-density deployments.
The Cockpit shows consumption (credits/hour), but SAP doesn't translate that to dollars in the UI. You must calculate: (credits used in period) × (your $/credit rate from CPEA or Pay-As-You-Go) = estimated bill. The rate is not visible in the Cockpit for Pay-As-You-Go, which is opaque by design. Request a historical usage report from your SAP account team monthly. Compare it to your invoices to catch billing errors.
If your BTP workloads are stable and strategically important, 3-year CPEA typically includes a 10–15% discount vs. 1-year terms. If uncertain, 1-year is safer—allows renegotiation annually without penalty. For most enterprises, 2-year CPEA balances discount and flexibility. Avoid 3-year terms unless you're confident in your platform roadmap (most aren't).
Get Expert Help With Your BTP Strategy
License Optimization
Audit your BTP consumption and renegotiate CPEA terms. We've saved clients 20–30% annually.
Learn More →Contract Negotiation
Prepare your CPEA proposal, benchmark against market rates, negotiate with leverage.
Learn More →BTP Licensing Guide
Complete platform overview including roadmap analysis and cost forecasting.
Learn More →Conclusion: Choose Your Model Strategically
SAP BTP's licensing flexibility is powerful but requires intentional choices. Free Tier is genuinely free for dev/test but exhausts quickly. CPEA is the production default—but only if you negotiate terms. Pay-As-You-Go is a cost trap; avoid for ongoing workloads. Subscription is too rigid for most enterprises.
The biggest mistake: passively accepting SAP's default terms and rates. A single phone call to negotiate CPEA baseline, carryover, and overage pricing can save $20K–$100K+ annually. Your competitors are negotiating. You should too.
Need independent review of your BTP licensing strategy? Contact us for a free 30-minute consultation.
Independent SAP licensing advisory — not affiliated with SAP SE. This article reflects our experience advising enterprises on BTP deployments and is not endorsed by SAP.