ServiceServiceA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPPublished 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 Software-as-a-Service Provisioning service
Registers a multitenant application so that subaccounts can subscribe to it, and calls the application back on every subscribe and unsubscribe.
Where it sits
Lives in
Provides
MultitenancyCAPBTPMultitenancyServing 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.
Serves
Designs
Multitenant SaaS Application using CAPMultitenant SaaS Application using CAPsubscription lifecycle
What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
As a service
- Plans
- 1
- Regions
- 46
Connections
Group by
NodeRelationBasis
Functional
MultitenancyMultitenancyServing many tenants from one deploymentSAP and community, narrow by design
provides
authored
provides Multitenancy
Serving many tenants from one deployment
Download
Others providing
Compare all 7 on the Multitenancy page →MultitenancyMultitenancyServing 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
- com.sap.cds:cds-feature-mtcom.sap.cds:cds-feature-mtThe 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 containers
- 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-community/mtx-tool@cap-js-community/mtx-toolCLI for operating multitenant CAP applications — inspecting, upgrading and repairing tenants across a landscape.community org, capCLI for operating tenants of multitenant CAP applications
- @sap/cds-mtxs@sap/cds-mtxsMultitenancy, tenant provisioning and model extensibility for CAP.sap official, capMultitenancy, tenant provisioning and extensibility for CAP
- @sap/cds-oyster@sap/cds-oysterRuns 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 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
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
discovered viaSAP-samples/btp-service-metadata · btp-service-metadata
first seen in the atlas
ecosystem and domainbtp, operations-and-runtime
History in the atlas
- First seen.
For your agent
- Ref
artifact:btp-saas-provisioning- JSON
- /artifacts/btp-saas-provisioning.json
- MCP
- Connecting an agent