What is SAP BTP? The plain language buyer side explainer for 2026.

SAP Business Technology Platform, or SAP BTP, is the publisher's umbrella for everything that is not S/4HANA. The naming is confusing on purpose. The commercial model is a credit pool that runs down fast unless someone is watching. This is the plain language buyer side explainer.

SAP Business Technology Platform, or SAP BTP, is the term SAP uses for almost every cloud product that is not the S/4HANA ERP itself. Integration Suite, Build, Build Apps, Datasphere, Analytics Cloud, AI Core, AI Launchpad, and Joule are all BTP services.

The product is genuinely useful. The commercial model is a credit prepay that burns down fast when the BTP team scales out without central oversight. This explainer takes a buyer side view of what BTP is, how it bills, and where the leverage sits.

Read the related SAP knowledge hub, the BTP credit cost optimization guide, and the SAP advisory practice for the wider context.

What SAP BTP is

The product positioning

BTP is the umbrella brand for the SAP cloud platform. It includes the developer tooling, the integration runtime, the database and data layer, the analytics, the AI tooling, and the agent framework. SAP positions it as the operating system for the wider SAP estate.

The historical name was SAP Cloud Platform. The rebrand to Business Technology Platform happened in 2021, alongside the consolidation of the runtime portfolio.

The component services

• Integration Suite. The SAP integration runtime, including Cloud Integration, API Management, Event Mesh, and Open Connectors.
• Build. The application development platform including Build Apps for low code and Build Process Automation.
• Datasphere. The data fabric layer for federated data across SAP and non SAP sources.
• Analytics Cloud. The dashboarding, planning, and predictive analytics tooling.
• AI Core and AI Launchpad. The model lifecycle and AI service hosting layer.
• Joule. The SAP generative AI copilot that sits on top of BTP services.

How it gets used

BTP shows up in three patterns. The first is the side car around S/4HANA where customers build extensions and integrations to keep the core clean. The second is the data and analytics overlay across the wider enterprise. The third is the agent platform for the new generation of process automation.

The commercial model

Cloud Platform Enterprise Agreement

The default commercial model is the Cloud Platform Enterprise Agreement, or CPEA. The customer prepays an annual credit pool. The pool burns down as services consume against the published rate card.

The credit is denominated in a notional cloud credit. Each service consumes credits at a published rate per metric. Integration Suite credits one rate, Build credits another, AI Core credits a third, and so on.

Pay As You Go

• Term. Pay as you go is billed monthly against actual consumption with no upfront commit.
• Rate. The unit rate sits above CPEA by twenty to thirty five percent on most services.
• Use case. Pay as you go suits true short term spikes and proof of concept work.
• Risk. The unbounded run rate can scale into six and seven figures fast on a hot AI workload.

Subscription

The older subscription model still exists for select services. The subscription buys a fixed quantity of a specific service for a fixed term. Subscription is simpler but inflexible.

The buyer side preference is CPEA for the breadth and Pay As You Go for the spikes, with subscription reserved for the few services where the metric is well understood and stable.

How credits actually burn

The service rate card

Every BTP service has a rate card. Integration Suite charges per message or per API call. Build Apps charges per user. Build Process Automation charges per process automation unit. AI Core charges per training hour or per inference.

The rate card is published by SAP and updated periodically. Buyer side teams should pull the current rate card before any service goes live, not after.

Cross service conversion

Credits are fungible across services. A credit purchased for Integration Suite can be consumed by Build, Analytics Cloud, or AI Core. The fungibility is helpful and dangerous. Helpful because the portfolio can shift over the term. Dangerous because the project team can rotate spend into the AI workload before procurement notices.

Overage and renewal

• Overage. Once the annual credit is exhausted, additional consumption runs at the higher Pay As You Go list rate.
• True up. The annual true up reconciles the actual consumption against the prepaid pool.
• Renewal sizing. SAP commonly proposes the next term sized at actual consumption plus a forecast uplift.
• Burn rate alerts. The BTP cockpit can trigger alerts at customer defined thresholds.

Where the waste lives

Dormant services

The classic source of BTP waste is the service that was provisioned for a project, used for two months, and then forgotten. The credit burn continued. The project sponsor moved on. Nobody decommissioned.

A quarterly BTP service inventory catches this. The cockpit lists every active subaccount and the services attached. Anything with no recent activity is a candidate for decommission or a tier downgrade.

Oversized runtime

