THE CAPABILITY MAP · WHY ONE PLATFORM
Every AI category covers a slice. One platform covers the map.
A control plane for enterprise AI takes ten capabilities — from discovering what you run to containing what it does. The tools market sells them two or three at a time. Kosmoy covers all ten, on one identity model, one policy layer and one audit trail.
A market is forming around enterprise AI control, and it is forming in slices. AI gateways centralize traffic. Observability platforms watch it. Governance suites document it. Security tools scan it. Eval and red-teaming tools test it before launch. Each category is real, and each covers two or three of the ten capabilities a mature AI programme needs.
Assemble the stack from categories and you hold five or six contracts, five or six integrations — and a seam between every pair of products. The seams are where risk hides: the agent the gateway never saw, the policy the observability tool cannot enforce, the audit trail split across four consoles. The four layers of Kosmoy’s AI management platform — Inventory, Monitoring, Governance and Action Control — exist to remove those seams.
Ten capabilities. Eight categories. One overlay.
Select a category to isolate its typical scope against Kosmoy’s dashed reference — the same honest baseline used on every comparison page.
Category by category, same axes.
Every panel plots one category’s typical scope with Kosmoy as the dashed outline. Panel titles open the buyer’s guide that scores that category vendor by vendor.
Do I need an AI gateway and an AI observability platform?
They solve different spokes. A gateway is a policy point — strong on GW and GRD, thin everywhere else. An observability platform watches quality and cost — strong on OBS and EVL, but it cannot enforce anything it sees. Run both and you still have no inventory, no containment, no compliance evidence — and a seam where the gateway’s logs meet the observability tool’s traces. Kosmoy runs the gateway and the monitoring as two layers of one platform, so what the monitor sees, the gateway can enforce.
How many tools does an AI governance stack take?
Assembled from point categories: five or six. A gateway for traffic, an observability platform for cost and quality, a governance suite for documentation, a security scanner, an eval tool — and still nothing that contains an agent or keeps prompts out of a vendor cloud. That is five or six products to license, integrate, upgrade and audit, each with its own identity model and its own logs. The capability map is the case for the alternative: one platform, one operating loop, one audit trail.
Which capabilities have no specialist category at all?
Two spokes on the map have no dedicated product category: agent containment (CTN) and deployment sovereignty (SOV). No point tool sells a kernel-enforced sandbox with scoped credentials and a kill switch — that is Kosmoy’s Action Capsule. And no SaaS control tool can make itself sovereign: Kosmoy runs single-tenant in your own Kubernetes, air-gap capable, so the control plane itself lives where your data does.
Ten capabilities, four layers.
Every spoke on the map is run by one of Kosmoy’s four layers. The tenth spoke is the platform itself — deployed in your own Kubernetes.
| Code | Capability | Where it runs in Kosmoy |
|---|---|---|
| INV | AI Inventory & Discovery | Layer 1 · AI Inventory |
| SEC | Security & Shadow AI | Layer 1 · Agents Master Registry |
| OBS | Observability & FinOps | Layer 2 · AI Monitoring |
| GW | Gateway & Policy Control | Layer 3 · AI Gateway |
| GRD | Guardrails & Runtime Safety | Layer 3 · Guardrails |
| CTN | Agent Containment | Layer 4 · Action Capsule |
| CMP | Compliance & Audit | Layer 3 · AI Compliance |
| EVL | Testing, Evals & Red-teaming | Layer 2 · AI Evaluation |
| BLD | Agent Building | Cross-layer · Agent Builder |
| SOV | Deployment Sovereignty | The platform itself — your Kubernetes |
The capability map, answered straight.
What is the AI capability map?
The AI capability map is a ten-axis view of what it takes to run AI at enterprise scale: inventory and discovery, security and shadow AI, observability and FinOps, gateway and policy control, guardrails, agent containment, compliance and audit, evals and red-teaming, agent building, and deployment sovereignty. Plotted on the map, each emerging product category — AI gateways, observability platforms, governance suites, security tools — covers two or three spokes. Kosmoy is built to cover all ten in one platform.
Does the capability map score vendors or categories?
Categories. Each profile on the map shows the typical scope of a product type, not a scoring of any individual product. Vendor-by-vendor scoring on the same ten axes lives in the buyer's guides — every guide plots real products against the same axes, with citations, and every category on the map links to its guide.
Where do specialist tools still beat Kosmoy?
On the deepest end of their own spoke. Pure-play eval platforms lead on experiment tracking, annotation queues and prompt playgrounds; dedicated agent-development platforms go deeper than Kosmoy's governed builder; observability specialists offer richer APM-style integrations. The map's argument is not that Kosmoy wins every spoke — it is that no specialist covers more than a slice, and the seams between specialists are where risk hides.
How does the capability map relate to Kosmoy's four layers?
The map is the demand side: the ten capabilities an enterprise AI programme needs. The four layers — AI Inventory, AI Monitoring, AI Governance, AI Action Control — are the supply side: how Kosmoy organizes those capabilities into one product. Every spoke on the map is run by one of the layers, sharing one identity model, one policy model and one audit trail.
Can Kosmoy coexist with tools we already run?
Yes. The gateway is OpenAI-compatible, so existing apps point at it without code changes, and existing observability or eval tools can keep reading from it. Most teams start by consolidating the spokes with no owner — containment, sovereignty, compliance evidence — and retire overlapping point tools at renewal time rather than in a big-bang migration.
Related modules
See your stack on the map.
Bring the tools you run today. We will plot them on the ten axes, show where the seams are, and what consolidating onto one platform would retire.
Or email sales@kosmoy.com.