Everything in CAP
Type
Domain: Operations & Runtime
Origin
Signals
Content
More
Group by: Capability
Shows which feature branches reached which environment branch
A team that does not keep one long-lived branch per environment has no environment branches for it to compare feature branches against. What it reports is the merge state of branches in Git, so it says nothing about whether a merged change has been built or deployed to the environment.
CAP Node.js runtime
Reads bound service credentials on SAP BTP, Cloud Foundry for CAP Java
Reads SAP BTP Operator service bindings on Kyma for CAP Java
Maven bill of materials pinning CAP Java module versions
Generates Helm charts for the CAP Operator on Kubernetes
Tool completing a CAP project's deployment configuration
Tied to a specific training repository and last released August 2023. The repository the package declares has been deleted — verified against the GitHub API, not just a failed fetch. The package is still on npm, so it installs; the source it was published from is no longer readable, which is a harder thing to discover than a stale version number.
Command line client and development toolkit for CAP
CAP bookshop with Fiori elements UI deployed whole to Cloud Foundry
Neither the package manifest nor the repository tree declares a licence.
CAP project built and deployed to Cloud Foundry by GitHub Actions
reCAP 2025 workshop on cutting a CAP app into microservices
Approuter session held in a bound Redis cache instance
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary Not a descriptor to deploy as it stands: the approuter's `sessionSecret` is written out in `mta.yaml`.
MTA deploying CAP, HDI container and a Fiori elements app
Companion repo deploying a CAP app to Cloud Foundry two ways
CAP sample sharing one domain model and database across apps
Not in production. SAP states it is just a sample, not optimised for performance or security.
CAP Java sample sharing one domain model across several apps
Not in production. SAP states it is just a sample, not optimised for performance or security.
VS Code Multi-Target Application tools
Live-updatable feature toggles for CAP, backed by Redis
Multitenancy, tenant provisioning and extensibility for CAP
Feature-toggle pattern for CAP CDS
Last released June 2022 at 0.0.6, and no repository is declared on the package.
Maven bill of materials pinning CAP Java module versions
Boolean and string flags read by applications at runtime
CAP Node.js runtime
Transactional processing of asynchronous and periodic CAP events
If you need sub-second fan-out to external consumers this is the wrong layer — reach for [Event Mesh](artifact:btp-event-mesh) or Kafka. Without [Redis](external:redis), periodic processing still works but instant dispatch degrades to polling.
CAP Node.js runtime
Calls an application endpoint on a schedule and logs each run
CAP integration with the SAP Audit Log service
Maven bill of materials pinning CAP Java module versions
Collects Cloud Foundry or Kyma logs into a searchable Kibana
Ten short CAP Java references, one document per topic
CLI for operating tenants of multitenant CAP applications
CAP Node.js runtime
Multitenancy, tenant provisioning and extensibility for CAP
WebAssembly sandbox for tenant-specific extension code in CAP
Multitenancy for CAP Java: tenant lifecycle and per-tenant containers
Maven bill of materials pinning CAP Java module versions
Registers a multitenant application for subaccount subscriptions
Multitenant CAP application using cds-mtxs
Neither the package manifest nor the repository tree declares a licence.
CAP sample of SAP Event Mesh events feeding a multi-tenant SaaS app
Poetry Slam Manager, a multi-tenant SaaS reference app on SAP BTP
Guide migrating the hana-shine-xsa demo from XS Advanced to CAP
Directed at single-tenant applications, which the guide states as its scope. The migration path it uses also has no option to select individual containers, so it migrates every container in the given space.
Guide to migrating XS Advanced database artefacts to CAP
Guide to migrating XS Classic database artefacts to CAP
Directed at single-tenant applications, which the guide states as its scope. Migration of the whole delivery unit or package fails if any source file has errors; the README gives JavaScript files containing unknown characters as its example.
Business-level metrics from CDS annotations via @cap-js/telemetry
OpenTelemetry instrumentation for CAP services
CAP plugin controlling CDS logger and OpenTelemetry log verbosity
Library for sending usage telemetry data
Policy enforcement and field masking for MCP-enabled CAP apps
UI5 frontend performance and error capture for CAP
CAP caching plugin for query results and remote service responses
When user-dependent responses are cached without user-aware or explicit operation keys, or translated responses share keys across locales. These cases require key isolation; locale-aware keys are off by default.
Maven bill of materials pinning CAP Java module versions
OpenTelemetry support for the CDS Node.js runtime