brianletort.ai
Industry

Companion view

The AI Market Reference Architecture.

A living taxonomy for AI market boundaries, leaders, metrics, and model cards.

Cloud had IaaS, PaaS, and SaaS. AI needs a different layer cake: infrastructure, model portfolios, raw data management, AI-ready data, developer tools, agent tools, and commercial tools. The strategic fight is whether SaaS keeps owning the data, or whether enterprises own their data and expose it safely to agents.

7

Categories

50

Seeded players

19

Leaders

21

Metrics

Reference architecture

The layer cake: from GPUs to commercial tools.

The new boundary is data access. Models matter, but the market structure forms around who owns the data, who makes it AI-ready, who builds with it, which agents can act on it, and which commercial tools survive on top.

L1 Infrastructure

Layer 1 — AI Infrastructure

Physical and cloud substrate for AI: GPUs, accelerators, networking, datacenters, power, storage, and managed compute capacity.

Leaders

Amazon Web Services logoAmazon Web ServicesBroadcom logoBroadcomGoogle logoGoogleMicrosoft logoMicrosoft

Control points

compute / power / networking / cloud_capacity

Watch

Alibaba logoAlibabaAMD logoAMDCloudflare logoCloudflare

L2 Models

Layer 2 — Model Portfolio

Foundation, frontier, open-weight, specialist, and routed model portfolios that provide the intelligence primitives consumed by higher layers.

Leaders

Amazon Web Services logoAmazon Web ServicesAnthropic logoAnthropicDatabricks logoDatabricksGoogle logoGoogle

Control points

weights / benchmarks / token_pricing / model_policy / routing

Watch

Alibaba logoAlibabaDeepSeek AI logoDeepSeek AIHeyGen logoHeyGen

L3 Data Mgmt

Layer 3 — Data Management

Raw systems of record, warehouses, lakehouses, operational databases, and document stores that hold enterprise data before it is shaped for AI use.

Leaders

Databricks logoDatabricksGoogle logoGooglePalantir logoPalantirSalesforce logoSalesforce

Control points

source_data / governance / lineage / access_control

Watch

Alibaba logoAlibabaElastic logoElasticGlean logoGlean

L4 AI Data

Layer 4 — AI-Ready Data

Processed, indexed, embedded, retrievable, policy-wrapped, and API-exposed data that can be consumed directly by models and agents.

Leaders

Amazon Web Services logoAmazon Web ServicesDatabricks logoDatabricksHugging Face logoHugging FacePinecone logoPinecone

Control points

embeddings / vector_index / retrieval / api_gateway / context_layer

Watch

Cloudflare logoCloudflareElastic logoElasticGlean logoGlean

L5 Dev Tools

Layer 5 — Developer Tools

Build tools for humans and agents creating software: IDE copilots, coding agents, CLI agents, context management, orchestration, evals, and tool harnesses.

Leaders

Amazon Web Services logoAmazon Web ServicesAnthropic logoAnthropicGitHub logoGitHubHugging Face logoHugging Face

Control points

developer_workflow / context_management / orchestration / tool_harness / evals

Watch

Cloudflare logoCloudflareCursor logoCursorVercel logoVercel

L6 Agents

Layer 6 — Agent Tools

Agent runtimes and operational tools that run scheduled, triggered, multi-agent, tool-using, and exception-escalating work.

Leaders

Anthropic logoAnthropicCrowdStrike logoCrowdStrikeGitHub logoGitHubOpenAI logoOpenAI

Control points

tools / memory / permissions / task_execution / human_review

Watch

Cursor logoCursorHarvey logoHarveySierra logoSierra

L7 Commercial

Layer 7 — Commercial Tools

Finished point solutions and vertical AI tools: video, voice, legal, sales, research, support, writing, and other specialist business outcomes.

Leaders

Adobe logoAdobeAnthropic logoAnthropicCrowdStrike logoCrowdStrikeGoogle logoGoogle

Control points

workflow_distribution / proprietary_context / seats / vertical_expertise

