Everything in CAP / Java
Type: 2
Domain
Origin
Signals
Java: Does not say
More
Group by: Capability
Where it runs
Distributed through
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
SAP's Node.js driver for SAP HANA
Managed PostgreSQL from the hyperscaler via a BTP service binding
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.
Managed queues and topics over AMQP, MQTT and REST
Destination lookup and connectivity proxy for the Cloud SDK
HTTP client carrying a destination's credentials
Shared machinery under the Cloud SDK's OData and OpenAPI clients
Generated OpenAPI clients for the Cloud SDK
Timeouts, retries and circuit breaking around remote calls
General utilities shared across the Cloud SDK packages
Prebuilt SAP S/4HANA integration package for CAP projects
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
Prebuilt SAP S/4HANA integration package for CAP projects
Low-code SAP Build capability for custom Joule skills and agents
SAP's AI engagement layer across SAP applications
Orchestration Service client for templating, grounding and masking
AI runtime on BTP with the Generative AI Hub
Orchestration Service client for templating, grounding and masking
AI runtime on BTP with the Generative AI Hub
Extracts header fields and line items from business documents
Vercel AI SDK provider for SAP AI Core
AI Core control plane API surface of SAP's AI SDK
Shared internals of SAP's AI SDK
Client for foundation models via SAP AI Core and Generative AI Hub
Orchestration Service client for templating, grounding and masking
Client for prompts kept in SAP's prompt registry
AI runtime on BTP with the Generative AI Hub
Orchestration Service client for templating, grounding and masking
Client for prompts kept in SAP's prompt registry
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
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
Library for sending usage telemetry data
Predefined CI/CD pipelines for SAP development projects
Language server for CDS
Development environment on BTP for UI5, Fiori, mobile and CAP
Writer of flexible programming model elements into Fiori elements apps
Shared functions and types of the Fiori generators
Writer that adds an OData service to an existing UI5 project
Joule's generative AI inside SAP Build Code
Development environment on BTP for UI5, Fiori, mobile and CAP
Fiori Elements mock server plugin taking a CDS file as metadata
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
Parser for annotations in CDS source
Converter from CDS annotations to their OData form
Programmatic API for reading and writing project annotations
OASIS and SAP OData vocabularies with a VocabularyService
Reader and writer for i18n bundles of UI5 or CAP projects
Fiori documentation indexed as embeddings
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