PAYG, CPEA, or BTPEA: each meters in Capacity Units, each consumes services differently, and the wrong choice costs fifteen to twenty five percent of total RISE value. Integration Suite, Build, Datasphere, HANA Cloud, and AI Foundation pricing math. Eleven buyer moves to size and structure correctly.
SAP BTP is sold through three commercial vehicles and metered in Capacity Units, and the largest saving for most buyers is the unaudited allocation already bundled inside their RISE contract.
SAP Business Technology Platform is the umbrella for SAP's platform services: Integration Suite, Build (low code), Datasphere, HANA Cloud, Analytics Cloud, AI Foundation, and dozens of smaller services. The single meter across all of them is the Capacity Unit.
Each service consumes Capacity Units at its own rate. A heavy Integration Suite estate and a heavy Datasphere estate of the same headline value can produce very different Capacity Unit draw. The published platform overview sits on the SAP BTP product page.
Because you commit to a Capacity Unit pool up front, but the services draw against it at runtime. Undersize the pool and you pay overage at list. Oversize it and you have prepaid for capacity you never use.
PAYG is monthly consumption billing at list with no commit. CPEA is an annual prepaid commit at a discount. BTPEA is the newer multi year commit aimed at larger customers, with deeper discounts and price protection across the term.
BTP commercial vehicles compared
| Vehicle | Commitment | Typical discount | Downsize at renewal |
|---|---|---|---|
| PAYG | None, monthly | List rates | Stop any time |
| CPEA | Annual prepaid | 20 to 40 percent | Moderate |
| BTPEA | Multi year | Deeper, plus price protection | Weak |
Start on CPEA sized to your real twelve month draw, not the SAP estimate. Move to BTPEA only when consumption is stable and the discount gain clearly beats the loss of downsize flexibility.
Every RISE with SAP contract bundles a BTP allocation, usually a CPEA Capacity Unit pool sized to the RISE tier. Buyers rarely audit it, rarely monitor it, and then buy more BTP on top of capacity they already own.
On a heavy SAP estate, Integration Suite usually wins on prebuilt SAP content and on avoiding a separate licensing stack. It loses where the integration landscape is mostly non SAP and a platform like MuleSoft already carries the enterprise.
Build competes with Microsoft Power Platform on SAP centric workflows. Datasphere competes with Snowflake and Databricks. In both cases the credible alternative is your strongest discount lever, so name it before you sign.
The standard SAP account team pitch is that a larger multi year BTPEA commit is always the cheaper path because the unit discount is deeper. We disagree. In roughly two thirds of the BTP estates we reviewed, the customer already held an unconsumed CPEA pool inside RISE, so the incremental BTPEA simply prepaid for duplicate capacity at a headline discount that looked good in isolation. The buyer side move is to audit the bundled RISE allocation first, size the real twelve month Capacity Unit draw, and only then decide whether any standalone commit is needed at all. Discount depth is meaningless on capacity you never use.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
“The cheapest Capacity Unit is the one already sitting inside your RISE contract, unaudited and unused.” Fredrik Filipsson, Co Founder and Group CEO
White Paper · SAP
SAP BTP Licensing. BTPEA versus consumption strategy
How to control SAP BTP cost: when a CPEA cloud credit commit beats pay as you go subscription, the consumption traps, and the drawdown levers. Read it free.
SAP Business Technology Platform is the umbrella for SAP's platform services, including Integration Suite, Build, Datasphere, HANA Cloud, and Analytics Cloud. All of them are metered in a single unit called the Capacity Unit, and customers buy that capacity through one of three commercial vehicles.
PAYG is monthly consumption billing at list with no commitment. CPEA is an annual prepaid commit at a twenty to forty percent discount. BTPEA is a multi year commit with deeper discounts and price protection, aimed at larger customers, but with weaker downsize rights at renewal.
A Capacity Unit is the single metering currency across all BTP services. Each service draws Capacity Units at its own rate, so the same headline spend can produce very different draw depending on whether you run mostly Integration Suite, Datasphere, or HANA Cloud.
Every RISE contract bundles a BTP allocation, usually a CPEA Capacity Unit pool. Buyers frequently fail to audit it, fail to monitor consumption, or buy more BTP on top of capacity they already own. Recovering that overlap is the single biggest BTP saving for RISE customers.
Twenty to thirty five percent is realistic through right vehicle selection, Capacity Unit alignment against real usage, removing standalone commits that duplicate the RISE pool, and a credible competitive frame against MuleSoft, Power Platform, and Snowflake.
No. BTPEA has a deeper unit discount but weaker downsize rights, and it is only cheaper if your consumption is stable and not already covered by a bundled RISE allocation. Audit the RISE pool before committing to BTPEA.
On a heavy SAP estate, Integration Suite usually wins on prebuilt SAP content and on avoiding a separate licensing stack. It is weaker where the landscape is mostly non SAP and a platform like MuleSoft already carries the enterprise integration load.
It depends on the estate. Datasphere consumes BTP Capacity Units and integrates tightly with SAP sources, while Snowflake and Databricks are stronger as a neutral enterprise warehouse. The competing option is your discount lever either way.
The full paper covers the three BTP commercial vehicles (PAYG, CPEA, BTPEA), Capacity Unit consumption by service, the RISE BTP tax audit playbook, Integration Suite versus MuleSoft / Boomi / Workato, SAP Build versus Microsoft Power Platform, Datasphere versus Snowflake / Databricks, and the eleven move buyer side playbook with dollar values against each move.
Used across more than five hundred enterprise software engagements. Independent. Buyer side. Built for SAP customers running the next SAP BTP cycle.
No download. The paper opens in your browser. Corporate email only (we reject Gmail, Yahoo, Hotmail, Outlook, AOL, and similar free providers).
The cheapest Capacity Unit is the one already sitting inside your RISE contract, unaudited and unused.
Twenty years on the buy side. 500+ enterprises. $2B in client savings.
SAP BTP framework signals, BTPEA signals, CPEA signals, Capacity Unit signals, SAP Build signals, SAP Integration Suite signals, and the broader SAP platform licensing leverage signals.
