The Category Fracture Index
The registry shows more vendors and little consolidation across the categories we track. Leaders need to understand how each category is dividing as they decide which tools fit their work.
The Software Innovators series covers software leaders from 1969 through 2026. Every legacy category we examined had more vendors than in the preceding wave; none consolidated.
Four waves: mainframe to client-server, on-prem to SaaS, SaaS to cloud-native, and the current shift from cloud-native to AI-native. Tracked vendor counts continued to rise.
Tools tracked in the Airframe registry across categories affected by AI. The count increased last quarter.
Peer deployment case studies indexed in the Airframe corpus and used to assess category trajectories.
The fracture map
These twelve categories cover the registry's rolling window. The charts are indexed, so they show relative change rather than absolute counts. All categories rise, and most move above the category median during the AI wave.
When a category doubles, new vendors challenge incumbents. When it multiplies many times within the same window, vendor evaluation becomes harder: procurement teams cannot reasonably assess every option at once. We call that pattern category fracture.
The tracked legacy categories expanded within roughly the same window. Observability fractured first as the infrastructure surface expanded, followed by data warehousing, then analytics, workflow, customer support, content, and code. Later-moving categories have curves that have not yet bent; that does not establish that they will consolidate.
There is no “market leader” in a fractured category. There is only which fracture you are inside.
Category of the quarter, code copilots.
Code copilots have grown from a small category into a field of funded vendors with different levels of autonomy, integration, and trust. We map them by developer autonomy and IDE integration depth.
The term code copilot once described one product, then a handful. It now covers many venture-backed vendors and an expanding open-source field. Broad access to foundation-model APIs helps explain the rapid growth: a team can assemble a plausible copilot in a single quarter.
Buyers need to understand where a tool sits on the map. Its developer autonomy and IDE integration depth affect licensing, security posture, and the team required to adopt it.
Deployment case studies show new enterprise spending on editor-native tools with high autonomy, where vendors are still revising their trust models. Remote agents form a newer segment. Most incumbents remain in ambient helpers, where the registry records attrition.
The deployment corpus suggests that inline completion and chat with a codebase are now baseline features. Autonomous task execution, codebase-wide indexing and memory, long-horizon refactoring, policy-driven tool scoping, and prompt-and-output audits still differentiate vendors. The registry records tools with earlier features being displaced within a quarter or two after a newer entrant reaches the same engineering organization.
This map helps buyers compare how tools fit their work. It is not a vendor ranking.
Tracked categories, ordered by fracture.
Categories are ordered by their illustrative expansion curves and the registry's tracked footprint. The ordering is directional and makes no market-share claim.
The Airframe registry is an AI-maintained tool index grounded in the Software Innovators series (2,398 software leaders, 1969 through 2026) and 174,000+ peer deployment case studies. A vendor can belong to multiple categories. We include it for a given category and year when at least one ingested deployment signal, funding record, or product artifact supports active status. Counts reflect the tracked footprint and are directional, not audited.
Assess your software stack.
Airframe compares your registry, tools, owners, and spend with the cohort. A thirty-minute call scopes the work.