Watch

Glean logoGleanHarvey logoHarveyHeyGen logoHeyGen

Boundary rule

Vendors get one primary layer by market role, plus secondary roles when they span the layer cake. Confidence is explicit so category ambiguity does not masquerade as precision.

Confidence distribution

19 high, 27 medium, 4 low-confidence placements.

Low confidence means useful signal, not settled category leadership.

Market scorecard

Quantitative signals that can survive a refresh cycle.

Each layer gets metrics that can be revalidated from public sources. When the data is sparse, the chart says so instead of inventing a false leaderboard.

Layer 1 — AI Infrastructure

Data-center capex growth: 53% YoY

high

AI infrastructure remains capital constrained; capex direction is the first-order signal for who can supply capacity.

Layer 2 — Model Portfolio

SWE-bench performance jump: 71.7%

high

Software-engineering capability moved from toy benchmark to enterprise relevance, changing the model layer's practical value.

Layer 3 — Data Management

Organizations using AI: 78%

high

More organizational AI use increases pressure to expose governed systems of record to agents without copying everything into SaaS silos.

Layer 4 — AI-Ready Data

Vector and hybrid retrieval availability: available across Pinecone, Weaviate, Milvus, MongoDB, Elastic

high

Retrieval infrastructure is now broad enough to treat AI-ready data as a separate layer between raw datastores and agent execution.

Layer 5 — Developer Tools

Coding tools as leading GenAI application category: top enterprise spend category

medium

Developer tools are the first place where AI changes production work, not only information retrieval.

Layer 6 — Agent Tools

Agent startups tracked: 170+

medium

Agentic workflows are a distinct market structure, not just another app feature.

Layer 7 — Commercial Tools

GenAI application spend: $19B+

medium

Commercial tools are already a major value-capture zone, but the durable winners need workflow depth that survives model-provider expansion.

Metrics by category

What we track, and how often it decays.

Each category carries a small metric basket: one or two headline indicators plus supporting signals. The point is not to rank everything every day; it is to keep a durable public watchlist with explicit confidence and refresh cadence.

L1 Infrastructure

Layer 1 — AI Infrastructure

3 signals

  • Data-center capex growth

    capital / Q1 2025

    53% YoY

    high / refresh 90d

    AI infrastructure remains capital constrained; capex direction is the first-order signal for who can supply capacity.

  • High-end accelerated servers

    mix_shift / 2025 forecast

    > one-third of total data-center capex

    medium / refresh 90d

    Accelerator-heavy systems are no longer a niche line item; they are a large share of the data-center investment stack.

  • Data-center capex forecast

    capital / 2025 forecast

    30% growth

    high / refresh 90d

    Sustained infrastructure expansion keeps the AI substrate layer strategic, not commodity.

L2 Models

Layer 2 — Model Portfolio

3 signals

  • SWE-bench performance jump

    capability / 2024 vs 2023

    71.7%

    prior 4.4%

    high / refresh 180d

    Software-engineering capability moved from toy benchmark to enterprise relevance, changing the model layer's practical value.

  • Open-weight vs closed-weight performance gap

    capability / 2024 vs prior year

    1.70%

    prior 8.04%

    high / refresh 180d

    Narrowing gaps increase buyer leverage and make openness a strategic dimension, not only a developer preference.

  • Live model price, latency, speed, and context comparisons

    efficiency / live

    available

    high / refresh 30d

    Model leadership should be benchmark-adjusted by cost and latency, not read from capability leaderboards alone.

L3 Data Mgmt

Layer 3 — Data Management

3 signals

  • Organizations using AI

    adoption / 2024 vs 2023

    78%

    prior 55%

    high / refresh 365d

    More organizational AI use increases pressure to expose governed systems of record to agents without copying everything into SaaS silos.

  • Generative AI in at least one business function

    adoption / 2024 vs 2023

    71%

    prior 33%

    high / refresh 365d

    Business-function adoption makes source-data access, lineage, and permissions first-class AI architecture concerns.

  • Enterprise GenAI spend

    spend / 2025 estimate

    $37B

    medium / refresh 365d

    Enterprise AI spend eventually lands against data platforms, not only model APIs and point tools.

L4 AI Data

Layer 4 — AI-Ready Data

3 signals

  • Vector and hybrid retrieval availability

    capability / current

    available across Pinecone, Weaviate, Milvus, MongoDB, Elastic

    high / refresh 90d

    Retrieval infrastructure is now broad enough to treat AI-ready data as a separate layer between raw datastores and agent execution.

  • Model and context gateway pattern

    architecture / 2026

    emerging

    medium / refresh 90d

    API gateways, model routers, and context wrappers become the control plane for which agents can consume which data.

  • Open-model serving demand proxy

    adoption / live

    downloads and model-card activity

    medium / refresh 30d

    Open ecosystem activity is a maintainable proxy for AI-ready data and serving demand where vendors do not disclose token volume.

L5 Dev Tools

Layer 5 — Developer Tools

3 signals

  • Coding tools as leading GenAI application category

    spend / 2025 estimate

    top enterprise spend category

    medium / refresh 365d

    Developer tools are the first place where AI changes production work, not only information retrieval.

  • Coding agents and CLI tools

    workflow / 2026

    Cursor / Codex / Claude Code / OpenCode

    medium / refresh 90d

    Build tools are moving from autocomplete to agent supervision, with context management and tool harnesses becoming the real differentiators.

  • Context management as build substrate

    architecture / 2026

    emerging

    medium / refresh 90d

    The durable build-tool layer may be less about the IDE and more about how context, tools, repo state, and review loops are packaged for agents.

L6 Agents

Layer 6 — Agent Tools

3 signals

  • Agent startups tracked

    market_structure / March 2025

    170+

    medium / refresh 180d

    Agentic workflows are a distinct market structure, not just another app feature.

  • Agent startup funding

    funding / 2024

    $3.8B

    medium / refresh 365d

    Funding growth signals that investors view delegated work as a separate value pool.

  • Public production-readiness disclosure

    disclosure / 2026

    uneven

    medium / refresh 90d

    Human-in-loop controls, tool permissions, and audit logs should carry as much weight as demos.

L7 Commercial

Layer 7 — Commercial Tools

3 signals

  • GenAI application spend

    spend / 2025 estimate

    $19B+

    medium / refresh 365d

    Commercial tools are already a major value-capture zone, but the durable winners need workflow depth that survives model-provider expansion.

  • Microsoft 365 Copilot paid enterprise seats

    adoption / April 2026

    20M+

    high / refresh 90d

    Seat adoption is the cleanest public signal for commercial AI distribution through incumbent software suites.

  • Specialist tool pressure

    market_structure / 2026

    model providers moving upward

    medium / refresh 90d

    OpenAI and Anthropic moving into implementation services raises the bar for point solutions: they need proprietary workflow depth, data access, or domain-specific trust.

Monthly position

Leaders, challengers, and direction of travel.

This is the living part of the taxonomy: a monthly read of who is gaining, holding, or losing position inside each category. Scores are editorial indices, not market share, and they should be recalibrated as better public signals arrive.

L1 Infrastructure

Layer 1 — AI Infrastructure

2026-03 / 2026-04 / 2026-05

  • NVIDIA logo

    NVIDIA

    leader

    96

    position index

    Merchant accelerator leadership remains the infrastructure benchmark; score rises with continued capex pull-through and networking attach.

  • Microsoft logo

    Microsoft

    leader

    89

    position index

    Infrastructure position strengthens when Azure capacity and Copilot distribution reinforce each other.

  • Amazon Web Services logo

    Amazon Web Services

    leader

    88

    position index

    Cloud capacity and procurement breadth keep AWS in the leader band.

  • AMD logo

    AMD

    challenger

    70

    position index

    Challenger score improves when substitution pressure and cloud availability become more credible.

L2 Models

Layer 2 — Model Portfolio

2026-03 / 2026-04 / 2026-05

  • OpenAI logo

    OpenAI

    leader

    94

    position index

    Frontier capability plus product habit keeps OpenAI in the leader band; open-weight pressure shows up as efficiency pressure, not displacement.

  • Anthropic logo

    Anthropic

    leader

    91

    position index

    Enterprise trust and agentic coding strength keep Anthropic gaining within the model layer.

  • Google logo

    Google

    leader

    89

    position index

    Google benefits from simultaneous model, cloud, and consumer distribution signals.

  • Hugging Face logo

    Hugging Face

    leader

    82

    position index

    Open-model distribution and model-card gravity keep Hugging Face in the platform leader band.

  • DeepSeek AI logo

    DeepSeek AI

    challenger

    81

    position index

    DeepSeek remains the open-weight efficiency challenger forcing price and training-capital discipline.

L3 Data Mgmt

Layer 3 — Data Management

2026-03 / 2026-04 / 2026-05

  • Databricks logo

    Databricks

    leader

    88

    position index

    Governed data gravity keeps Databricks central as enterprise AI shifts from experiments to operated systems.

  • Snowflake logo

    Snowflake

    leader

    84

    position index

    Snowflake remains a leader when AI starts from governed enterprise data.

L4 AI Data

Layer 4 — AI-Ready Data

2026-03 / 2026-04 / 2026-05

  • Pinecone logo

    Pinecone

    leader

    84

    position index

    Pinecone anchors the vector-store portion of the AI-ready data layer.

  • Weaviate logo

    Weaviate

    challenger

    74

    position index

    Weaviate gains when teams want open, hybrid, and self-controlled retrieval infrastructure.

  • Vercel logo

    Vercel

    challenger

    71

    position index

    Runtime position improves as model routing becomes part of application deployment rather than a separate platform decision.

  • Cloudflare logo

    Cloudflare

    challenger

    69

    position index

    Edge distribution and security posture keep Cloudflare relevant as inference gets closer to users and policies.

  • Together AI logo

    Together AI

    challenger

    68

    position index

    Open-model serving demand keeps Together AI in the runtime challenger set.

L5 Dev Tools

Layer 5 — Developer Tools

2026-03 / 2026-04 / 2026-05

  • Anthropic logo

    Anthropic

    leader

    85

    position index

    Claude Code makes Anthropic one of the most important movers in build tooling, not only model APIs.

  • GitHub logo

    GitHub

    leader

    84

    position index

    GitHub owns a high-frequency execution surface where agentic behavior can become daily workflow rather than demo.

  • OpenAI logo

    OpenAI

    leader

    82

    position index

    Codex and implementation services move OpenAI upward from model portfolio into the developer-tools layer.

  • Cursor logo

    Cursor

    challenger

    77

    position index

    Cursor gains as coding remains the cleanest category for visible AI productivity and agentic workflow adoption.

  • LangChain logo

    LangChain

    specialist

    66

    position index

    Orchestration and observability mindshare rises as multi-model systems become more common.

L6 Agents

Layer 6 — Agent Tools

2026-03 / 2026-04 / 2026-05

  • Anthropic logo

    Anthropic

    leader

    87

    position index

    Claude's coding and tool-use posture keeps Anthropic central to early production agentic workflows.

  • ServiceNow logo

    ServiceNow

    leader

    80

    position index

    ServiceNow is positioned where delegated action meets governed enterprise process.

  • Hermes logo

    Hermes

    specialist

    70

    position index

    Hermes represents owned-agent operations over personal infrastructure and owned data, with humans paged only on exception.

  • Sierra logo

    Sierra

    challenger

    69

    position index

    Sierra is a useful challenger signal for customer-facing production agents.

  • Zeroclaw logo

    Zeroclaw

    specialist

    66

    position index

    Zeroclaw is tracked as a future-stack signal for lightweight autonomous execution over owner-controlled tools.

L7 Commercial

Layer 7 — Commercial Tools

2026-03 / 2026-04 / 2026-05

  • Microsoft logo

    Microsoft

    leader

    92

    position index

    Paid Copilot seats and enterprise distribution make Microsoft the application-layer benchmark.

  • Google logo

    Google

    leader

    88

    position index

    Gemini consumer adoption keeps Google in the leader band even when enterprise monetization is harder to isolate.

  • Salesforce logo

    Salesforce

    leader

    81

    position index

    Salesforce stays strong where AI rides existing CRM workflow ownership.

  • Wiz logo

    Wiz

    leader

    80

    position index

    Cloud security posture extends naturally into AI posture as models and agents become part of the attack surface.

  • CrowdStrike logo

    CrowdStrike

    leader

    78

    position index

    Security workflow ownership makes CrowdStrike relevant as AI changes detection, response, and governance boundaries.

Shared responsibility

The cloud lesson AI still needs.

Cloud became governable when buyers understood what the provider owned and what the customer still had to own. AI needs the same boundary language for accuracy, data exposure, actions, observability, and outcomes.

L1 Infrastructure

Layer 1 — AI Infrastructure

Provider owns capacity, availability, hardware lifecycle, and physical resilience. Customer owns workload placement, demand forecasting, and utilization risk.

L2 Models

Layer 2 — Model Portfolio

Model provider owns training, model behavior, release cadence, and safety defaults. Customer owns model selection, workload routing, evals, and fallback policy.

L3 Data Mgmt

Layer 3 — Data Management

Data platform owns storage, lineage, access control, and governance surfaces. Customer owns data quality, semantic modeling, and agent-access policy.

L4 AI Data

Layer 4 — AI-Ready Data

AI-ready data provider owns retrieval quality, indexing, wrappers, and access surfaces. Customer owns source-data truth, freshness, permissions, and which agents may consume which context.

L5 Dev Tools

Layer 5 — Developer Tools

Tool provider owns coding UX, context packaging, model/tool invocation, and review affordances. Customer owns repository permissions, acceptance criteria, and production release governance.

L6 Agents

Layer 6 — Agent Tools

Agent tool owns execution loop, tool-use guardrails, memory, logging, and escalation mechanics. Customer owns delegated authority, permissions, rollback, and exception policy.

L7 Commercial

Layer 7 — Commercial Tools

Tool provider owns workflow UX, packaged domain behavior, and product controls. Customer owns data portability, agent access, workflow redesign, and whether point tools become durable or get absorbed by agent systems.

Controls tracked across layers

Accuracy and fitness for taskData exposure and retentionAction safety and rollbackLogs, traces, evals, and cost visibilityCompliance, residency, and audit evidenceHuman review and escalationBusiness outcome accountability

Top model cards

Capability is only one column.

The cards link model lineage to market fit: capability signature, operating envelope, drift watch, and trust surface. They are designed to sit on top of the LLM Evolutionary Tree rather than replace it.

reasoning

GPT-5.5

OpenAI / Frontier closed reasoning default

Reasoning5/5
Coding5/5
Multi5/5
Tools5/5
Context4/5
Cost3/5
Open1/5

Best fit

High-stakes reasoning, agentic coding, multimodal work, and workloads where frontier quality outweighs portability.

Trust surface

Strong enterprise posture through hosted controls; portability and inspectability remain closed-model constraints.

reasoning

Claude Opus 4.7

Anthropic / Frontier enterprise reasoning and coding model

Reasoning5/5
Coding5/5
Multi4/5
Tools5/5
Context4/5
Cost3/5
Open1/5

Best fit

Long-form reasoning, coding, tool-use workflows, and enterprise contexts that weight safety and trust posture heavily.

Trust surface

Strong trust-center posture; still requires application-level output review and action controls.

reasoning

Gemini 2.5 Pro

Google + DeepMind / Frontier multimodal reasoning model

Reasoning5/5
Coding4/5
Multi5/5
Tools4/5
Context5/5
Cost3/5
Open1/5

Best fit

Multimodal and long-context workloads, especially where Google Cloud or Google product distribution is already strategic.

Trust surface

Strong cloud control surface; model behavior remains closed and requires independent application evals.

reasoning

DeepSeek-R1

DeepSeek AI / Open-weight reasoning pressure point

Reasoning5/5
Coding4/5
Multi1/5
Tools3/5
Context4/5
Cost5/5
Open4/5

Best fit

Reasoning workloads where cost, portability, and self-hosting leverage matter more than first-party product polish.

Trust surface

Openness improves inspection and hosting control; customers inherit more responsibility for safety, deployment, and monitoring.

mixture_of_experts

Llama 4 Maverick

Meta AI / Open ecosystem frontier family

Reasoning4/5
Coding4/5
Multi4/5
Tools3/5
Context4/5
Cost4/5
Open4/5

Best fit

Enterprise and developer contexts that value ecosystem breadth, inspectability, and deployment flexibility.

Trust surface

Strong portability; customer must own hosting, eval, and policy controls unless using a managed provider.

reasoning

Qwen3-235B-A22B-Thinking-2507

Alibaba / Open-weight reasoning and regional sovereignty signal

Reasoning5/5
Coding4/5
Multi3/5
Tools3/5
Context4/5
Cost4/5
Open4/5

Best fit

Reasoning workloads where open weights, regional availability, and China-scale ecosystem signals matter.

Trust surface

Openness aids inspection; jurisdiction, hosting, and data governance need explicit buyer review.

mixture_of_experts

Mistral Large 3

Mistral AI / European frontier and sovereignty model

Reasoning4/5
Coding4/5
Multi3/5
Tools3/5
Context4/5
Cost4/5
Open3/5

Best fit

European enterprise and sovereignty-sensitive workloads that need strong performance without a single US frontier dependency.

Trust surface

Regional positioning helps governance narratives; individual deployment controls still determine practical risk.

decoder_only

Cohere Command A

Cohere / Enterprise retrieval and workflow specialist

Reasoning3/5
Coding3/5
Multi1/5
Tools4/5
Context4/5
Cost4/5
Open1/5

Best fit

Retrieval-heavy enterprise workflows, knowledge applications, and workloads that value business-context fit over raw frontier rank.

Trust surface

Enterprise positioning is useful, but buyer-side evals should prove retrieval quality and data handling.

reasoning

Grok 4

xAI / Frontier challenger with social distribution

Reasoning5/5
Coding4/5
Multi3/5
Tools3/5
Context4/5
Cost3/5
Open1/5

Best fit

Buyers exploring frontier alternatives and consumer/social-context distribution signals.

Trust surface

Closed-provider controls apply; enterprise trust posture should be treated as less proven than the leading incumbents until evidence improves.

mixture_of_experts

gpt-oss-120b

OpenAI / Open-weight strategic hedge from a closed-model leader

Reasoning4/5
Coding4/5
Multi1/5
Tools3/5
Context4/5
Cost4/5
Open4/5

Best fit

Portability-sensitive teams that want open-weight leverage without leaving the OpenAI model family narrative entirely.

Trust surface

Open weights shift more operational responsibility to the deployer while retaining strategic familiarity with a leading model provider.

Methodology.

  • Primary category by market role. Companies can span the stack, but the main placement reflects what a buyer or board most needs to understand.
  • Control points over logo boxes. The taxonomy tracks who owns compute, model choice, source data, AI-ready context, developer workflow, agent execution, and vertical commercial outcomes.
  • Quantitative claims with freshness. Metrics include period, confidence, source refs, and refresh cadence. Sparse disclosure stays labeled as sparse.
  • Monthly position history. Leader and challenger status is tracked as a dated index so the market map can show direction of travel, not only a current logo placement.
  • Model cards as operating cards. Cards include best fit, poor fit, drift watch, and trust surface, not just benchmark rank.
  • Data ownership as the strategic axis. The future-state bet is that durable AI architectures let us own the data and permission agents into it, rather than letting each SaaS vendor trap context inside its own product boundary.

AI-readable exports.

Boundaries. Leaders. Evidence.