SAP’s Business Technology Platform (BTP) is the foundation of its cloud strategy. It’s a powerful and flexible platform-as-a-service (PaaS) that allows you to build integrations, create extensions, and leverage advanced analytics and AI capabilities. But with great power comes great licensing complexity. BTP’s consumption-based model is a world away from traditional SAP licensing, and if you’re not careful, costs can quickly spiral out of control.
The Three Flavors of BTP Licensing
SAP offers three main commercial models for BTP, each with its own pros and cons:
- Pay-As-You-Go (PAYG): This is the entry-level option. With PAYG, there’s no upfront commitment. You simply activate the services you need and pay for what you use at the end of each month. It’s incredibly flexible and a great way to experiment with BTP services without any risk. The downside? You pay full list price for everything, which can get expensive at scale.
- Cloud Platform Enterprise Agreement (CPEA): This is SAP’s preferred model for enterprise customers. With a CPEA, you prepay for a pool of “cloud credits” that you can use to consume any BTP service. Think of it like a prepaid debit card for the BTP. The more you commit to upfront, the bigger the discount you get on the credits. This gives you the flexibility of a PAYG model with the cost benefits of a bulk purchase. The catch is that the credits are “use-it-or-lose-it”—if you don’t consume them by the end of your contract term (usually one year), they expire.
- Fixed Subscriptions: For certain high-use services, you can opt for a traditional fixed-price subscription. For example, you might buy a subscription for the Integration Suite that gives you a certain number of messages per year for a fixed fee. This model offers cost predictability but lacks the flexibility of a CPEA. If you don’t use your full entitlement, you still pay the full price, and you can’t reallocate that spend to other BTP services.
| Model | How It Works | Pros | Cons | Best For |
|---|---|---|---|---|
| PAYG | Pay monthly for what you use | Zero commitment, high flexibility | No discounts, unpredictable costs | Pilots, experiments, small-scale usage |
| CPEA | Prepay for a pool of cloud credits | Volume discounts, high flexibility | Upfront commitment, risk of wasted credits | Enterprises with steady, multi-service BTP usage |
| Fixed Subscription | Fixed annual fee for a set capacity of a specific service | Predictable cost for that service | Inflexible, risk of under-utilization | High, consistent usage of a single BTP service |
Understanding Credit Consumption
In the CPEA and PAYG models, everything revolves around the consumption of cloud credits. One credit is roughly equivalent to one US dollar at list price. Each BTP service has its own unique consumption metric and rate. For example:
- SAP HANA Cloud is charged per hour based on the amount of memory and storage provisioned.
- The Integration Suite is charged per message processed.
- Application runtimes like Cloud Foundry are charged per hour based on the amount of memory allocated to your applications.
- AI and machine learning services are often charged per 1,000 API calls.
It’s critical to understand these metrics and monitor your consumption closely. A small, experimental app might only burn a few credits a day, but a large, production-grade HANA Cloud instance can consume thousands of credits a month. SAP provides dashboards and alerting tools to help you track your usage, and you should be using them. Set up budget alerts to notify you when you’re approaching your credit limit, and review your consumption reports monthly to identify any unexpected spikes.
Negotiating Your BTP Contract
When you’re ready to sign a CPEA, don’t just accept SAP’s standard terms. There are several key points you should negotiate to protect your budget and give yourself more flexibility:
- Commitment Discounts: The bigger your upfront commitment, the bigger your discount should be. Benchmark your deal against similar companies to make sure you’re getting a fair price.
- Rollover Rights: SAP’s standard policy is that unused credits expire at the end of the year. Push for the ability to roll over a percentage of your unused credits (even 10-20%) into the next year. This gives you a buffer if your projects are delayed.
- Rate Protection: Lock in the consumption rates for BTP services for the duration of your contract. This protects you from any mid-contract price hikes.
- Flexibility to Convert: Ask for the ability to convert a fixed subscription into CPEA credits (or vice-versa) if your needs change. This gives you an escape hatch if you find you’re not using a subscription service as much as you expected.
BTP is a powerful platform, but its consumption-based pricing model requires a new level of financial governance. By choosing the right licensing model, monitoring your usage diligently, and negotiating a favorable contract, you can unlock the full potential of BTP without getting hit with a surprise bill.