Everything in the atlas
Type
Domain: Data & Persistence
Origin
Signals
More: 2
Group by: None
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
CAP Node.js attachments with database, S3, Azure or GCP storage
Monorepo of CAP's SQL database services
Base service shared by CAP's SQLite, PostgreSQL and HANA services
SAP HANA database service for CAP
PostgreSQL database service for CAP
CAP attachments stored in an SAP Document Management repository
If document versions are required, [@cap-js/sdm](artifact:cap-js-sdm) excludes versioned repositories in its [documented restrictions](https://raw.githubusercontent.com/cap-js/sdm/ad13b61f21816ebead2d08264a74521cfb75846c/README.md).
SQLite database service for CAP, in memory during development
CLI for DROP and RENAME schema changes beside @cap-js/postgres
CDS annotation vocabulary for entity search with schema discovery
The metadata is inconsistent: the declared repository is github.com/acme/search-vocab and the README installs @acme/search-vocab, neither of which matches the published name. One release, November 2025.
MCP server with forty-five tools across a Datasphere tenant
It writes and it administers — ETL extraction and database user management are not read operations, and the same connection that profiles a column can move data out of the tenant. Masking is only as good as the configuration naming the fields, so an unlisted sensitive column is an unmasked one.
CAP plugin casting read values back to CDS model types
CAP plugin stripping whitespace from strings on write via @cds.trim
CAP plugin uppercasing strings on write via @cds.uppercase
DB2 adapter for CDS
The README is one line and the package carries no licence field. Last released July 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.
Fork of cds-dbm with deploy, load, diff and drop tasks
Release and repository quiet for 39 months.
CAP Node.js runtime
ISO content for CAP's countries, languages, currencies and timezones
Compiler from CDS models to CSN, EDMX and database schemas
Command line client and development toolkit for CAP
Database adapter for SAP HANA in CAP
Multitenancy, tenant provisioning and extensibility for CAP
SAP's Node.js driver for SAP HANA
Node.js deployer for SAP HANA Deployment Infrastructure containers
CAP Node.js attachments plugin with Object Store and malware scanning
MCP server for BW/4HANA modelling objects
Its README says it plainly and so does this entry: this is not a simulation, every tool call reaches a live BW system, and write operations produce real changes. BW modelling objects are the definition of a warehouse — the blast radius of a wrong one is every report built on it.
CAP Node.js attachments plugin with database or cloud storage
Collaborative draft support for CAP Node.js services
The maintainer marks this under active development; public APIs, annotation names and OData contracts may still change.
Annotation-driven geocoding, address correction and routing for CAP
Nothing about it is readable from outside the package: there is no repository, no issue tracker, and the npm page carries no readme, so the README, the examples and the changelog can be read only from the tarball or a CDN mirror, and a bug has nowhere to be filed. Provider URLs are called from the plugin with API keys taken from environment variables in a .env file, so on BTP no call resolves through a destination and the keys live in the environment. The npm line stops at 1.0.1 on 3 November 2025; the changelog shipped inside that version is headed v2.1, so the version npm shows and the version the author counts are not the same.
Tunnels CAP Node.js to a private PostgreSQL via Cloud Connector
CAP database adapter for Snowflake with OData V4 support
The maintainer marks this early development; expect the contract to move.
User details and quickview links for createdBy and modifiedBy
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.
Data federation for CAP via delegation, caching and replication
Scheduled READ, MAP, WRITE pipelines between CAP services
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.
CAP Java plugin for soft delete with a softdelete aspect
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The Maven coordinate its README gives, io.github.miyasuta:cds-feature-softdelete:1.0.0, does not resolve on Maven Central as of 2026-09-07 — you build and install it from source.
CAP-to-CAP data federation over SAP HANA synonyms
When your adoption policy excludes experimental dependencies: the [maintainer’s README](https://github.com/cap-js/cds-federation-synonyms#about-this-project) explicitly labels this plugin experimental.
MongoDB as a CAP database service through Mongoose
It declares no peer range on [@sap/cds](artifact:sap-cds) and publishes no repository, so there is nothing to read but the package itself and no CI to look at.
MySQL and MariaDB database adapter for CAP
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.
Fills a CDS element from a database-backed number range
PostgreSQL adapter for SAP CDS from the SAP Mentors community
The declared repository is archived.
CAP plugin turning DELETE into a flag on annotated entities
It changes what DELETE means for every client of the annotated projection, so anything that must actually remove a row — an erasure request, a retention job — has to go around it.
Spreadsheet upload into a CDS entity, parsed on the server
CAP Java attachments with database storage and an Object Store module
For deployed environments, the [README](https://raw.githubusercontent.com/cap-java/cds-feature-attachments/302f61c8bb76a0f54f43482ad91d89bf7dc5540f/README.md) excludes the cds-feature-attachments-fs file-system target, which is intended only for local development and testing.
SAP HANA Cloud datasource for CAP Java applications
JDBC runtime for H2 and SQLite in CAP Java
PostgreSQL datasource for CAP Java applications
Maven bill of materials pinning CAP Java module versions
CAP Java plugin for attachments in SAP Document Management
If document versions are required, the [documented restrictions](https://raw.githubusercontent.com/cap-java/sdm/673769f24ef66fd97daa6a6be41262d45065d3fe/README.md) exclude versioned repositories.
dbt adapter targeting SAP HANA Cloud as its warehouse
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.
Read-only MCP server for exploring SAP Datasphere
Business Source License 1.1, which is source-available rather than open source: reading and evaluating are fine, and production use is restricted until the licence's change date. That is a procurement question, not a technical one, and it is the thing to settle first. Read-only also means read-only — no modelling, no loads.
Binding onto hyperscaler object storage, chosen by plan
Managed PostgreSQL from the hyperscaler via a BTP service binding
Managed Redis from the hyperscaler via a BTP service binding
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.
Managed SAP ASE databases on BTP for Java applications
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.
APIs for address cleansing, geocoding and suggestions
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.
Eighteen Datasphere skills over a bundled MCP server
It reaches a data warehouse, so what an agent can see is business data by definition — the SQL sanitisation and PII filtering in the server are there because of that, not instead of a decision about it. And the guidance is Datasphere-shaped: nothing here transfers to a HANA Cloud database used directly.
Ready-to-use web application for enterprise content
APIs and a UI5 component for document management in apps
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.
Managed SAP HANA 2.0 databases in fixed sizes on SAP BTP
APIs for geocoding, map tiles and routing
Cloud service replicating master data across a hybrid landscape
MCP server for the SAP Analytics Cloud REST API
Ninety tools is a large surface to put in front of a model at once, and client-credentials OAuth means the tenant sees one identity rather than the person asking. Content transport and user management sit in the same tool list as reading a story.
MCP tooling for SAP Business Data Cloud discovery and contracts
Business Source License 1.1: source-available, with production use restricted until the change date — settle that before anything technical. And the governed execution path in v0.2 does act on data, which is a different grant from the discovery the v0.1 baseline offered.
MCP server managing Delta shares in SAP Business Data Cloud
CAP Node.js plugin mapping CDS entities to SAP Document Management
Archived The declared repository is archived.
Functional boundary For versioned or thumbnail-enabled repositories, or bulk upload and download, the [README](https://raw.githubusercontent.com/vneecious/sap-cap-sdm-plugin/d9f036b16542e5c5b9b6dc704e0ba5f880193212/README.md) labels this an “early release” and lists those features as unsupported.
Developer-centric command line for SAP HANA
Promise-based wrappers around the SAP HANA client libraries
Fiori Elements page embedding upload controls on @cap-js/attachments
Neither the package manifest nor the repository tree declares a licence.
Fiori overview page comparing aggregated and plain donut-chart cards
Neither the package manifest nor the repository tree declares a licence.
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
CAP and Fiori app showing BTP Application Vulnerability Report data
Neither the package manifest nor the repository tree declares a licence.
Analytical List Page over a CAP OData V4 service
Neither the package manifest nor the repository tree declares a licence.
CAP services reading each other's HANA tables across HDI containers
Neither the package manifest nor the repository tree declares a licence.
Media handling in core CDS with a UI5 UploadSet
Neither the package manifest nor the repository tree declares a licence.
Replication between systems with CAP
Neither the package manifest nor the repository tree declares a licence.
sflight example extended with hierarchy support
Neither the package manifest nor the repository tree declares a licence.
CAP's getting-started bookshop sample
Composite CAP app from separately deployed services
SQL scripts and a notebook for SAP HANA's built-in graph algorithms
Tutorials and use cases for SAP HANA database and analytics products
Java demo running Spring and Hibernate against SAP HANA
CAP beershop on PostgreSQL, predating an official adapter
CAP service reading and writing MongoDB from custom handlers
Neither the package manifest nor the repository tree declares a licence.
Five-part workshop on CDS, from a first service to constraints
CodeJam building a full-stack CAP app on SAP HANA Cloud
CAP data model of many-to-many relationships on a Star Wars dataset
Starting project for a tutorial on NoSQL, graph and spatial in HANA
Course files for Developing Data Models with SAP HANA Cloud
reCAP 2026 workshop on data federation between CAP applications
Guides connecting hyperscaler sources into SAP Datasphere in BDC
TechEd 2025 workshop on SAP Business Data Cloud connectivity options
TechEd 2025 jump-start on a semantic model in SAP Datasphere and SAC
CAP Risks and Mitigations project with a Spreadsheet Upload button
TechEd 2023 session on SAP HANA features over HDI
TechEd 2025 workshop on SAP HANA Cloud's AI capabilities
TechEd 2025 workshop on Just Ask natural-language questions
TechEd 2025 workshop on seamless planning for xP&A in BDC
CAP reuse package serving Airlines, Airports and Flights data
CAP Java reuse package for Airlines, Airports and Flights data