SAP BAIP, Kyma runtime is now available in China, extending the local SAP BAIP portfolio with a managed Kubernetes-based runtime for cloud-native applications, microservices, and SAP extensions.
Bringing Cloud-Native Innovation Closer to Chinese Customers
Modern enterprises increasingly need to extend business applications, connect systems, and deliver new digital capabilities without introducing unnecessary complexity into their core landscapes.
SAP BAIP in China already offers Cloud Foundry runtime as a mature PaaS option for deploying applications using buildpack-based workflows. Kyma runtime addresses a different set of needs. Built on the open-source Kyma project and Kubernetes, it gives development teams direct access to container-based workloads, serverless functions, and the broader Kubernetes ecosystem—without restriction on programming language or framework. Any workload that can be containerized can run on Kyma runtime.
On June 2, 2026, SAP BAIP, Kyma runtime became available in China (North 3), followed by China (Shanghai) on July 10, 2026—making this managed cloud-native application runtime available through the local BTPEA commercial offering across both regions.
What Is Now Available?
SAP BAIP, Kyma runtime is offered under the BTPEA commercial model, under SKU 8016044 (the customer-facing BTPEA SKU), with the following service plans:
Service: Display Name
Service Plan: Display Name
Available Data Center
Kyma Runtime
Kyma Runtime Alibaba Cloud
China (Shanghai) — cn40
Kyma Runtime
Kyma Runtime Azure
China (North 3) — cn20
Customers and partners can explore the service and its regional availability through SAP Discovery Center:
The China BTPEA price list lists the Standard plan as a billable plan for SAP BAIP, Kyma runtime.
Why This Matters
A Managed, Flexible Foundation for Cloud-Native Applications
Running Kubernetes in-house requires ongoing investment in cluster management, upgrades, security patching, and infrastructure operations. SAP BAIP, Kyma runtime removes that burden: SAP manages the underlying platform, while customers retain full control over their applications and workloads. Development teams can focus on building business capabilities instead of maintaining infrastructure.
Compared to Cloud Foundry runtime, Kyma offers a meaningfully different development model. Cloud Foundry abstracts the runtime through buildpacks, which works well for deploying Java or Node.js applications quickly but limits what you can run and how. Kyma places no such constraints: any containerized workload runs on Kyma regardless of language or framework, and teams have direct access to Kubernetes-native tooling—Helm for packaging, custom resource definitions, fine-grained resource configuration, and the broader CNCF ecosystem. For teams building modern cloud-native applications or needing precise control over their workloads, this flexibility is a significant advantage.
The two runtimes are complementary. Cloud Foundry remains a solid choice for buildpack-based application deployment; Kyma is the better fit when container-native flexibility, polyglot development, or Kubernetes ecosystem tooling is a requirement.
Extending SAP Applications with Event-Driven Integration
Kyma runtime includes a built-in Eventing component that allows applications to subscribe directly to business events from SAP S/4HANA and other SAP systems—so an extension can react to a sales order creation, a goods movement, or a master data change in real time, without polling or point-to-point connections. Having this capability integrated into the runtime means teams can start building event-driven extensions without separately provisioning and configuring a messaging service.
Combined with serverless functions and a built-in API Gateway, this makes it practical to build lightweight, loosely coupled extensions that sit alongside the SAP core rather than inside it. Custom logic evolves independently, upgrade cycles are decoupled, and the core system remains stable.
For scenarios that go beyond SAP-to-SAP integration—connecting third-party systems, orchestrating multi-step workflows, or building net-new business applications—Kyma provides the same Kubernetes-based foundation with the flexibility to incorporate any service or technology the use case requires.
Expanding the Local SAP BAIP Development Portfolio
With Kyma runtime available in China (North 3) and China (Shanghai), customers gain an additional runtime option within the local SAP BAIP portfolio.
This is particularly relevant for teams building containerized applications, API-based integrations, event-driven extensions, and microservices that complement SAP business solutions.
The availability of Kyma runtime broadens the technology choices available to the China ecosystem and provides another foundation for cloud-native application development.
SAP BAIP, Kyma runtime is now available in China, extending the local SAP BAIP portfolio with a managed Kubernetes-based runtime for cloud-native applications, microservices, and SAP extensions.Bringing Cloud-Native Innovation Closer to Chinese CustomersModern enterprises increasingly need to extend business applications, connect systems, and deliver new digital capabilities without introducing unnecessary complexity into their core landscapes.SAP BAIP in China already offers Cloud Foundry runtime as a mature PaaS option for deploying applications using buildpack-based workflows. Kyma runtime addresses a different set of needs. Built on the open-source Kyma project and Kubernetes, it gives development teams direct access to container-based workloads, serverless functions, and the broader Kubernetes ecosystem—without restriction on programming language or framework. Any workload that can be containerized can run on Kyma runtime.On June 2, 2026, SAP BAIP, Kyma runtime became available in China (North 3), followed by China (Shanghai) on July 10, 2026—making this managed cloud-native application runtime available through the local BTPEA commercial offering across both regions. What Is Now Available?SAP BAIP, Kyma runtime is offered under the BTPEA commercial model, under SKU 8016044 (the customer-facing BTPEA SKU), with the following service plans:Service: Display NameService Plan: Display NameAvailable Data CenterKyma RuntimeKyma Runtime Alibaba CloudChina (Shanghai) — cn40Kyma RuntimeKyma Runtime AzureChina (North 3) — cn20Customers and partners can explore the service and its regional availability through SAP Discovery Center:China (North 3) — Kyma RuntimeChina (Shanghai) — Kyma RuntimeThe China BTPEA price list lists the Standard plan as a billable plan for SAP BAIP, Kyma runtime.Why This MattersA Managed, Flexible Foundation for Cloud-Native ApplicationsRunning Kubernetes in-house requires ongoing investment in cluster management, upgrades, security patching, and infrastructure operations. SAP BAIP, Kyma runtime removes that burden: SAP manages the underlying platform, while customers retain full control over their applications and workloads. Development teams can focus on building business capabilities instead of maintaining infrastructure.Compared to Cloud Foundry runtime, Kyma offers a meaningfully different development model. Cloud Foundry abstracts the runtime through buildpacks, which works well for deploying Java or Node.js applications quickly but limits what you can run and how. Kyma places no such constraints: any containerized workload runs on Kyma regardless of language or framework, and teams have direct access to Kubernetes-native tooling—Helm for packaging, custom resource definitions, fine-grained resource configuration, and the broader CNCF ecosystem. For teams building modern cloud-native applications or needing precise control over their workloads, this flexibility is a significant advantage.The two runtimes are complementary. Cloud Foundry remains a solid choice for buildpack-based application deployment; Kyma is the better fit when container-native flexibility, polyglot development, or Kubernetes ecosystem tooling is a requirement.Extending SAP Applications with Event-Driven IntegrationKyma runtime includes a built-in Eventing component that allows applications to subscribe directly to business events from SAP S/4HANA and other SAP systems—so an extension can react to a sales order creation, a goods movement, or a master data change in real time, without polling or point-to-point connections. Having this capability integrated into the runtime means teams can start building event-driven extensions without separately provisioning and configuring a messaging service.Combined with serverless functions and a built-in API Gateway, this makes it practical to build lightweight, loosely coupled extensions that sit alongside the SAP core rather than inside it. Custom logic evolves independently, upgrade cycles are decoupled, and the core system remains stable.For scenarios that go beyond SAP-to-SAP integration—connecting third-party systems, orchestrating multi-step workflows, or building net-new business applications—Kyma provides the same Kubernetes-based foundation with the flexibility to incorporate any service or technology the use case requires.Expanding the Local SAP BAIP Development PortfolioWith Kyma runtime available in China (North 3) and China (Shanghai), customers gain an additional runtime option within the local SAP BAIP portfolio.This is particularly relevant for teams building containerized applications, API-based integrations, event-driven extensions, and microservices that complement SAP business solutions.The availability of Kyma runtime broadens the technology choices available to the China ecosystem and provides another foundation for cloud-native application development. Read More Technology Blog Posts by SAP articles
