Executive findings
From the 21 November 2026 landscape. Click a category card below to list its offers.
How to read the D3 views
Ports of the named Observable notebooks, bound to this report.
Capability bubbles — D3 pack (@d3/bubble-chart/2). Nested circles are categories; leaf area is illustrative emphasis.
Edge bundling — radial cluster + curveBundle (@d3/hierarchical-edge-bundling/2). Hover: orange = outgoing depends-on; cyan = incoming dependents.
Stack timeline — (@tezzutezzu/world-history-timeline). Public first-release years; every bar ends at 21 Nov 2026.
Nested treemap — (@d3/nested-treemap). Category tiles contain listed offers.
Sequences sunburst — (@kerryrodden/sequences-sunburst). Buying paths, not live usage share.
Pie / chord / Sankey / force tree — Observable pie, chord, Sankey and force-directed tree. Chord is category-to-category import counts.
World Voronoi — (@d3/world-airports-voronoi) applied to public cloud-region cities.
Nested treemap — offer catalogue
D3 treemap. Click a leaf for the detail pane. Area follows illustrative weights, not revenue share.
Sequences sunburst — buying paths
Kerry Rodden sequences sunburst. Percentages are share of mapped paths, not production traffic.
Pie — listed offers by category
Observable @d3/pie-chart/2. Counts of named offers in this snapshot, not revenue.
If the core is… you still import
Bill-of-materials check from the dependency chapter. A healthy architecture has one system of record per layer.
Compare listed cores
Side-by-side from the landscape. Click a row. This is a fit comparison, not a procurement ranking.
Categories in this report
Seven groups: platforms, hyperscalers, supply chain, observability, incident/ITSM, CNAPP/AST, automation. Click a card.
Capability bubble chart
D3 pack layout (Observable @d3/bubble-chart/2). Outer circles are categories. Click a bubble to lock the detail pane. Area is illustrative emphasis, not market share.
Hierarchical edge bundling — dependency mapping
D3 cluster + curveBundle.beta(0.85) (Observable @d3/hierarchical-edge-bundling/2). Hover a leaf: orange = outgoing depends-on; cyan = incoming dependents.
Stack timeline
World-history timeline layout (Observable @tezzutezzu/world-history-timeline). Start years are public first-release years used only for this view. Every bar ends at the 21 November 2026 snapshot.
Benchmark graphs
Index of native capability sums (leader = 100), change vs leader, stacked mix, and a pie of reported pure-play revenue. Diversified parents (Microsoft, Amazon, Google, IBM, Cisco, ServiceNow, Palo Alto, Broadcom, Oracle) are omitted from the revenue pie because they do not isolate DevOps SKU revenue.
Index chart (leader = 100)
Native profile sums for the eight inner-loop / hybrid platforms.
Change versus leader (%)
Same profile sums as percent below the listed leader.
Stacked mix — native capability contribution
Each bar is the 12-dimension 0–5 profile. Color is the dimension, not a quality rank.
Pure-play reported revenue
Latest full fiscal year from public earnings. Atlassian is work-management broader than DevOps. Datadog is observability plus security.
Compare and correlate — heatmaps
Top: native capability 0–5 for listed inner-loop platforms. Middle: qualitative coupling 1–5 among layers (not Pearson). Bottom: outer-loop specialists.
Inner-loop capability heatmap
From Table 13 of the landscape. Azure DevOps and GitHub are scored separately even though both sit under MSFT.
Layer coupling heatmap
How layers tend to move together in real toolchains. Diagonal is 5. AI coding couples tightly to SCM/CI and AppSec, weakly to ITSM.
Outer-loop heatmap
Datadog, Dynatrace, Elastic, Cisco Splunk/AppD/ThousandEyes, ServiceNow, PagerDuty.
Gap analysis
Holes from the landscape. Bar length is decision impact (5 = structural). A gap is a design problem, not a claim that a product is unusable.
| Gap | Impact | Pattern | Business impact | Gate |
|---|
Dependency mapping
Canonical toolchain, force-directed tree (Observable @d3/force-directed-tree), chord (Observable @d3/chord-diagram) and Sankey (Observable @d3/sankey/2). Drag nodes in the tree.
Canonical toolchain
Identity → git → CI → artifacts/scan → deploy → runtime → telemetry → page → change record. Open-source nodes (Git, Kubernetes, OpenTelemetry, often Argo/Flux) still appear even in an all-listed buy.
Force-directed tree
Chord — category imports
How many named depends-on edges run from one category into another.
Sankey — delivery system
Layered flow. Link width is illustrative path weight from the landscape, not traffic.
| Edge | Needs | Failure | Proof | Related |
|---|
Distribution of cloud data centers by vendor
Equal-earth projection + Delaunay Voronoi in the spirit of Observable @d3/world-airports-voronoi. Points are public commercial-region city centroids for AWS, Azure, Google Cloud, Oracle and IBM — the listed hyperscalers that DevOps pipelines actually deploy onto. Cells show nearest listed region, not exclusive coverage, building counts, or power. Land silhouette is a coarse outline for orientation only.
Catalogue
Listed DevOps and adjacent offers in this snapshot. Search across name, ticker and description.
| Short | Name | Category | Kind | Ticker | Era | Description |
|---|