Guide

SAP BTP pricing: subscription, BTPEA, CPEA and pay-as-you-go, and where the prices are

As of 2026-10-30

Edited by Cédric Mary, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

SAP Business Technology Platform has no single price. SAP sells it under two commercial models: a subscription to named services at a fixed cost, or a consumption-based model in which you draw on all eligible services and pay for what you use, in one of three flavours, BTPEA, CPEA or pay-as-you-go. Per-service list prices and an estimator sit in the SAP Discovery Center; your effective price depends on the model, the commitment and the discount negotiated.

The two commercial models, in SAP's words

Subscription: your organisation subscribes only to the services it plans to use, for a fixed price over a specified period, typically one to three years, paid in advance when the period starts. You pay the same whatever you consume, and adding a service means modifying the contract through SAP sales.

Consumption-based: your organisation gets access to all current and future services eligible for the model, and can switch services on and off during the contract. It comes in three flavours: the SAP BTP Enterprise Agreement (BTPEA), the Cloud Platform Enterprise Agreement (CPEA), which SAP describes as BTPEA's predecessor, and pay-as-you-go.

Both models can coexist, in separate global accounts or in the same one, but you cannot mix more than one consumption flavour in the same global account. That rule shapes the account design before it shapes the bill.

BTPEA, CPEA and pay-as-you-go compared

BTPEA: a prepaid investment in cloud credits for the contract duration, with an annual commitment to consume BTP services and a minimum investment entry. It is billed annually in advance; consumption is deducted monthly from the credit balance, shown on a monthly statement; usage beyond the credits is billed in arrears at list price. Volume-based discounts are available, and credits can be topped up at any time to avoid overage.

CPEA: the older prepaid agreement, still in place on existing accounts. SAP lists a separate service catalogue for CPEA services on existing agreements, so check whether a service you need is in it.

Pay-as-you-go: no upfront cost, no minimum usage and no annual commitment. You are billed monthly in arrears for the services you use; the contract auto-renews every three months; and service charges are not discountable.

The trade-off is plain. Pay-as-you-go buys flexibility at list price; BTPEA buys a discount with a commitment you must consume.

Decision table: which model fits which situation

Proof of concept, unknown volumes — Model: pay-as-you-go · Why: no minimum, no commitment; accept list price for the trial period.

Stable estate with known services and steady use — Model: subscription · Why: a fixed price per service, predictable for finance.

Growing, varied use across many services — Model: BTPEA · Why: one credit pool, volume discounts; size the commitment to measured consumption.

Existing CPEA contract — Model: stay or move at renewal · Why: check the CPEA service catalogue for the services the roadmap needs.

Learning and prototyping on a consumption account — Model: free service plans · Why: free tier plans are added to consumption-based contracts, within technical limits and without an SLA.

Where the real numbers are, and how to estimate

SAP does not print a platform price because there is none to print: each service has its own metric and price. The SAP Discovery Center service catalogue carries, per service, a pricing tab where you compare plans and add them to the estimator, which then totals a service estimate.

A reliable estimate follows three steps. List the services the architecture really needs, with their metric, such as capacity units, instances, gigabytes or requests. Read each plan's metric and list price in the Discovery Center, in the currency and region of the contract. Then model the commitment: under BTPEA, the annual credit you are confident of consuming, with overage priced at list.

For AI, two meters coexist. Custom AI on SAP AI Core and models called through the generative AI hub are metered in capacity units against the BTP contract. SAP's Premium AI, such as Joule Agents, is paid in AI Units, a separate pool. A BTP estimate that includes Joule Agents is missing that second line.

Free tier, trial, and the bill nobody expected

Free service plans are added automatically to consumption-based contracts, subject to the model's availability in your country or region. SAP's own documentation names CPEA and pay-as-you-go in its scope section while listing BTPEA among the flavours, so confirm with SAP for a BTPEA account. Free plans are limited in scope and capacity, carry community support only and no SLA, and once a service hits its technical limit you must move to a paid plan; you cannot switch back from paid to free.

The classic surprise on a consumption account is an instance left running. Under pay-as-you-go it arrives as a monthly bill in arrears; under BTPEA it eats into credits and, once they are gone, is billed at list price. Assign quotas per subaccount and review the monthly statement.

What SAP TechEd 2026 means for BTP budgets

At TechEd on 27 October 2026 SAP positioned BTP and Joule Studio as the build layer for agents. Running custom agents on the SAP-managed Joule Studio runtime is free until December 2026 for select customers; afterwards, custom-built AI is billed on consumption through the BTP commercial model, so the 2027 BTP commitment should already carry an agent line. The agent gateway for third-party agents is generally available.

For the agent side read the Joule Studio pricing guide; for SAP's own AI, the SAP Joule pricing and AI Units guides.

What we cannot assert

SAP publishes per-service list prices in the Discovery Center but no BTPEA minimum entry amount, no discount curve and no CPEA end date in the sources we read. SAP's free-tier documentation is internally inconsistent on whether BTPEA accounts are in scope. We quote no currency figure: prices vary by service, region and contract.

Frequently asked

How much does SAP BTP cost?

There is no single BTP price. Each service has its own metric and list price in the SAP Discovery Center, and the effective price depends on the commercial model: a fixed subscription, or consumption under BTPEA, CPEA or pay-as-you-go.

What is the difference between BTPEA and pay-as-you-go?

BTPEA is prepaid cloud credits with an annual commitment and a minimum entry, billed annually in advance, with volume discounts and overage at list price. Pay-as-you-go has no upfront cost or commitment, is billed monthly in arrears and is not discountable.

Is CPEA still available?

SAP describes CPEA as the predecessor of BTPEA and keeps a service catalogue for CPEA services on existing agreements. For a new contract, the consumption options SAP leads with are BTPEA and pay-as-you-go.

Is there a free SAP BTP tier?

Yes. Free service plans are added to consumption-based contracts, where the model is available in your region. They are technically limited, have no SLA, and a service that reaches its limit must move to a paid plan.

Engage the editor

This guide is written by Cédric Mary, SAP AI & Analytics Architect & Team Lead. 27 years of SAP — Datasphere, Business Data Cloud, SAC Planning, Joule. Freelance or permanent · Hybrid / remote · Anywhere in EMEA.

Profile and contact

What this page is built on

SAP AI Foundation on SAP BTP — the three-layer map
SAP AI Units & the SAP Business AI Commercial Model
Commercial models, SAP BTP documentation (SAP)
SAP BTPEA basics, SAP BTP onboarding guide (SAP)
Using free service plans, SAP BTP documentation (SAP)
SAP Discovery Center service catalogue and estimator (SAP)
SAP Empowers AI Developers to Build What Matters (SAP News, 27 October 2026)