If you are evaluating SAP Business Technology Platform, the first practical question is always the same: where will my code actually run? This comprehensive guide to SAP BTP environments answers exactly that. We walk through the three environments available today — Cloud Foundry, Kyma, and the ABAP environment — explain what happened to Neo, show how the commercial models work, and cover what SAP added to the platform in 2025 and 2026, from the SAP Build family to Joule.
A quick note on names before we start: SAP BTP was called SAP Cloud Platform until January 2021, and you will still meet the old name in older documentation and even in one of the current pricing models. In this guide, everything refers to SAP BTP as it stands in 2026.
For the architecture decision behind those environments, use Cloud Foundry, Kyma and the Neo retirement clock to match the runtime to the integration obligation.
First, what is an SAP BTP environment?
SAP BTP offers distinct development zones, called environments. These environments are cloud-based runtimes where you build, deploy, and operate your applications. Each environment comes pre-loaded with the tools, technologies, and programming models suited to a particular kind of development work, so you can pick the right one for the software you are building.
All of today’s environments run on SAP BTP’s multi-cloud foundation, which has been the default for new customers since 2020. That means you choose the hyperscaler infrastructure underneath — AWS, Microsoft Azure, or Google Cloud — and the region that fits your data-residency requirements, while SAP manages the platform layer.
There are three environments available in SAP BTP today:
- Cloud Foundry — the polyglot, cloud-native application runtime and the most widely used of the three
- Kyma — a fully managed Kubernetes runtime, now built around modular components
- ABAP environment — ABAP Cloud as a platform-as-a-service, also known by its project name, Steampunk
And one environment you should not plan around: Neo, which is in managed sunset. We cover it below, because knowing what to do about Neo is now part of any serious SAP BTP decision.
Cloud Foundry: the default home for cloud applications on SAP BTP
The Cloud Foundry environment is SAP BTP’s one-stop shop for building modern cloud applications, and it remains the most-used runtime on the platform. It is built on the open-source Cloud Foundry platform, which translates into genuine freedom of choice: a wide range of runtimes, programming languages, libraries, and services, all inside a managed, secure environment.
Cloud Foundry is where most side-by-side extensions live. It is the natural home for applications built with the SAP Cloud Application Programming Model (CAP), and it is also the migration target SAP recommends for most workloads leaving Neo.
Need a concrete example? Imagine building a web application on Cloud Foundry. You can develop it in Node.js or with CAP, connect it to an SAP HANA Cloud database, and surface real-time sales data to your users — all without provisioning or patching a single server yourself.
Choose Cloud Foundry when your team builds in JavaScript, Java, Python, or Go, when you want the shortest path from code to a running app, and when you do not need direct control over container orchestration.
The ABAP environment: ABAP Cloud in the modern era
The ABAP environment (also known as SAP BTP ABAP environment, or by its original project name Steampunk) brings the ABAP platform to the cloud as a true platform-as-a-service. For organizations with deep ABAP expertise, this is the environment that lets those skills carry forward.
Here is how the ABAP environment empowers your team:
- Leverage existing skills: your ABAP developers keep working in the language they know, now against cloud-released APIs.
- Extend your core systems: build extensions for SAP S/4HANA Cloud and other ABAP-based products without modifying them.
- Build for the future: develop brand-new cloud applications using ABAP Cloud, the modern, cloud-ready flavor of the language.
- Modernize your codebase: transform existing custom ABAP code into upgrade-safe cloud extensions.
Technically, the environment runs on the same ABAP platform cloud release that powers SAP S/4HANA Cloud, and development follows the ABAP RESTful Application Programming Model (RAP) with SAP Fiori and Core Data Services (CDS). Development happens in modern tooling — and since 2025, AI assistance has arrived here too: Joule’s capabilities for developers extend to ABAP Cloud, helping generate and explain code as part of SAP’s broader push to put AI across its development stack.
Kyma: fully managed Kubernetes, now modular
In its simplest form, Kyma is a fully managed Kubernetes runtime based on the open-source Kyma project. It combines Kubernetes with a curated set of tools so developers can build, run, and maintain secure, scalable, cloud-native applications — with the cluster lifecycle handled by SAP on the hyperscaler of your choice.
The important change since this guide was first written: Kyma has moved to a modular architecture. Instead of shipping one fixed bundle of components, Kyma now lets you enable only the modules your workload actually needs — for example, the KEDA module for event-driven autoscaling, or modules for serverless functions, eventing, observability, and API exposure. That keeps clusters lean and reduces the surface you operate.
Key benefits of the Kyma environment:
- A managed Kubernetes cluster without the operational burden: SAP runs the cluster; your team focuses on applications.
- Current Kubernetes capabilities: access to the up-to-date Kubernetes ecosystem for container orchestration.
- À-la-carte platform features: enable serverless, eventing, observability, service mesh, and connectivity modules only where you need them.
- Native SAP integration: Kyma connects cleanly to SAP BTP services and to systems such as SAP S/4HANA and SAP SuccessFactors, making it a strong choice for event-driven extensions of your SAP landscape.
Choose Kyma when your team is container-native, needs Kubernetes-level control, or is building microservice and event-driven architectures around the SAP core.
What about Neo? A migration deadline, not an option
Older guides list a fourth environment: Neo, SAP’s original proprietary runtime from the SAP Cloud Platform era. Treat Neo as history in the making. SAP announced its sunset in June 2023, and the Neo environment is scheduled for final decommissioning on December 31, 2028 (subject to individual contract terms). New features and innovations ship only to the multi-cloud environments — Cloud Foundry, Kyma, and ABAP — and Neo contracts can be renewed only up to the end-of-life date.
The practical implications:
- Never start a new project on Neo. The go-forward set is Cloud Foundry, Kyma, and the ABAP environment.
- If you run Neo workloads today, plan the migration now. Most Neo applications and services map to the Cloud Foundry environment on the multi-cloud foundation; the earlier you assess, the more room you have to re-architect where it pays off rather than porting under deadline pressure.
Can you mix environments? Yes — in one subaccount
SAP BTP is organized into global accounts and subaccounts, and a single subaccount can host multiple environments at once — for example, Cloud Foundry and Kyma side by side. Users, authorizations, and entitlements are managed once per subaccount, and shared services such as SAP HANA Cloud can be consumed from both runtimes. A common pattern is a CAP application on Cloud Foundry working alongside event-driven microservices on Kyma, both talking to the same HANA Cloud instance.
This flexibility means the environment question is rarely either/or. Teams pick the runtime that fits each workload and let SAP BTP handle the shared plumbing. (Note that multi-environment subaccounts do not apply to Neo — one more reason it belongs in your migration plan, not your architecture.)
How SAP BTP is priced: the commercial models
Understanding the runtimes is half the decision; the other half is commercial. SAP BTP offers two umbrella models today:
- Consumption-based, in three flavors:
- SAP BTP Enterprise Agreement (BTPEA) — the newer evolution of CPEA and the model SAP leads with for new customers. Importantly, newly released SAP BTP services are added to the BTPEA catalog only.
- Cloud Platform Enterprise Agreement (CPEA) — the predecessor model (still carrying the platform’s old name). Existing CPEA customers can keep renewing, but its service scope is frozen; migration to BTPEA typically happens at renewal.
- Pay-As-You-Go — no upfront commitment, billed monthly in arrears for what you actually use, with free-tier service plans available. Ideal for proofs of concept, pilots, and small-scale applications; there are no entry or volume discounts.
- Subscription-based — a fixed cost for named services, regardless of how much you consume.
Consumption and subscription models can coexist in one global account, but you cannot combine two consumption flavors in the same global account. A useful on-ramp: free-tier plans run under commercial accounts, so a team can start free on Pay-As-You-Go and upgrade service plans later without re-platforming.
What’s new on SAP BTP in 2025–2026
The SAP Build family and Joule for developers
Development on SAP BTP now centers on the SAP Build family: SAP Build Apps (low-code applications), SAP Build Process Automation (workflows and automation — the successor to the retired SAP Workflow Management), SAP Build Code (pro-code, CAP-based development), and SAP Build Work Zone (business sites and digital workplaces). Joule Studio, part of SAP Build, adds the ability to build custom AI skills and agents on the platform.
Joule for Developers, announced in March 2025, threads AI assistance through this tooling — across SAP Build Code, ABAP Cloud, SAP Build Apps, and SAP Build Process Automation — so both low-code builders and professional developers get generation, explanation, and automation help inside their normal workflow.
One platform under a bigger umbrella
SAP has also been consolidating its platform story. At TechEd in November 2025, SAP brought SAP BTP, SAP Business Data Cloud, and its AI Foundation together into a unified architecture, adding agent-ready capabilities such as support for the Model Context Protocol (MCP) in SAP HANA Cloud and an MCP gateway in SAP Integration Suite. At Sapphire in May 2026, this consolidation got a name: the SAP Business AI Platform, an umbrella spanning SAP BTP, SAP Business Data Cloud, and SAP Business AI.
To be clear: SAP BTP has not been renamed or discontinued. It remains the foundation layer of that umbrella, and everything in this guide — environments, subaccounts, commercial models — continues to apply. What the umbrella signals is direction: the platform you extend on is the same platform SAP’s AI capabilities are built into.
SAP BTP and the clean core
Why does all of this matter strategically? Because SAP BTP is the canonical home for side-by-side extensions — custom logic that lives next to your ERP rather than inside it. In 2025 SAP replaced its old three-tier extensibility model with a four-level clean core level concept (Levels A through D), grading extensions by upgrade safety and their use of released APIs. Side-by-side extensions built on SAP BTP with the SAP Build options — whether ABAP Cloud, CAP, or low-code — sit at Level A, the cleanest level, alongside properly built on-stack ABAP Cloud extensions.
In plain terms: properly designed extensions in these environments — built on released APIs and clean-core practices — keep your S/4HANA core clean and your upgrades predictable. If you are weighing RISE with SAP versus GROW with SAP, this is the extensibility strategy both paths assume.
Choosing the right SAP BTP environment
A quick decision summary:
- Cloud Foundry — cloud-native web applications, CAP-based side-by-side extensions, polyglot teams, fastest path to production.
- Kyma — Kubernetes-native teams, microservices, event-driven extensions, workloads needing container-level control.
- ABAP environment — ABAP-skilled teams, upgrade-safe extensions to S/4HANA Cloud, modernizing custom ABAP for the cloud.
- Neo — no new projects; migrate existing workloads before December 31, 2028.
And remember the environments are composable: one subaccount can run Cloud Foundry and Kyma together, sharing users, entitlements, and services.
Interested in getting started with SAP BTP?
As an SAP Gold Partner, Altivate helps organizations plan, build, and run on SAP Business Technology Platform — from choosing the right environment and commercial model to delivering clean-core extensions and AI-powered applications. Explore our SAP BTP services, see the breadth of our SAP practice, or talk to our team about where SAP BTP fits in your landscape.
