PackagePackagetypeA library you install and call yourself.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
@sap/cds-mtxs
Multitenancy, tenant provisioning and model extensibility for CAP.
Schema evolutionCAPSchema evolutioncapabilityGetting a model change into a database that already holds data, in every tenant, without losing any of it. Generating the initial schema and migrating one that already holds data are often treated as the same step.MultitenancyCAPMultitenancycapabilityServing many tenants from one deployment — onboarding, tenant-isolated data, per-tenant schema deployment and the operational tooling around it. It is decided once, before anything is built, and narrows the artifacts in almost every capability downstream: most sharply in [caching](capability:caching) and anything else holding state in process.Tenant extensibilityCAPTenant extensibilitycapabilityLetting a customer extend the model of a running SaaS application with extra fields and entities per tenant, without forking the application, as distinct from extending the application's code for every customer at once.Feature togglesCAPFeature togglescapabilityTurning behaviour on and off per tenant or per user at runtime, without redeploying, and knowing which toggles are live. System-level switches for delivered objects and runtime flags for unfinished features share the name.
declared, Where the library runs once installed: inside its host (loaded into the CAP application, installed into the ABAP system, loaded by the UI5 application), in a program of your own, or only at build time.
Distributed through
does not say
declared, How it is installed, as its documentation tells a user to get it.
Connections5
Group by
NodeRelationConditionBasis
Functional4
Feature togglesFeature togglescapabilityTurning behaviour on and off per tenant or user at runtimeSAP and community, narrow by design
→provides
Serves feature-toggled CDS aspects from fts/ subfolders when cds.requires.toggles is switched on, activating them per tenant, user or request.
provides Feature toggles
Functional, stated
For
Serves feature-toggled CDS aspects from fts/ subfolders when cds.requires.toggles is switched on, activating them per tenant, user or request.
Basis
“Switch on feature toggle support by adding cds.requires.toggles: true.”Feature Toggles — capire, checked “Add a subfolder per feature to folder fts and put .cds files into it.”Feature Toggles — capire, checked
stated
provides Feature toggles
Functional, stated
For
Serves feature-toggled CDS aspects from fts/ subfolders when cds.requires.toggles is switched on, activating them per tenant, user or request.
Basis
“Switch on feature toggle support by adding cds.requires.toggles: true.”Feature Toggles — capire, checked “Add a subfolder per feature to folder fts and put .cds files into it.”Feature Toggles — capire, checked
Turning behaviour on and off per tenant or user at runtime
MultitenancyMultitenancycapabilityServing many tenants from one deploymentSAP and community, narrow by design
→provides
Tenant provisioning, tenant-isolated persistence and per-tenant model deployment, served from an MTX sidecar once cds add multitenancy has switched it on.
provides Multitenancy
Functional, stated
For
Tenant provisioning, tenant-isolated persistence and per-tenant model deployment, served from an MTX sidecar once cds add multitenancy has switched it on.
Basis
“CAP has built-in support for multitenancy with the @sap/cds-mtxs package.”Deploy Multitenant SaaS Applications — capire, checked
stated
provides Multitenancy
Functional, stated
For
Tenant provisioning, tenant-isolated persistence and per-tenant model deployment, served from an MTX sidecar once cds add multitenancy has switched it on.
Basis
“CAP has built-in support for multitenancy with the @sap/cds-mtxs package.”Deploy Multitenant SaaS Applications — capire, checked
Serving many tenants from one deployment
Schema evolutionSchema evolutioncapabilityGetting a model change into a database that already holds dataSAP and community, narrow by design
→provides
none
authored
provides Schema evolution
Functional, authored
Getting a model change into a database that already holds data
Tenant extensibilityTenant extensibilitycapabilityLetting a customer extend a running SaaS model per tenantSAP and community, unassessed
→provides
Serves the ExtensibilityService a subscriber's developer pulls the base model from and pushes extend and annotate definitions to, switched on with cds add extensibility.
provides Tenant extensibility
Functional, stated
For
Serves the ExtensibilityService a subscriber's developer pulls the base model from and pushes extend and annotate definitions to, switched on with cds add extensibility.
Basis
“Library for multitenancy, feature toggle and extensibility support for the SAP Cloud Application Programming Model (CAP).”@sap/cds-mtxs — README, checked “It adds an @sap/cds-mtxs package dependency”Extending SaaS Applications — capire, checked
stated
provides Tenant extensibility
Functional, stated
For
Serves the ExtensibilityService a subscriber's developer pulls the base model from and pushes extend and annotate definitions to, switched on with cds add extensibility.
Basis
“Library for multitenancy, feature toggle and extensibility support for the SAP Cloud Application Programming Model (CAP).”@sap/cds-mtxs — README, checked “It adds an @sap/cds-mtxs package dependency”Extending SaaS Applications — capire, checked
Letting a customer extend a running SaaS model per tenant
Technical1
com.sap.cds:cds-feature-mtcom.sap.cds:cds-feature-mtpackageMultitenancy for CAP Java: tenant lifecycle and per-tenant containerssap official, cap
←optionally used by
if Tenant CDS model extensions are used
optionally used by com.sap.cds:cds-feature-mt
Technical, derived, through inverted from its requires edge
If
Tenant CDS model extensions are used.
Basis
“Note that switching the tenant in the context is a quite expensive operation as CDS model data might need to be fetched from MTX sidecar in case of tenant extensions.”Multitenancy — capire, checked
derived
optionally used by com.sap.cds:cds-feature-mt
Technical, derived, through inverted from its requires edge
If
Tenant CDS model extensions are used.
Basis
“Note that switching the tenant in the context is a quite expensive operation as CDS model data might need to be fetched from MTX sidecar in case of tenant extensions.”Multitenancy — capire, checked
Multitenancy for CAP Java: tenant lifecycle and per-tenant containers
Derived from the package name. No recipe recorded; the README has the configuration.
Learn more2
Readings
Custom Business Logic Extensibility in CAP (CDS-Oyster)Custom Business Logic Extensibility in CAP (CDS-Oyster)talkA Devtoberfest 2026 session walking @sap/cds-oyster — at version 0.55, with 1.0 stated for Q4 — end to end on a multitenant xtravels, from the application developer's side and the extension developer's side. The application developer adds a submit-for-review action to the status flow and opens exactly one surface for custom code: a separate extension service marked as extensible code, holding a no-op validate action and two read-only helper entities, which the host application calls before the status change; nothing else is extensible, because the annotation defaults to false. The extension developer works in a project whose base model came from cds pull, with test data, a server.js and types from @cap-js/cds-typer added so the UI and code completion work, debugs the handler locally and pushes it as an @sap/cds-mtxs extension, after which the next request rejects a travel over the policy limit without a restart — the code having been stored as an annotation in the tenant's model and run in a Rust WebAssembly sandbox with no database connection, whose queries go back to the CAP runtime as CQL strings, which is tenant extensibility extended from fields to logic.published 2026-10-09Nick Josipovic, DJ Adams, YouTube — SAP Developers playlists
Developing CAP java/node.js mixed mono Multitenant SaaS Applications with Shared DatabaseDeveloping CAP java/node.js mixed mono Multitenant SaaS Applications with Shared DatabaseblogTwo CAP projects, one Java and one Node.js, in one npm workspace sharing a single tenant database. The interesting part is which sidecar wins: both sub-projects get an MTX sidecar, both have cds.xt.SaasProvisioningService switched off, and a third onboarding project keeps provisioning to itself. Configuration listings rather than prose, and it assumes you already know why you would want this.xuelong, published 2025-01-08xuelong, SAP Community
What changed
v2.0.1
@sap/instance-manager is no longer supported as a fallback to the built-in Service Manager client, which is the only client used from this release.
Makes stale:
Multitenancy setups that keep @sap/instance-manager in the project as the way @sap/cds-mtxs creates tenant containers.
Schema evolutionSchema evolutioncapabilityGetting a model change into a database that already holds data, in every tenant, without losing any of it. Generating the initial schema and migrating one that already holds data are often treated as the same step.SAP and community, narrow by design
@cap-js-community/common@cap-js-community/commonpackageSix independent features for CAP services in one package: replication cache, migration check, rate limiting, a Redis client broker, a local HTML5 repository and a CDM builder.community org, capSix CAP features in one package, from replication cache to rate limitsfrom CAP
cds-dbmcds-dbmbuild-toolA delta deployment and migration tool for CAP on PostgreSQL that diffs the live schema against a reference schema with Liquibase and applies the change, never dropping tables by default.independent, capDelta deployment and migrations for CAP database adaptersfrom CAP
@quadrio/cds-dbm@quadrio/cds-dbmcliA published fork of cds-dbm — deploy, load, diff and drop as CDS command-line tasks for relational databases the core does not natively support.independent, capFork of cds-dbm with deploy, load, diff and drop tasksfrom CAP
@sap/cds@sap/cdspackageThe 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 runtimefrom CAP
@sap/hdi-deploy@sap/hdi-deploypackageThe Node.js deployer for SAP HANA Deployment Infrastructure: it writes a database module's design-time files into an HDI container as a delta, and it is what cds deploy runs for SAP HANA.sap official, capNode.js deployer for SAP HANA Deployment Infrastructure containersfrom CAP
MultitenancyMultitenancycapabilityServing many tenants from one deployment — onboarding, tenant-isolated data, per-tenant schema deployment and the operational tooling around it. It is decided once, before anything is built, and narrows the artifacts in almost every capability downstream: most sharply in caching and anything else holding state in process.SAP and community, narrow by design
SAP Software-as-a-Service Provisioning serviceSAP Software-as-a-Service Provisioning serviceserviceRegisters a multitenant application so that subaccounts can subscribe to it, and calls the application back on every subscribe and unsubscribe.sap official, btpRegisters a multitenant application for subaccount subscriptionsfrom BTP/BAIP
com.sap.cds:cds-feature-mtcom.sap.cds:cds-feature-mtpackageThe CAP Java feature that makes a Maven application multitenant aware: tenant lifecycle events, per-tenant database containers, and the wiring to the Node.js MTX sidecar.sap official, capMultitenancy for CAP Java: tenant lifecycle and per-tenant containersfrom CAP
com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bompackageThe 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 versionsfrom CAP
@cap-js-community/mtx-tool@cap-js-community/mtx-toolcliCLI for operating multitenant CAP applications — inspecting, upgrading and repairing tenants across a landscape.community org, capCLI for operating tenants of multitenant CAP applicationsfrom CAP
@sap/cds-oyster@sap/cds-oystercds-pluginRuns tenant-specific extension code inside a WebAssembly sandbox, so a SaaS application can accept custom logic from a customer without running it unguarded.sap official, capWebAssembly sandbox for tenant-specific extension code in CAPfrom CAP
@sap/cds@sap/cdspackageThe 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 runtimefrom CAP
Tenant extensibilityTenant extensibilitycapabilityLetting a customer extend the model of a running SaaS application with extra fields and entities per tenant, without forking the application, as distinct from extending the application's code for every customer at once.SAP and community, unassessed
dynamic-external-cds-joindynamic-external-cds-joincds-pluginA CAP plugin for SaaS extension scenarios that joins external entities with internal tables at query time; its declared repository is not publicly reachable.independent, capCAP plugin joining external entities with internal tables at queryfrom CAP
Feature togglesFeature togglescapabilityTurning behaviour on and off per tenant or per user at runtime, without redeploying, and knowing which toggles are live. System-level switches for delivered objects and runtime flags for unfinished features share the name.SAP and community, narrow by design
FeaturetoggleFeaturetogglepackageA feature toggle framework for ABAP that ships an unfinished feature to production deactivated: toggles declared as class attributes, branched on in code and switched in a UI5 GUI.independent, abapFeature toggle framework for ABAP with a UI5 GUIfrom ABAP
SAP Feature Flags serviceSAP Feature Flags serviceserviceBoolean and string flags toggled in a dashboard and read by an application at runtime over a binding, with a cache in the client so a flip does not need a deploy or a round-trip per check.sap official, btpBoolean and string flags read by applications at runtimefrom BTP/BAIP
com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bompackageThe 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 versionsfrom CAP
@cap-js-community/feature-toggle-library@cap-js-community/feature-toggle-librarypackageLive-updatable feature toggles for CAP applications, backed by Redis.community org, capLive-updatable feature toggles for CAP, backed by Redisfrom CAP
abap-feature-toggleabap-feature-togglepackageA feature toggle for ABAP: a toggle is an entry on the view ZFEAT_TOGGLE, switched there rather than by a deployment, and code reads its state with is_active.independent, abapFeature toggle for ABAP read via is_active on view ZFEAT_TOGGLEfrom ABAP
cds-feature-togglecds-feature-togglecds-pluginA feature-toggle pattern for CAP CDS from before the core had one, sitting at the CDS layer rather than the tenant-extensibility layer of @sap/cds-mtxs feature toggles.independent, capFeature-toggle pattern for CAP CDSfrom CAP