CDS pluginCDS pluginInstalls into a CAP project and extends the runtime. CAP loads it through cds.requires or the plugin hook.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
cap-postgres-btp-connectivity
Connects a CAP Node.js application to a PostgreSQLPostgreSQLA relational database. For CAP it is the production database when the answer is not HANA, reached through an adapter that translates CDS queries into its SQL. database that is not publicly reachable, tunnelling through BTP Connectivity and the Cloud Connector.
Facts
Latestv0.3.0ReleasedLicenceCopyright 2026 cap-postgres-btp-connectivity contributors
Where it sits
Lives in
Provides
Database connectorsCAPDatabase connectorsConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).
Flavors
Requires
PostgreSQLPostgreSQLNamed as a dependency in its documentation.SAP Connectivity serviceSAP Connectivity serviceNamed as a dependency in its documentation.Cloud ConnectorCloud ConnectorThe private PostgreSQL database is reached through a Cloud Connector TCP system mapping, whose Location ID and virtual host and port the package is configured with.
Before choosing this
Conditions
LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2, 3A cds-plugin is used with SAP CAP materials, or an artifact is explicitly identified as a CAP plugin or application.
- § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
- § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.
- § 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
Also, from Database connectors§ 1: The connector itself does not decide the licence boundary. Section 1 makes the destination and purpose of extraction relevant, including the scoped exception for interoperability with an SAP product.
What it declares
Every artifact
- Type
- CDS plugin
- Origin
- Independently maintained
As a CDS plugin
- Distributed through
- npm
Connections
Group by
NodeRelationBasis
Functional
Database connectorsDatabase connectorsConnecting a data model and its queries to a databaseSAP and community, narrow by design
provides
authored
provides Database connectors
Connecting a data model and its queries to a database
Technical
PostgreSQL on SAP BTP, hyperscaler optionPostgreSQL on SAP BTP, hyperscaler optionManaged PostgreSQL from the hyperscaler via a BTP service bindingsap official, btp
available via
derived
available via PostgreSQL on SAP BTP, hyperscaler option
Managed PostgreSQL from the hyperscaler via a BTP service binding
connects to
stated
connects to PostgreSQL
Opening the database connection of a CAP application to a PostgreSQL server in a private network, through the Connectivity service's SOCKS5 endpoint and a TCP mapping in the Cloud Connector.
“Community adapter for connecting a Node.js CAP application to a private PostgreSQL database through SAP BTP Connectivity Service and SAP Cloud Connector.”“explains the Connectivity service SOCKS5 endpoint”“Use the third document to perform the required Cloud Connector TCP configuration.”
A relational database. For CAP it is the production database when the answer is not HANA, reached through an adapter that translates CDS queries into its SQL.
Cloud ConnectorCloud ConnectorSAP's on-premises agent linking SAP BTP to customer-network systemssap official, btp
needs
stated
needs Cloud Connector
The private [PostgreSQL](external:postgresql) database is reached through a Cloud Connector TCP system mapping, whose Location ID and virtual host and port the package is configured with.
“Do not continue with the package configuration until the BTP subaccount is connected to Cloud Connector, the TCP mapping is reachable, and the virtual host, virtual port, and Location ID are known.”
SAP's on-premises agent linking SAP BTP to customer-network systems
needs
authored
needs PostgreSQL
A relational database. For CAP it is the production database when the answer is not HANA, reached through an adapter that translates CDS queries into its SQL.
SAP Connectivity serviceSAP Connectivity serviceProxy from cloud apps to on-premise systems via Cloud Connectorsap official, btp
needs
authored
needs SAP Connectivity service
Proxy from cloud apps to on-premise systems via Cloud Connector
Download
Install
npm add cap-postgres-btp-connectivityDerived from the package name. No recipe recorded; the README has the configuration.
Where it sits in your app
Download
PostgreSQLA relational database. For CAP it is the production database when the answer is not HANA, reached through an adapter that translates CDS queries into its SQL.
cap-postgres-btp-connectivityConnects a CAP Node.js application to a PostgreSQL database that is not publicly reachable, tunnelling through BTP Connectivity and the Cloud Connector.independent, cap
Cloud ConnectorSAP's on-premises agent that links SAP BTP applications to systems in a customer's own network, as a reverse invoke proxy that exposes only the systems and resources it is configured to allow.sap official, btp
SAP Connectivity serviceThe proxy through which a cloud application reaches an on-premise system behind a Cloud Connector — HTTP, RFC and raw sockets — without that system being exposed.sap official, btp
cap-postgres-btp-connectivity → PostgreSQLStated in the document, data, SOCKS5, TCP, outbound, via SAP Connectivity serviceOpening the database connection of a CAP application to a PostgreSQL server in a private network, through the Connectivity service's SOCKS5 endpoint and a TCP mapping in the Cloud Connector.
cap-postgres-btp-connectivity → SAP Connectivity serviceDocumented only
cap-postgres-btp-connectivity → Cloud ConnectorDocumented onlyThe private PostgreSQL database is reached through a Cloud Connector TCP system mapping, whose Location ID and virtual host and port the package is configured with.
Cloud Connector → SAP Connectivity serviceDocumented only, data, outboundRegistering with the Connectivity service of a subaccount and, with it, providing the tunnel through which applications on SAP BTP reach systems in the on-premise network. The connector works as a reverse invoke proxy, and no port is exposed on the on-premise side.
SAPnot SAP's, or the project's ownstated in the documentdocumented only
README
quoted from cap-postgres-btp-connectivity@0.3.0, readcap-postgres-btp-connectivity@0.3.0/README.mdthe maintainer’s wordsOn npm
cap-postgres-btp-connectivity
Community adapter for connecting a Node.js CAP application to a private PostgreSQL database through SAP BTP Connectivity Service and SAP Cloud Connector.
This package is not an official SAP product and is not supported by SAP.
History
Others providing
Compare all 22 on the Database connectors page →Database connectorsDatabase connectorsConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to schema evolution.SAP and community, narrow by design
- SAP HANA CloudSAP HANA CloudThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btpManaged SAP HANA database service on BTP
- PostgreSQL on SAP BTP, hyperscaler optionPostgreSQL on SAP BTP, hyperscaler optionA managed PostgreSQL from the underlying hyperscaler — AWS, Azure, Google Cloud or Alicloud — consumed through a BTP service binding.sap official, btpManaged PostgreSQL from the hyperscaler via a BTP service binding
- com.sap.cds:cds-feature-hanacom.sap.cds:cds-feature-hanaThe CAP Java feature that wires a Maven application to SAP HANA Cloud, the production default among CAP's supported databases.sap official, capSAP HANA Cloud datasource for CAP Java applications
- com.sap.cds:cds-feature-jdbccom.sap.cds:cds-feature-jdbcConnects the CAP Java runtime to JDBC databases through the CDS4j JDBC runtime: H2 and SQLite, which capire names for local development and CI tests rather than enterprise use.sap official, capJDBC runtime for H2 and SQLite in CAP Java
- com.sap.cds:cds-feature-postgresqlcom.sap.cds:cds-feature-postgresqlThe CAP Java feature that wires a Maven application to PostgreSQL as its datasource beside SAP HANA, with limitations capire lists: schema evolution first, and no multitenancy or extensibility yet.sap official, capPostgreSQL datasource for CAP Java applications
- com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, capMaven bill of materials pinning CAP Java module versions
- @cap-js/db-service@cap-js/db-serviceThe base every CAP database service is built on: the shared query translation and pooling that SQLite, PostgreSQL and HANA specialise rather than reimplement.sap official, capBase service shared by CAP's SQLite, PostgreSQL and HANA services
- @cap-js/hana@cap-js/hanaThe HANA database service — the production default, on the same streamlined architecture as the SQLite and PostgreSQL services.sap official, capSAP HANA database service for CAP
- @cap-js/postgres@cap-js/postgresThe PostgreSQL database service — the production option for running CAP off HANA, sharing the base service with the other three.sap official, capPostgreSQL database service for CAP
- @cap-js/sqlite@cap-js/sqliteThe SQLite service, in memory during the inner loop — which is why a CAP project runs before anyone has provisioned a database.sap official, capSQLite database service for CAP, in memory during development
- cds-mongodbcds-mongodbMongoDB as a native CAP database service, through Mongoose — CQN reads and writes, managed associations as ObjectId references, $expand resolved by populate, and cds deploy --to mongoose.independent, capMongoDB as a CAP database service through Mongoose
- @cds-pgroll/postgres@cds-pgroll/postgresThe destructive half of PostgreSQL schema evolution — DROP and RENAME, which CAP's own schema_evolution: alter will not perform — driven from the command line beside @cap-js/postgres.independent, capCLI for DROP and RENAME schema changes beside @cap-js/postgres
- @neoimpulse/cap-js-restore-model-defined-types@neoimpulse/cap-js-restore-model-defined-typesA CAP plugin that casts values back to the types the CDS model declares after a READ, for the entities you name, where the database driver returned them as strings.independent, capCAP plugin casting read values back to CDS model types
- @quadrio/cds-db2@quadrio/cds-db2A DB2 adapter for CDS, so a CAP model can be deployed to and served from DB2, last released July 2023 and still on npm while the repository it was published from has been deleted.independent, capDB2 adapter for CDS
- @sap/cds-hana@sap/cds-hanaThe SAP Cloud Application Programming Model's database adapter for SAP HANA, the package a CAP project adds to run its model on a SAP HANA database.sap official, capDatabase adapter for SAP HANA in CAP
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtime
- @sap/hana-client@sap/hana-clientSAP's own Node.js driver for SAP HANA: connect, run SQL and prepared statements, synchronously, through callbacks or as promises, over native client libraries npm installs per platform.sap official, btpSAP's Node.js driver for SAP HANA
- SAP HANASAP HANASAP’s relational database platform, which stores application data and executes SQL and SQLScript in the database, available on-premise and as the managed service SAP HANA Cloud.sap official, btpSAP's relational database platform, on-premise and in HANA Cloud
- cds-pgcds-pgA PostgreSQL adapter for SAP CDS, built by the SAP Mentors community, which gave CAP a Postgres persistence option years before @cap-js/postgres shipped.independent, capPostgreSQL adapter for SAP CDS from the SAP Mentors community
- cap-snowflakecap-snowflakeA CAP database adapter for Snowflake with OData V4 support, which the maintainer marks as early development, so its contract is expected to move.independent, capCAP database adapter for Snowflake with OData V4 support
- cds-mysqlcds-mysqlA MySQL and MariaDB database adapter for CAP that connects to a database instance and translates incoming CQL/CQN requests to it; the repository the package declares has been deleted.independent, capMySQL and MariaDB database adapter for CAP
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
latestv0.3.0
first release
releases and cadence20, ~0d median
discovered vianpm registry, The discovery pass
first seen in the atlas
ecosystem and domaincap, data-and-persistence
Flavors
Node.js
“Community adapter for connecting a Node.js CAP application to a private PostgreSQL database through SAP BTP Connectivity Service and SAP Cloud Connector.” — cap-postgres-btp-connectivity — npm README
History in the atlas
- The second reader read the connects batch of 2026-09-19 on 2026-09-22, after its acceptance, and found: tcp rested on no quote of the edge's own; the README's line on the Cloud Connector's TCP configuration is quoted now.
- The adapter required PostgreSQL, the Connectivity service and the Cloud Connector as three separate things. The connection says how they line up: the database is the target, and the service is what the connection runs through.
- external:postgresql, artifact:btp-connectivity, artifact:sap-cloud-connector
- npm: https://www.npmjs.com/package/cap-postgres-btp-connectivity
- Connects a CAP Node.js application to a PostgreSQL database that is not publicly reachable, tunnelling through BTP Connectivity and the Cloud Connector.
- First seen.
For your agent
- Ref
artifact:cap-postgres-btp-connectivity- JSON
- /artifacts/cap-postgres-btp-connectivity.json
- MCP
- Connecting an agent