• Integration Suite tenants. Dev and QA tenants run at the same tier as production by default. Tier them down.
• Analytics Cloud agents. The agent count drifts up with each new use case. Audit and consolidate.
• AI Core compute. GPU resources stay attached after the training job completes. Detach by policy.
• Build runtime. Idle Build runtime continues to consume capacity credits. Auto suspend on inactivity.

AI workload explosion

Joule, AI Launchpad, and the wider AI Core service can scale credit consumption faster than the procurement cycle. A demo agent that goes into production at scale can multiply the annual burn rate inside a quarter.

BTP is sold to the BTP team, not to the central licensing office. The fungible credit and the cross service burn are the leading source of unmanaged spend on the SAP estate in 2026.

Buyer side moves at the BTP renewal

Top six moves

• Right size the CPEA. Size the pool against the documented twelve month burn, not the forecast plus padding.
• Service portfolio audit. Inventory every active service, tier the dev and QA, retire the dormant.
• Burn rate dashboard. Set monthly burn rate alerts in the BTP cockpit with a defined escalation path to procurement.
• Renewal escalator cap. Cap the year on year credit price uplift against a defensible CPI proxy.
• AI workload separation. Carve AI Core, AI Launchpad, and Joule into a separate CPEA pool with its own governance.
• Multi year discount. Trade a longer term commit for a discount only when the burn forecast is genuinely stable.

The mid term operating discipline

The renewal night discussion is not where the value sits. The value sits in the monthly burn rate review and the quarterly service portfolio audit.

Pull in the SAP advisory practice for the joint renewal posture and the operating cadence that holds the BTP team accountable to the credit pool budget.

BTP and the wider SAP estate

Relationship with S/4HANA

BTP sits alongside S/4HANA. The clean core principle says extensions go on BTP, not in S/4. The platform is the destination for any custom logic and any integration to non SAP systems.

Read the related SAP RISE pillar for the wider RISE commercial framework that bundles BTP credit with S/4HANA Cloud Private Edition.

RISE and BTP

RISE With SAP includes a bundled CPEA credit pool. The bundle simplifies the procurement but blurs the visibility. The renewal posture should still treat the bundled BTP as a separable component for benchmarking purposes.

What to do next

1. Inventory every active BTP service across every subaccount.
2. Pull the last twelve months of credit consumption from the BTP cockpit and tier by service.
3. Identify dormant services and dev or QA tiers that can be downgraded or retired.
4. Set monthly burn rate alerts at fifty, seventy five, and ninety percent of the pool.
5. Right size the next CPEA against actuals, not against forecast plus padding.
6. Carve any AI workload into a separate CPEA pool with its own governance.
7. Cap the renewal escalator at a defensible CPI proxy in the contract.
8. Pull in the SAP advisory practice for the renewal negotiation.

Frequently asked questions

What does BTP stand for in SAP?

BTP stands for Business Technology Platform. It is the SAP umbrella brand for the cloud services that surround S/4HANA, including integration, application development, automation, data, analytics, and AI.

How is BTP priced?

The default model is the Cloud Platform Enterprise Agreement, or CPEA, which prepays an annual credit pool. Credits are fungible across services. Pay As You Go and Subscription models also exist for specific needs.

What happens to unused BTP credits?

Unused CPEA credits do not roll into the next term. The renewal should be sized against actual consumption, not against the prior commit, to avoid paying for credits that will not be used.

What is the difference between BTP and SAP Cloud Platform?

BTP is the rebranded name for what used to be SAP Cloud Platform. SAP consolidated the runtime and analytics portfolios under the BTP umbrella in 2021.

Is Joule part of BTP?

Yes. Joule is the SAP generative AI copilot. It runs on AI Core and surfaces in S/4HANA and other SAP products. The underlying compute and inference consumes BTP credits.

How does BTP relate to RISE With SAP?

RISE With SAP includes a bundled CPEA credit allocation alongside S/4HANA Cloud Private Edition. The bundle simplifies procurement but should still be benchmarked as a separable component at renewal.

What is the biggest source of BTP waste?

Dormant services that continue to burn credits, oversized dev and QA tiers, idle runtime that does not auto suspend, and AI workloads that scale faster than the procurement cycle. A quarterly service portfolio audit catches all four.

How do we benchmark BTP pricing?

Pull the current SAP rate card, compare the consumption pattern against the SAP knowledge hub reference rates, and model the renewal under both CPEA and Pay As You Go to surface the true unit economics.