SAP BTP Kyma
Kubernetes-native extensibility on SAP BTP — containerized microservices, Helm chart deployments, serverless functions, and event-driven architectures that keep your SAP core clean and your extensions independently scalable.
What we deliver
Kyma Environment Setup
Kyma cluster provisioning, namespace design, resource quota planning, RBAC configuration, SAP BTP service operator setup, and BTP Operator for seamless service binding integration.
Workload Deployment
Helm chart design and deployment, Kubernetes manifest management, Docker image build pipelines, multi-arch container support, and blue/green or canary release strategies.
BTP Service Integration
BTP Operator configuration, service instance and binding management for XSUAA, Destination, Connectivity, SAP Event Mesh, and HANA Cloud — all declaratively managed in Git.
Serverless & Event-Driven
Kyma serverless function development, SAP Event Mesh subscription configuration, CloudEvents handling, and event-driven extension patterns reacting to SAP S/4HANA business events.
CI/CD for Kubernetes
GitHub Actions pipelines for container build, image scanning, Helm deployment to Kyma, smoke tests, and automated rollback — GitOps-ready, with OIDC-based workload identity and no long-lived credentials.
Observability & Operations
Istio service mesh metrics, distributed tracing, log aggregation, alerting rules, autoscaling configuration, and capacity planning — full observability across all Kyma workloads.
Kyma vs Cloud Foundry — when to use which
| Dimension | Cloud Foundry | Kyma |
|---|---|---|
| Runtime model | PaaS — managed app containers | Kubernetes — full container control |
| Language support | Buildpack-based (Node.js, Java, Python…) | Any container image |
| Operational complexity | Low — CF manages routing and scaling | Higher — Helm, K8s manifests |
| Serverless | CF Tasks | Kyma serverless functions |
| Best for | CAP apps, MTA-based SAP extensions | Microservices, event processors, custom runtimes |
Both runtimes are available on SAP BTP and can be used together within the same subaccount.
How we work
Design
We define the cluster topology, namespace strategy, service mesh configuration, BTP service operator setup, and CI/CD model — aligned with your security requirements and team capabilities.
Provision
Kyma environment activation, namespace creation, RBAC setup, BTP Operator configuration, service instance provisioning, and initial connectivity validation with SAP backend systems.
Deploy
Helm chart deployment, container registry setup, GitHub Actions CI/CD pipeline, image scanning, deployment validation, and first production workload release with rollback safety net.
Operate
Monitoring dashboards, alerting, log analysis, autoscaling review, capacity planning, and runbooks covering common Kyma operational tasks — your team owns the platform from day one.
Ready to modernize with Kubernetes on BTP?
Let’s design your Kyma environment.
Tell us about your extension and microservice requirements — we’ll architect a secure, scalable Kyma environment on SAP BTP that’s built for production from day one.
Get in touch →