What Is SAP BTP? The Platform Behind SAP's Cloud Strategy

SAP Business Technology Platform (BTP) is the technology layer between SAP’s business applications (S/4HANA, the SAP CX suite, SuccessFactors) and the infrastructure they run on. It covers integration, extension, data, analytics, AI and application runtimes on one platform, under one account model and one security concept.

If you run any SAP cloud product, BTP is already part of your landscape. The practical question is how much of it you need.

TL;DR: SAP BTP is the platform SAP uses to connect, extend and add intelligence to its cloud applications. It bundles integration (Integration Suite), development (CAP, SAP Build), data (HANA Cloud), AI and runtimes (Cloud Foundry, Kyma). You need it as soon as you connect SAP CX to S/4HANA, build clean-core extensions or integrate non-SAP systems; a single SAP product without integrations can live without it.

What problem does SAP BTP solve?

Before BTP, an SAP landscape needed a separate product for every technical capability: SAP PI/PO for integration, an on-premise HANA for data, separate analytics tools, and custom ABAP code inside the ERP for extensions. Each had its own security model, its own administration and its own update cycle. A pattern we still see in older landscapes: several middleware products side by side, different security models, and nobody who can explain the whole picture.

BTP consolidates these capabilities on one platform:

• One administration interface: the BTP cockpit
• One security concept: SAP Authorization and Trust Management (XSUAA) connected to your identity provider
• One extension framework: the SAP Cloud Application Programming Model (CAP)
• One integration approach: SAP Integration Suite
• One data layer: SAP HANA Cloud, with SAP Datasphere now a component of SAP Business Data Cloud

BTP does not replace everything overnight. It gives you one platform to invest in instead of a collection of disconnected tools. SAP took this a step further at Sapphire in May 2026, when it announced that the new SAP Business AI Platform unifies SAP Business Technology Platform, SAP Business Data Cloud and SAP Business AI into a single, governed environment.

What services does SAP BTP include?

BTP is a catalogue of services that grows with every release; the SAP Discovery Center lists them with plans and regions. The services that matter most in practice fall into five groups.

Integration Suite. Connects SAP to SAP and SAP to third-party systems: Cloud Integration with prebuilt integration packages, API Management, Integration Advisor for B2B formats and event-driven messaging. Integration is usually the first thing that needs attention when you move to the cloud, which is why most BTP footprints start here. At Meier Tobler, Spadoom built a central SAP Integration Suite platform that replaced PI/PO and now processes more than one million messages a month in real time.

SAP HANA Cloud and the data layer. HANA Cloud provides in-memory database services, for example as persistence for CAP applications. Cross-system analytics has moved to SAP Business Data Cloud, of which SAP Datasphere is now a component. Federation lets you query SAP and non-SAP sources without copying everything into a central warehouse.

SAP Build and SAP Business Application Studio. Low-code tools for business users plus pro-code tools for developers. Build process automations, apps and workflow extensions, all deployed on BTP. Low-code works well for approval workflows and simple data-entry forms; for complex business logic we still prefer CAP.

SAP AI Core and Joule. AI Core provides the infrastructure to run and serve AI models, including access to large language models through the generative AI hub. Joule is the AI assistant embedded across SAP applications.

Application runtimes. The Cloud Foundry environment and Kyma (Kubernetes-based) run custom applications in Node.js, Java, Python and other languages, and the ABAP environment runs cloud ABAP. This is where your extensions execute. We run our own CX extensions on Cloud Foundry.

How does BTP fit into an SAP landscape?

A typical SAP cloud landscape has three layers:

1. SAP S/4HANA (Public or Private Cloud) runs the ERP: finance, procurement, logistics, manufacturing.
2. The SAP CX suite (Sales Cloud V2, Service Cloud V2, Commerce Cloud) runs the customer-facing processes.
3. SAP BTP connects them and hosts the extensions.

In our CX and ERP projects, BTP typically does the following:

• Integration Suite synchronises master data between S/4HANA and the CX applications (customers, products, prices).
• SAP Event Mesh, or SAP Integration Suite, advanced event mesh for higher volumes, distributes business events (order created, invoice posted, case resolved) across systems.
• CAP extensions on Cloud Foundry add business logic that does not belong in the standard products.
• The Destination and Connectivity services manage connections to external APIs and, via the Cloud Connector, to on-premise systems.
• Authorization and Trust Management handles authentication and authorisation across BTP services.

The clean-core principle governs this architecture: keep the SAP applications standard, build side-by-side extensions on BTP and connect them through released APIs. SAP can then update its products on its own schedule without breaking your customisations. How that looks for the ERP is described in our post on extending S/4HANA Public Cloud with BTP and Cloud Foundry. Because we deliver the ERP core and the CX stack with one team, the BTP layer between them is designed once, not negotiated between two partners; the ERP and CRM partner guide explains why that seam matters.

What does BTP cost?

BTP is licensed through cloud credits or subscriptions. With the consumption-based models, you commit to a volume of credits in your SAP contract (standalone or as part of RISE or GROW with SAP), and services consume those credits based on usage: API calls, compute hours, storage, users.

What you need to know about costs:

• Some services are typically included. Basic services such as Destination and Connectivity usually come without additional credit consumption; check your contract for the exact scope.
• Other services consume credits. HANA Cloud, Integration Suite, AI Core and the Cloud Foundry runtime are charged by usage.
• The plan matters. Each service has several plans (free, standard, premium and others). Development environments should use free or small plans; production uses the plans with the service levels you need.
• Monitor consumption in the cockpit. The usage views in the global account show consumption per service and per subaccount. Review them monthly.

A common mistake we see: services in development subaccounts provisioned with production-grade plans, and consumption ends up far above the estimate. It is easy to fix once you spot it, but it gets expensive if nobody looks.

When do you need BTP, and when is it optional?

You need BTP when you:

• Connect the SAP CX applications to SAP S/4HANA with custom mappings or non-standard scenarios (Integration Suite is the standard approach)
• Build custom extensions for Sales Cloud V2 or Service Cloud V2 (CAP on Cloud Foundry)
• Extend SAP Commerce Cloud side-by-side, for example with CAP services or on Kyma, instead of customising the core
• Implement event-driven processes across SAP and non-SAP applications
• Replace an on-premise middleware such as SAP PI/PO

BTP can be optional when you:

• Run a single SAP product with no integrations (rare, but it happens)
• Use only SAP Engagement Cloud (formerly SAP Emarsys) for marketing automation, which brings its own integration options
• Cover all integration needs with standard SAP-to-SAP connectors

In practice, most SAP cloud projects beyond the simplest scope need at least Integration Suite and one BTP runtime. The question is usually how much BTP, not whether. If you want to see what that means for your landscape, our work as an SAP BTP partner in Switzerland starts with exactly that scoping, and our overview of SAP BTP development partners in Switzerland shows what to look for in a partner. The SAP BTP documentation is the reference for every service mentioned here.

FAQ

What is the difference between SAP BTP and SAP Cloud Platform?

SAP BTP is the successor of SAP Cloud Platform (SCP). SAP renamed and expanded it in January 2021, so older documentation that mentions SCP describes what is now BTP.

Does SAP BTP require S/4HANA?

No. BTP works with any SAP cloud application and with non-SAP systems. S/4HANA projects are a very common use case, because clean-core extensions and integrations for the ERP are built on BTP, but a Sales Cloud V2 extension or an integration between two non-SAP systems runs on BTP just as well.

Can SAP BTP run on any cloud provider?

BTP runs on several hyperscalers, including AWS, Microsoft Azure and Google Cloud, plus SAP’s own data centres for some services. You choose provider and region per subaccount, and service availability differs by region, so check the SAP Discovery Center before you commit.

How long does it take to set up SAP BTP?

Creating a global account and the first subaccount takes hours. Configuring Integration Suite, setting up the Cloud Foundry environment with identity and transport, and deploying a first extension typically takes an experienced team two to four weeks.

Is SAP BTP included with RISE with SAP?

RISE with SAP and GROW with SAP contracts usually include a BTP credit allocation, but the amount and the services it covers depend on your contract. It is usually enough to start with integration and a first extension; extensive custom development often needs additional credits.