Everything in BTP/BAIP
Type: 3
Domain
Origin
Signals
More
Group by: Capability
Where it runs
Distributed through
Generates
Run with
HL7 FHIR implementation for storing and exchanging health data
API proxies with security and traffic policies and Developer Hub
SaaS for business intelligence, planning and predictive analytics
A tenant with its own model layer, its own transport and its own user administration — content moves between tenants through export and import jobs rather than through your pipeline, and planning brings a calendar and a workflow that a reporting-only use never touches.
Cloud data warehouse with spaces, views and analytic models
A tenant with spaces and a role model, not a database you point an application at — privileges are granted per space, and what somebody can model depends on the scoped role they hold. Federation is the default answer to moving data, and where it is not, a load has to be scheduled and watched.
Ready-to-use web application for enterprise content
APIs and a UI5 component for document management in apps
Managed Redis from the hyperscaler via a BTP service binding
Data products, a governed catalog and a path to SAP Databricks
It presumes the estate it governs: intelligent content is installed and viewed rather than authored, and the catalog is only as useful as what has been published into it. The Databricks path is a direction data goes, which is a decision about where analytics happens and not only about a tool.
Cloud data warehouse with spaces, views and analytic models
A tenant with spaces and a role model, not a database you point an application at — privileges are granted per space, and what somebody can model depends on the scoped role they hold. Federation is the default answer to moving data, and where it is not, a load has to be scheduled and watched.
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.
SAP's Node.js driver for SAP HANA
Pure JavaScript SAP HANA driver for Node.js
Its own feature comparison marks connection pooling, automatic reconnect, active-active reads, client-side data encryption, statement distribution, Kerberos authentication, the hdbuserstore, promises and TypeScript types as [@sap/hana-client](https://www.npmjs.com/package/@sap/hana-client) only, so a service that wants a pool or a promise API writes both itself over a callback interface. OpenSSL is its one security provider where the other driver lists SAP CommonCryptoLib, OpenSSL and MSCrypto, and it runs on Node.js 18 or later.
Managed PostgreSQL from the hyperscaler via a BTP service binding
Managed SAP ASE databases on BTP for Java applications
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 SAP HANA 2.0 databases in fixed sizes on SAP BTP
Promise-based wrappers around the SAP HANA client libraries
dbt adapter targeting SAP HANA Cloud as its warehouse
SaaS for business intelligence, planning and predictive analytics
A tenant with its own model layer, its own transport and its own user administration — content moves between tenants through export and import jobs rather than through your pipeline, and planning brings a calendar and a workflow that a reporting-only use never touches.
Cloud data warehouse with spaces, views and analytic models
A tenant with spaces and a role model, not a database you point an application at — privileges are granted per space, and what somebody can model depends on the scoped role they hold. Federation is the default answer to moving data, and where it is not, a load has to be scheduled and watched.
APIs for address cleansing, geocoding and suggestions
APIs for geocoding, map tiles and routing
Cloud service replicating master data across a hybrid landscape
Binding onto hyperscaler object storage, chosen by plan
Managed queues and topics over AMQP, MQTT and REST
B2B interface and mapping specification in Integration Suite
Yeoman generator for Cloud Connector mappings and BTP destinations
Named, credentialed addresses of other systems resolved at runtime
Private network link between a BTP service and a partner cloud
Adobe Document Services on BTP for print and interactive PDFs
Print queues between cloud applications and local printers
Managed queues and topics over AMQP, MQTT and REST
Distributes business events between SAP cloud applications
Event streaming and management platform in Integration Suite
Event broker inside SAP Integration Suite
Builds and runs integration flows between cloud and on premise
Guided workflow for configuring SAP cloud solution integration
Proxy from cloud apps to on-premise systems via Cloud Connector
Prebuilt connectors to non-SAP cloud applications as REST APIs
Partner profiles and agreements for B2B exchange in Integration Suite
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
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.
Python library turning OData or HANA records into chunked documents
An early alpha release whose README says to pin the version and test recipes against non-production data first. HANA synchronisation is snapshot-only and does not reconcile deleted rows, so a document for a row deleted in the source stays in the index. A recipe's field allow-list does not decide what the service account may read: the README states that field allow-listing does not replace SAP authorization, and that the package infers no SAP module semantics, authorization scope or safe fields from table names. Only Business Partner has a built-in recipe, every other dataset needs a `KnowledgeRecipe` written for it, and [Qdrant](external:qdrant) local mode is stated to be for development and smaller indexes.
AI runtime on BTP with the Generative AI Hub
ML models that classify records and predict attributes
Machine learning recommendations over browsing history via REST
AI runtime on BTP with the Generative AI Hub
API proxies with security and traffic policies and Developer Hub
Ingests and retains compliance audit data from BTP
XSUAA authentication stack for an MCP server on SAP BTP
It stops at the `AuthInfo` and the raw bearer token, and the README lists what stays with the consuming server: rate limiting, the scope and tool policy, the MCP transport, the SAP HTTP client's headers, and helmet-style hardening. The one piece of hardening it constrains rather than defers is the cross-origin opener policy, which it deliberately leaves unset because popup-based OAuth breaks under it. It is ESM-only on Node 22 or later and shares the host's Express and MCP SDK instances as peer dependencies, so a server on Express 4 cannot take it.
Browser login and session module for SAP MCP servers
The maintainer states it is unofficial, not endorsed by SAP, and that it automates authenticated SAP web endpoints and browser session cookies in ways SAP's terms of service or an organisation's own policies may restrict. Password login is confined to `accounts.sap.com` and the standard SAP Cloud Identity Services tenant domains: a custom IAS domain, or a login that conditional authentication delegates to a corporate identity provider, fails closed before the password is filled and has to be completed through an interactive login instead.
TypeScript library reaching ABAP service instances on Cloud Foundry
Identity Authentication and Identity Provisioning as one tenant
OAuth 2.0 grant flows for applications and APIs in Neo regions
OAuth server issuing JWTs and holding scopes for BTP apps
Registration, login and consent for customer-facing sites
OAuth 2.0 grant flows for applications and APIs in Neo regions
OAuth server issuing JWTs and holding scopes for BTP apps
Serves BTP applications under the customer's own domain
Registration, login and consent for customer-facing sites
APIs for retention, deletion and personal data reports
Retention rules triggering blocking, deletion and archiving
Service answering data subjects about their stored personal data
Key and certificate repository in SAP BTP's Neo data centres
Provisioning jobs carrying users and groups between systems
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
Tracks vulnerabilities in open-source components of BTP apps
REST APIs for administering a BTP account
Registry for service brokers, instances and environments on SAP BTP
Terraform and OpenTofu provider for SAP BTP global accounts
ABAP runtime on BTP for the ABAP Cloud model
1 of 8 plans deprecated.
Cloud Foundry runtime of SAP BTP for polyglot applications
Managed Kubernetes runtime on SAP BTP based on Kyma
Moves MTA archives and content between SAP BTP accounts
REST APIs for SAP BTP usage per metric and monthly cost
Scales Cloud Foundry app instances by policy rules and schedules
Moves MTA archives and content between SAP BTP accounts
Assembles BTP service content into an MTAR for transport
Deploys and manages MTA-based Solutions in the Neo environment
MTA generation and Cloud Foundry deploy for VS Code workspaces
A library a VS Code extension calls, not something installed and run on its own; there is no documented standalone CLI. No public repository either, so what it does is read from its own README rather than checked against source.
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
OpenSearch-based store for logs, metrics and traces
Registers a multitenant application for subaccount subscriptions
Scales Cloud Foundry app instances by policy rules and schedules
Publishing and subscribing to alerts about BTP resources and apps
Runs operations commands on BTP by hand, schedule or event
Metrics, availability checks and alerts for apps in Neo regions
SAP Passport handling for Node.js components
Injects the Dynatrace agent into Java applications on SAP BTP
OpenSearch-based store for logs, metrics and traces
Metrics, availability checks and alerts for apps in Neo regions
Predefined CI/CD pipelines for SAP development projects
Development environment on BTP for UI5, Fiori, mobile and CAP
Browser-based development environment with dev spaces
IDE service on SAP BTP for SAPUI5, Fiori and full-stack apps
Low-code platform for web and native mobile apps
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
Key-user adaptation and personalisation for UI5 apps on SAP BTP
Business sites and digital workspaces with collaboration tools
Role-based business site for SAP and third-party apps
Role-based portal sites with pages, apps and widgets
Easy-UI5 generator for a TypeScript Fiori launchpad plugin
Role-based business site for SAP and third-party apps
Translation service for software texts and documents
BTP service for building and running Agentry mobile apps
Low-code platform for web and native mobile apps
SAP BTP service for native and cross-platform mobile apps
2 of 8 plans deprecated.
One inbox for tasks across SAP applications and BTP workflows
Rule-based resolution of SAP S/4HANA business situations
Low-code and no-code tool for business processes and RPA bots
Resolves who is responsible for a process or item, and notifies them
Business data graph queried with OData V4 or GraphQL
Joule's generative AI inside SAP Build Code
SaaS front end over SAP AI Core
Integration service on BTP with Cloud Integration and API Management