CDS pluginCDS plugintypeInstalls 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 →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-oyster
Runs tenant-specific extension code inside a WebAssembly sandbox, so a SaaS application can accept custom logic from a customer without running it unguarded.
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.
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.
Derived: the instrument's applicability matches this artifact, checked
§ 1License. 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.
§ 2Intellectual 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.
§ 3Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
declared, How the plugin is installed into a CAP project, as its documentation says., read npm add @sap/cds-oyster — @sap/cds-oyster — README, 2026-10-18
Connections1
Group by
NodeRelationConditionBasis
Functional1
MultitenancyMultitenancycapabilityServing many tenants from one deploymentSAP and community, narrow by design
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
Everything new: Try out the latest features in CAPEverything new: Try out the latest features in CAPtalkCAP (@sap/cds) gains the features this hands-on session works through: declarative constraints, which is the input validation concern, status flows as status transition flows, a cds REPL, extensibility through @sap/cds-oyster, and HCQL, which SAP's abstract calls CAP's native query-over-HTTP protocol, after an opening stretch of AI-driven app development. The abstract names the features and stops there; what each one does is not described. A TechEd 2026 hands-on session (Wednesday 28 October, Berlin), presented by Daniel Hutzel, Daniel Schlachter, Marc Huber and Tim Back, written here from SAP's abstract; the recording is not yet published.Daniel Hutzel, Daniel Schlachter, SAP TechEd — session catalogue
What changed
v0.5.1
The runtime option is now sandbox, with wasm for oyster and mocked for debug; development defaults to mocked and production allows only wasm. extensibleAnnotation defaults to true, so @extensible.code decides which code extensions are allowed instead of the extension allow-list, and the maxResultSize option and req.user in the sandbox are removed.
Makes stale:
Configuration that sets runtime to oyster, or that relies on extension-allowlist to gate code extensions.
1 earlier
v0.2.0
Extension code can no longer call a bound action as this.action(), only unbound actions, and before-READ extension handlers are removed. The same release switches to Oyster v2.
Makes stale:
Extension examples that call this.action() or register a before-READ handler.
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-mtxs@sap/cds-mtxspackageMultitenancy, tenant provisioning and model extensibility for CAP.sap official, capMultitenancy, tenant provisioning and extensibility for 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
Runs tenant-specific extension code inside a WebAssembly sandbox, so a SaaS application can accept custom logic from a customer without running it unguarded.