data-centered.com · landscape
Context-Layer Landscape
31 vendors and patterns mapped across the four-axis context-layer stack — substrate, composition, delivery, runtime — plus incumbents that span all four. Verdicts assessed from the perspective of a producer-maintained-context analytics platform.
What the map says
Delivery is thin
5 entries; only MCP is a clear buy. The producer-maintained-context pitch needs an MCP runtime resource handler — that's the gap to claim.
Substrate is crowded
10 entries, 4 evaluate. The market is loud but most plays are wrong-shape (vendor data risk). The white space: OSS substrate with analytics-domain primitives — what CocoIndex + a thin meta-context layer could occupy.
Highest-fit is open
Only MCP and Claude Code Tasks are high analytics fit — both are protocols/patterns, not vendors. No incumbent owns the analytics-domain context layer yet.
// Built with DESIGN.md tokens (linted) and Emil Kowalski's emil-design-eng animation rules. No transition: all, no ease-in, no scale(0) entrances. Tokens declared once at /docs/design.md.