SAP Business Technology Platform (BTP) sells through two commercial models: CPEA (Cloud Platform Enterprise Agreement, a consumption commit at 12 to 28 percent discount) and Subscription (fixed-term per-service pricing). Integration Suite lists at $2,500 per tenant per month. Build Apps lists $15 to $30 per user per month. AI Foundation runs $0.005 to $0.04 per inference. CPEA discount math improves with commit size but accounts for 18 percent of unused credit on average across customer renewals. This page is the 2026 BTP pricing reference: per-service rates, CPEA mechanics, the free tier, and the levers that reduce overspend.
Inside This Pricing Guide
- SAP BTP list pricing 2026
- CPEA consumption model explained
- Subscription model for high-volume services
- Free tier: what's actually included
- Integration Suite pricing
- Build Apps, Build Process Automation, Build Code
- Datasphere and Analytics Cloud overlap
- AI Foundation and AI Core
- Discount math: 12 to 28 percent off list
- CFP credit migration
- Where 18 percent of CPEA evaporates
- Negotiation levers
SAP BTP list pricing 2026
BTP is not a single product. It is a catalogue of 95-plus services covering integration, application development, automation, data, analytics, and AI. Pricing is published per service in SAP's BTP catalogue. The 2026 reference rates for the high-volume services:
| Service | Unit | List rate |
|---|---|---|
| Integration Suite | Per tenant per month | $2,500 (Base), $5,000 (Premium) |
| Integration Suite (message-based) | Per million messages | $1,800 to $3,200 |
| Build Apps (low-code) | Per user per month | $15 (Citizen), $30 (Pro) |
| Build Process Automation | Per automated process per month | $28 to $46 |
| Build Code (developer) | Per developer per month | $59 to $89 |
| Datasphere | Per Block (8 GB memory + 16 vCPU) | $3,200 per month |
| SAP Analytics Cloud (Business Intelligence) | Per user per month | $28 to $108 |
| AI Foundation | Per 1,000 inferences (varies by model) | $0.005 to $0.04 per inference |
| AI Core | Per compute unit per hour | $0.78 to $4.20 |
| HANA Cloud (Database) | Per Block (32 GB + 4 vCPU) | $1,800 per month |
List is the published catalogue rate. The CPEA model applies a discount against list in exchange for an annual consumption commit. Subscription model applies a different (typically deeper) discount in exchange for a fixed-term, fixed-quantity commit per service.
CPEA consumption model explained
The Cloud Platform Enterprise Agreement is BTP's consumption commit model. The customer commits to an annual consumption value in BTP currency (US dollars or local currency equivalent). SAP debits actual service consumption against the commit at list rate, minus the CPEA discount. Unused commit at the end of the contract year is forfeited.
CPEA discount tiers as of 2026:
| Annual CPEA commit | Discount versus list | Term |
|---|---|---|
| $50K to $150K | 12 percent | 1 to 3 years |
| $150K to $500K | 15 to 18 percent | 1 to 3 years |
| $500K to $1.5M | 18 to 22 percent | 2 to 3 years |
| $1.5M to $5M | 22 to 26 percent | 3 years |
| $5M+ | 26 to 28 percent (custom) | 3 to 5 years |
The CPEA discount is meaningful at scale. The trap is the use-it-or-lose-it mechanic at year-end. Customers who commit aggressively to reach a higher discount tier and then under-consume the commit pay the full commit value with no rebate.
Subscription model for high-volume services
The Subscription model is the alternative to CPEA. Customers pay a fixed quarterly fee for a specified quantity of a specified service. The discount versus list is typically 18 to 35 percent at enterprise volume, but the commit is per-service and inflexible (you cannot shift unused Integration Suite capacity to AI Foundation).
Subscription is the right model for predictable, steady-state services. CPEA is the right model for variable or experimental consumption. A typical enterprise BTP deployment uses Subscription for Integration Suite and HANA Cloud (predictable), CPEA for AI Foundation and Build (variable).
| Workload pattern | Recommended commercial model | Reasoning |
|---|---|---|
| Steady-state Integration Suite (1 tenant, predictable message volume) | Subscription | Deeper discount; predictable cost. |
| Variable AI Foundation usage (developer experimentation) | CPEA | No service-specific commit; flexible consumption. |
| Build Apps citizen-developer rollout (uncertain user count) | CPEA | Scale up and down without re-papering. |
| HANA Cloud production database (steady block count) | Subscription | Reservation-style discount on steady consumption. |
| Multi-service developer platform (mixed services) | CPEA | Single commit covers the catalogue. |
Free tier: what's actually included
SAP BTP offers a free tier under the Trial and Free programs. The free tier includes limited capacity on most BTP services and is intended for evaluation and developer experimentation. The boundaries:
- Integration Suite: 500K free messages per month (Trial only).
- Build Apps: 1 free citizen-developer seat per organisation.
- HANA Cloud: 1 free 8GB database for 90 days.
- Build Code: 1 free developer seat with limited compute.
- AI Foundation: $50 of free inference credit per organisation per month.
- Datasphere: 90-day trial, 1 block, expires.
The free tier is genuinely useful for proof-of-concept work and small-team developer onboarding. It is not a path to production. Free-tier services impose connection limits, performance caps, and 90-day expiry on Trial-flagged accounts.
Integration Suite pricing
Integration Suite is BTP's flagship service and the most common single line item. It encompasses Cloud Integration (formerly SAP CPI), API Management, Open Connectors, Event Mesh, and Integration Advisor.
Integration Suite is licensed two ways: per tenant (a fixed monthly fee for a logical integration environment) or per million messages (consumption-priced). Most enterprise customers run a per-tenant commitment with Premium edition, supplemented by message-based billing for high-volume integrations.
| Integration Suite tier | Per tenant per month | Included message volume | Overage rate |
|---|---|---|---|
| Base | $2,500 | 5M messages | $2,400 per million overage |
| Premium | $5,000 | 15M messages | $2,000 per million overage |
| Premium Plus (custom) | $8,500+ | 40M messages | $1,600 per million overage |
The overage rate is the negotiation lever. Standard contracts apply overage at list. Negotiated contracts cap overage at the included rate or 110 percent of the included rate.
Build Apps, Build Process Automation, Build Code
The Build suite is SAP's developer toolkit. Three sub-products with distinct pricing:
Build Apps is the low-code application builder (formerly AppGyver). Citizen-developer licence at $15 per user per month. Pro-developer licence at $30 per user per month. Both include published-app hosting on BTP. Build Apps is the lowest-cost path to citizen-developer rollout in the SAP ecosystem.
Build Process Automation is the workflow and RPA tool (formerly SAP Workflow Management plus Intelligent RPA). Priced per automated process: $28 to $46 per process per month. An automated process is a defined end-to-end workflow with a start trigger and a defined output.
Build Code is the pro-developer IDE plus deployment pipeline. $59 to $89 per developer per month, including BTP compute allocation for build pipelines.
| Build product | Use case fit | Per-user list |
|---|---|---|
| Build Apps (Citizen) | Departmental apps, low-code citizen developers | $15 |
| Build Apps (Pro) | Enterprise apps with integration depth | $30 |
| Build Process Automation | RPA and workflow orchestration | $28 to $46 per process |
| Build Code | Pro-developer Fiori, RAP, Java/Node services | $59 to $89 |
Datasphere and Analytics Cloud overlap
SAP Datasphere is the data warehouse and integration platform. SAP Analytics Cloud is the BI and planning tool. The two products overlap on data modelling and semantic layer. Customers routinely buy both and use one.
Datasphere lists at $3,200 per Block (8 GB memory + 16 vCPU) per month. An enterprise customer typically runs 3 to 8 Blocks, costing $115,000 to $310,000 per year.
Analytics Cloud lists at $28 to $108 per user per month depending on edition (Business Intelligence, Planning, or Enterprise Planning Bundle). A 500-user Analytics Cloud rollout costs $168,000 to $648,000 per year at list.
The negotiation lever: assess actual usage of Datasphere versus existing data warehouse (Snowflake, Databricks, BigQuery). If the existing warehouse handles the workload, Datasphere is unnecessary. If Datasphere is essential for SAP data extraction, Analytics Cloud may not be. Buying both is justified only when both are materially used.
Datasphere plus Analytics Cloud principle: 40 percent of customers with both products materially use only one. The other product runs at 10 to 20 percent utilisation and is shelfware. Audit actual usage before each renewal.
AI Foundation and AI Core
AI Foundation is the inference layer for SAP's generative AI capabilities. It is the engine behind Joule (the conversational AI assistant) and is increasingly used for custom AI workloads built by enterprise developers.
Pricing is per inference, priced by model class:
| Model class | Per 1,000 inferences (input + output tokens) | Use case |
|---|---|---|
| SAP-curated small models | $0.005 to $0.012 | Classification, simple summarisation |
| SAP-curated mid models | $0.015 to $0.028 | Document Q and A, structured generation |
| SAP-curated large models (Joule equivalent) | $0.028 to $0.04 | Complex conversational, long-context |
| Hyperscaler-routed (OpenAI, Anthropic) | List plus 15 to 30 percent margin | Bring-your-own-API-key alternative |
AI Core is the compute and training layer. Priced per compute unit per hour, with GPU-class differentiation. For most enterprise BTP customers, AI Foundation usage is meaningful and AI Core usage is minimal. AI Core matters for organisations actively training or fine-tuning models on SAP data.
For Joule pricing context, see SAP Joule AI Licensing. For the Microsoft AI comparison, see Microsoft 365 Copilot Pricing 2026 and Microsoft Copilot Licensing.
Discount math: 12 to 28 percent off list
The published CPEA discount tiers are the starting position. Negotiated CPEA discounts can extend 4 to 8 percentage points beyond the published tier when combined with a broader SAP commercial commitment (RISE conversion, S/4HANA expansion, multi-year renewal).
The discount lever interacts with the commit lever. A higher discount tier requires a larger commit. The right answer is the commit value that matches forecast consumption plus a 10 to 15 percent buffer, not the commit value that unlocks the next discount tier.
CFP credit migration
Customers with legacy SAP Cloud Platform Framework (CFP) credits can migrate them to BTP CPEA balance. The migration is one-to-one for unused CFP balance. The trap: the migration window is 90 days from contract anniversary. Unmigrated credits expire.
For customers with material CFP balances, the migration is a one-time recovery of $50K to $400K of pre-paid spend. Confirm the migration mechanic with SAP commercial in writing before the anniversary date.
Where 18 percent of CPEA evaporates
The 18 percent figure is the average unused CPEA commit across a sample of 35 enterprise BTP renewals. Three root causes:
Aspirational committing. The customer commits at the planned consumption level for year three of a three-year contract, not actual year-one consumption. Year-one and year-two under-consume.
Service catalogue drift. The customer commits expecting heavy AI Foundation use, then the AI initiative slows, but the CPEA commit is set. The commit value cannot redirect to other services that scaled instead.
Implementation delay. A planned Integration Suite rollout slips 6 months. The CPEA year-one consumption falls 35 percent below commit. The commit balance forfeits at year-end.
The structural fix is the commit-to-actual reset clause: a contractual right to reset the CPEA commit at the 12-month anniversary based on actual consumption, with no penalty. SAP grants this clause in 30 to 40 percent of enterprise CPEA negotiations.
Negotiation levers
Six levers move BTP pricing:
Right-sized CPEA commit. Forecast consumption plus 10 to 15 percent buffer, not aspirational consumption.
Commit-to-actual reset clause. Right to reduce CPEA commit at anniversary if actual consumption is materially below.
Service-by-service overage cap. Cap overage on Integration Suite messages and AI Foundation inferences at the included rate.
Subscription versus CPEA mix. Subscription for predictable services, CPEA for variable. Reduces unused-commit risk.
CFP credit migration. Recover unused legacy CFP balance at the 90-day anniversary window.
Datasphere plus Analytics Cloud rationalisation. Audit overlap, drop the under-used product at renewal.
Frequently asked questions about BTP pricing
What is the difference between CPEA and SAP Cloud Platform Framework (CFP)?
CFP is the legacy commercial framework for SAP Cloud Platform, pre-dating the rebrand to BTP. CFP customers paid for credits that could be spent across the catalogue. CPEA is the current consumption commit framework for BTP. Migration is one-to-one: unused CFP credits convert to CPEA balance at contract anniversary. The 90-day migration window is strict; unmigrated credits expire. Customers with material CFP balances should confirm the migration mechanic with SAP commercial in writing well before the anniversary date.
Is the BTP free tier sufficient for production workloads?
No. The free tier is for evaluation and developer experimentation. Free-tier Integration Suite is capped at 500,000 messages per month, well below production message volumes. Free-tier HANA Cloud is 90-day trial only. Free-tier Build Apps is one citizen-developer seat per organisation, not a team. Free-tier AI Foundation is $50 of inference credit per month. The free tier is genuinely useful for proof-of-concept and developer onboarding, and is not a production path.
How does Datasphere differ from Analytics Cloud?
Datasphere is the data warehouse and integration platform: it stores data, models it semantically, federates queries across sources. SAP Analytics Cloud is the visualisation, BI, and planning layer: it consumes data from Datasphere or other sources and presents it. The two products overlap on the semantic modelling layer, where both can define calculated measures and dimensions. The overlap is the source of the routine over-buying pattern, where customers license both and materially use one. The decision rule: if your existing data warehouse (Snowflake, Databricks, BigQuery) handles the storage and federation, Datasphere is not required, and Analytics Cloud can be evaluated against Tableau, Power BI, and Qlik on its own merit.
When does HANA Cloud beat HANA Enterprise perpetual on cost?
HANA Cloud subscription is competitive at small scale (under 200 GB) or for highly variable workloads. HANA Enterprise perpetual plus 22 percent maintenance is materially cheaper at scale (1 TB and above) and for stable workloads on a 4-to-7-year horizon. A 1 TB workload costs $1.09M over 5 years on perpetual, versus $3.45M on Cloud subscription. The crossover scale is approximately 350 to 500 GB depending on workload variability. For variable workloads with material scale-up and scale-down patterns, Cloud subscription's elasticity can outweigh the higher unit cost.
Can BTP services be paid per-month?
Subscription model BTP services bill quarterly. CPEA bills monthly or quarterly against actual consumption with the annual commit reconciled at year-end. Free-tier services have no billing. Pure month-to-month billing without an annual commit is rare and typically available only for very small CPEA commits (under $50,000 per year), where SAP commercial waives the multi-year requirement.
How does AI Foundation compare to OpenAI direct API for cost?
AI Foundation pricing for SAP-curated large models is in the range of $0.028 to $0.04 per 1,000 inferences (input plus output tokens). OpenAI direct API for GPT-4 class models prices similar at $0.03 to $0.06 per 1,000 input tokens and $0.06 to $0.12 per 1,000 output tokens (typical 2026 rates). For most enterprise workloads, the per-token cost is comparable. AI Foundation's advantage is integration with SAP data and Joule's enterprise capabilities. Direct API's advantage is model flexibility and avoiding the SAP commercial layer. The right answer depends on whether the workload genuinely needs SAP data context.
What happens to unused CPEA balance at year-end?
Standard CPEA contracts forfeit unused balance at contract year-end. There is no rollover, no rebate, no credit to next year's commit. This is the use-it-or-lose-it mechanic that produces the 18 percent unused-commit pattern. The negotiated protective clause is a balance carry-forward (often 10 to 15 percent of annual commit can roll forward 12 months) or a year-end consumption reset (right to apply unused balance to additional services beyond contracted scope). Both clauses are available in 30 to 45 percent of enterprise CPEA negotiations.
CFP to CPEA migration playbook
Customers carrying legacy SAP Cloud Platform Framework balances face a structured migration. The migration mechanics:
Step 1: balance inventory. Pull the current CFP balance from SAP for Me at least 120 days before contract anniversary. The balance is denominated in CFP credits. The credit-to-dollar conversion is documented in the original CFP agreement (typically $1 per credit but verify).
Step 2: consumption forecast. Model the planned BTP consumption for the next contract year. CPEA commit should match forecast plus 10 to 15 percent buffer. CFP balance reduces the net new CPEA commit by an equivalent amount.
Step 3: migration request. Submit the migration request through SAP for Me at least 60 days before contract anniversary. The request requires SAP commercial sign-off. Unmigrated balance at anniversary forfeits.
Step 4: post-migration validation. Confirm the migrated balance appears in CPEA accounting within 30 days of contract anniversary. Discrepancies require escalation to SAP licence management.
| CFP balance scenario | Recommended action |
|---|---|
| Material unused CFP balance ($100K+) | Migrate to CPEA immediately. Reduce next-year CPEA commit by the migrated amount. |
| Minor CFP balance (under $50K) | Consume in remaining CFP term if possible. Migrate residual. |
| CFP balance with no planned BTP consumption | Negotiate one-time refund or credit against other SAP commercial. Migration with no consumption forfeits at next anniversary. |
| CFP balance from acquired entity | Confirm migration eligibility with SAP commercial. Acquisitions sometimes carry restrictive credit terms. |
Closing position on BTP economics
BTP pricing is the most complex SAP commercial conversation in 2026. The catalogue of 95 services, the dual commercial models (CPEA and Subscription), the free-tier exceptions, the CFP migration overlay, and the AI Foundation pricing volatility combine to produce a contract surface that is difficult to model. The defensive position requires three disciplines.
First, consumption modelling. Customers who treat the BTP commit as a single annual number cannot manage it. Customers who model consumption by service, by month, against actual usage, identify the under-consumption pattern early enough to redirect or renegotiate.
Second, commit structure. The choice between CPEA and Subscription should be made service by service, not as a global decision. Predictable services belong in Subscription. Variable services belong in CPEA. Mixing the two structures produces the lowest total cost.
Third, anniversary discipline. The CPEA anniversary is the single commercial event each year where commit-to-actual reconciliation can trigger a renegotiation, where CFP migration must complete, and where the next year's commit is set. Customers who treat the anniversary as an administrative checkpoint pay the unused-commit forfeit. Customers who treat the anniversary as the annual BTP negotiation point recover the unused balance and right-size the next year.
For RISE bundling context, see SAP RISE versus GROW versus HEC and RISE Negotiation. For broader SAP commercial framework, see the SAP Licensing Complete Guide, the SAP Conversion Credits guide, and SAP vendor intelligence. To engage on a BTP commit review, see Software Licensing Advisory.