Software Release & Deployment Management

BC-4210 Level 1 Software & Technology 3 providers 6 API surfaces 2 rated strong or better

Continuous integration, environment management, release engineering, feature flagging, and progressive deployment of SaaS products to production.

Software Release & Deployment Management (BC-4210) is a level-1 business capability in the Software & Technology model. The catalog holds 6 API surface(s) from 3 provider(s) that can perform some part of it, 2 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Authorities this capability cites

Cited by the capability model itself. These frameworks are referenced, never redistributed, and citing one does not imply its owner endorses this listing.

Sub-capabilities

Continuous Integration Management BC-4210.10

Build pipelines, artefact production, and pipeline policy enforcement that keep the integrated product continuously buildable.

no catalog coverage

Environment Management BC-4210.20

Provisioning and stewardship of non-production environments used for development, integration, and pre-production validation.

1 provider, 1 API surface

Release Engineering Management BC-4210.30

Cadence, versioning, branching, and release-note discipline for software releases.

no catalog coverage

Deployment Orchestration BC-4210.40

Strategies for delivering software changes to production safely and with controlled blast radius.

1 provider, 1 API surface

Feature Flag Management BC-4210.50

Lifecycle and runtime control of feature flags used to decouple deploy from release and target features to cohorts.

2 providers, 2 API surfaces

Configuration & Secrets Management BC-4210.60

Management of runtime configuration values and secrets consumed by product services.

1 provider, 2 API surfaces

Production Change Authorisation BC-4210.70

Pre-deployment review, deployment-window governance, and authorisation of human access to production.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Strong 2 Solid coverage with minor gaps
MedusaFeature Flags1 API62.7LeafLinkSplitIO1 API59.4
Developing 1 Usable, with meaningful gaps to close
Platform.shDeploymentEnvironmentEnvironment VariablesProject Variables4 APIs52.9

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Software Release & Deployment Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →