Assessment Disclosure

What These Assessments Are Not

• Not rankings. Vendors are not scored against each other or ranked in order. There is no Layer2C top-ten list.
• Not certifications. No vendor pays to receive a certification, badge, or seal of approval from Layer2C or The CTO Advisor.
• Not procurement recommendations. These assessments do not tell you which vendor to buy. They map the architectural and authority implications of each vendor's platform so buyers can ask better questions.
• Not lab validations. Assessments are based on publicly available materials and briefings, not independent benchmark testing or hands-on lab evaluation.
• Not exhaustive product reviews. Each assessment evaluates authority placement across the 4+1 AI Infrastructure Model. It does not cover every product feature, SKU, or configuration option.
• Not permanent. AI infrastructure evolves rapidly. Assessments reflect a point in time and are updated as architectures change. Each assessment displays its date and version.

Assessment Type

Layer2C assessments are opinionated architectural analyses. They evaluate where decision authority resides across the 4+1 Layer AI Infrastructure Model — from compute and networking through data, orchestration, runtime, reasoning, and applications — and classify each vendor component using the Decision Authority Placement Model (DAPM).

The assessments are produced by The CTO Advisor LLC, an independent analyst firm. The primary author is Keith Townsend. The CTO Advisor's independent architectural judgment is one of the evidence inputs; it is not the only one.

Evidence Sources

Assessments draw from publicly available materials, which may include:

• Vendor conference presentations and technical sessions (GTC, re:Invent, Google Cloud Next, HPE Discover, Microsoft Ignite, etc.)
• Official product documentation, white papers, and architecture guides
• Press releases and earnings call transcripts
• Analyst coverage and independent technical reporting
• Vendor briefings and technical conversations
• GitHub repositories and open-source project documentation
• The CTO Advisor's independent architectural judgment

Each assessment lists its primary sources. Where a vendor has reviewed an assessment prior to publication, this is noted on the assessment page.

Update Cadence

Assessments are updated when material architectural changes occur — new product launches, significant partner changes, acquisition of capabilities relevant to a layer, or substantial platform evolution. Minor updates (corrected facts, updated phrasing) may occur without a version increment.

The date and version displayed on each assessment reflect the most recent substantive update. Assessments are not updated on a fixed schedule — they are updated when the architecture changes.

Vendor Correction Process

Vendors who identify factual errors in their assessment may submit corrections to The CTO Advisor at thectoadvisor.com. Factual corrections — incorrect product names, inaccurate capability descriptions, outdated information — are reviewed and incorporated promptly.

Vendor review does not imply vendor approval or endorsement. Editorial positions — architectural judgments, DAPM classifications, gap analysis conclusions — are retained at The CTO Advisor's discretion. Vendors do not have final approval over assessment content.

Commercial Relationship Policy

Vendors do not pay to be assessed on Layer2C. Assessment inclusion and findings are not influenced by commercial relationships.

Where The CTO Advisor has a commercial relationship with an assessed vendor — advisory engagements, consulting work, or sponsored content — this is disclosed on the relevant assessment page. The absence of a disclosure note means no such relationship exists at the time of assessment publication.

What DAPM Does and Does Not Mean

The Decision Authority Placement Model (DAPM) classifies each assessed component on one axis: can the enterprise take its accumulated opinions at this layer — configs, policies, governance logic, operational model — and operate them independently of this vendor without rebuilding?

Retained means yes. The capability rests on a commodity substrate (x86 compute substitutable across OEMs) or open-source software with real alternatives. Also applies when the vendor provides nothing at a layer — the enterprise owns the function by default.

Delegated means partially. The capability is provided by a substitutable partner or open-source tooling the enterprise could swap without rebuilding. The enterprise keeps the right to change providers.

Ceded means no. A closed system is a closed system. The vendor's opinions are proprietary with no open exit, regardless of who operates the software or where it runs.

DAPM is not a quality score. A Ceded component can be excellent — cloud vendors routinely provide world-class capability that enterprises consume without governance authority. The classification describes the governance relationship, not the capability's fitness for purpose. Completeness and authority are orthogonal. A Retained classification does not mean the capability is good. A Ceded classification does not mean the vendor should be avoided.