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 Feature Flags service
Boolean 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.
Where it sits
Lives in
Provides
Feature togglesCAPBTPFeature togglesTurning 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.
Serves
What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
As a service
- Plans
- 2
- Regions
- 46
- Support component
- BC-CP-CF-FEATUREFLG
Connections
Group by
NodeRelationBasis
Functional
Feature togglesFeature togglesTurning behaviour on and off per tenant or user at runtimeSAP and community, narrow by design
provides
authored
provides Feature toggles
Turning behaviour on and off per tenant or user at runtime
Download
Learn more
Readings
- Streamline User Targeting with Segments in SAP Feature FlagsStreamline User Targeting with Segments in SAP Feature FlagsWalks through segments in the SAP Feature Flags service: reusable, named user lists — up to 1,000 direct user IDs or 15 attribute-based conditional rules per segment — referenced across every feature flag in a service instance instead of redefined per flag. Covers creating a segment from the Feature Flags Dashboard and the per-instance limit of 20 segments, plus the safeguard that a segment in use cannot be deleted.Maksimiliana, published 2026-02-05Maksimiliana, SAP Community
What’s New
from SAP Help Portal, readhelp.sap.com/whats-new, Feature Flags ServiceSAP’s wordsOn SAP Help Portal
14 entries from to , counted per month.
Custom X.509 Certificates
Service Binding Limit: 400 per Instance
Reusable User Segments for Feature Targeting
Issues Editing Feature Flags due to Legacy Access Token Signing Key
Deprecation of basic authentication
Additional properties
Flag dependencies
Custom flag attributes
Service Instance Sharing
SAP Fiori Horizon theme
Environments
Feature Flags Dashboard
Evaluate with a certificate-protected token
Keep existing feature flags unchanged during import
Others providing
Compare all 5 on the Feature toggles page →Feature togglesFeature togglesTurning 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
- 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/feature-toggle-library@cap-js-community/feature-toggle-libraryLive-updatable feature toggles for CAP applications, backed by Redis.community org, capLive-updatable feature toggles for CAP, backed by Redis
- @sap/cds-mtxs@sap/cds-mtxsMultitenancy, tenant provisioning and model extensibility for CAP.sap official, capMultitenancy, tenant provisioning and extensibility for CAP
- cds-feature-togglecds-feature-toggleA 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 CDS
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-feature-flags- JSON
- /artifacts/btp-feature-flags.json
- MCP
- Connecting an agent