Everything in CAP
Type: 4
Domain
Origin
Signals
More
Group by: Capability
Distributed through
Compiler from a CDS service to SEGW model and data provider classes
The generated files are copied or deployed into the ABAP system by hand, the fourth step of its own usage list, so nothing keeps an activated service in step with the model it was generated from. Its peer dependency is `@sap/cds` ^9.8, so it does not install into a project on an earlier CAP release.
API proxies with security and traffic policies and Developer Hub
APIs and a UI5 component for document management in apps
Managed Redis from the hyperscaler via a BTP service binding
Compiler from CDS models to CSN, EDMX and database schemas
Managed PostgreSQL from the hyperscaler via a BTP service binding
SAP's relational database platform, on-premise and in HANA Cloud
For provisioning a managed database on BTP, see [SAP HANA Cloud](artifact:btp-hana-cloud). Features differ between HANA versions; an on-premise deployment and a cloud instance are not interchangeable without compatibility checks.
Managed SAP HANA database service on BTP
Provisioned per plan and per component, so capacity and cost are decisions taken before any model exists. And it is the database, not a warehouse — modelling, loading and cataloguing are the products above it, and reaching it directly bypasses every semantic they add.
Delta deployment and migrations for CAP database adapters
Archived The declared repository is archived.
Functional boundary The repository is archived, so nothing here will move again. Fine to keep where it already runs; anything new should start from what the current cds deploy leaves open rather than from this.
Managed queues and topics over AMQP, MQTT and REST
Named, credentialed addresses of other systems resolved at runtime
Managed queues and topics over AMQP, MQTT and REST
Event streaming and management platform in Integration Suite
Proxy from cloud apps to on-premise systems via Cloud Connector
Low-code SAP Build capability for custom Joule skills and agents
SAP's AI engagement layer across SAP applications
AI runtime on BTP with the Generative AI Hub
AI runtime on BTP with the Generative AI Hub
Extracts header fields and line items from business documents
AI runtime on BTP with the Generative AI Hub
AI runtime on BTP with the Generative AI Hub
AI runtime on BTP with the Generative AI Hub
Managed SAP HANA database service on BTP
Provisioned per plan and per component, so capacity and cost are decisions taken before any model exists. And it is the database, not a warehouse — modelling, loading and cataloguing are the products above it, and reaching it directly bypasses every semantic they add.
API proxies with security and traffic policies and Developer Hub
Ingests and retains compliance audit data from BTP
Identity Authentication and Identity Provisioning as one tenant
OAuth server issuing JWTs and holding scopes for BTP apps
Compiler from AMS DCL policies to DCN for local runs and tests
Its own account of itself is local running and tests: the DCN it writes serves as input for running an application using AMS on the DCL bundle locally. It carries the SAP Developer License Agreement rather than an open-source licence, and the repository named in its package metadata is an internal SAP host, so the npm page is the only thing to read.
OAuth server issuing JWTs and holding scopes for BTP apps
Scans uploaded files over REST with ClamAV
API proxies with security and traffic policies and Developer Hub
Vault for an application's passwords, keys and keyrings
Boolean and string flags read by applications at runtime
Calls an application endpoint on a schedule and logs each run
Collects Cloud Foundry or Kyma logs into a searchable Kibana
Registers a multitenant application for subaccount subscriptions
GitHub Action setting up the Cloud Foundry CLI
Predefined CI/CD pipelines for SAP development projects
Development environment on BTP for UI5, Fiori, mobile and CAP
Maven plugin running CDS build steps in a CAP Java project
Joule's generative AI inside SAP Build Code
Development environment on BTP for UI5, Fiori, mobile and CAP
ESLint plugin with one consultancy's rules for CDS files
Neither the package manifest nor the repository tree declares a licence.
Shared ESLint configuration for SAPUI5 and CAP projects
ESLint rules for projects the Fiori tools generators produce
SAP's ESLint plugin for CDS
ESLint rules flagging deprecated CAP configuration
Compiler from AMS DCL policies to DCN for local runs and tests
Its own account of itself is local running and tests: the DCN it writes serves as input for running an application using AMS on the DCL bundle locally. It carries the SAP Developer License Agreement rather than an open-source licence, and the repository named in its package metadata is an internal SAP host, so the npm page is the only thing to read.
Maven plugin running CDS build steps in a CAP Java project
Dev-time wrapper for the SAP Application Router
CDS build task compiling TypeScript sources during cds build
Generates TypeScript types from a CDS model
Maven plugin running CDS build steps in a CAP Java project
Managed hosting and routing for built frontends
SAP's own guidance is narrower than the service's reach: it names standalone, single-tenant applications that do not connect to other applications as the fit, and says to stay on [the HTML5 Application Repository](artifact:btp-html5-application-repository) and the application router where those meet your needs better. Four hard limits decide it before taste does — 300 requests per second per subaccount, ten retained versions per application, 100 MB per application and 400 MB for the deployment archive.
Stores UI5 and HTML5 apps and serves them through the approuter
Versioned specification of the abap2UI5 roundtrip protocol
Neither suite has been run against an ABAP system: the reference backends are the framework transpiled to Node and cap2UI5 on CAP, so what a check does on a real system is open. The portable profile is a subset of 61 controls, filled from a census of 247 core apps of which 64.8 % run unchanged, so an app outside it renders placeholders in the terminal and Adaptive Cards renderers.
Binding onto hyperscaler object storage, chosen by plan
Cloud Foundry runtime of SAP BTP for polyglot applications
One inbox for tasks across SAP applications and BTP workflows