# Key Value (Valkey/Redis) managed store — the mechanism half

Render has Key Value stores as a first-class product (REST `/v1/key-value`, MCP `create_key_value` / `get_key_value` / `list_key_value_instances`). bex's parity gap starts with the **platform mechanism**, which is w1 territory: a `KeyValue` CRD + operator reconciler analogous to `Database` → CNPG (docs/ADR009-postgresql-management.md) — Valkey single-instance per plan tier, internal service DNS, optional public route, connection-info from a Secret.

Surfaces come after and elsewhere: REST/GraphQL/MCP adapters (w2-style, tracking Render's names) and a dashboard page (w5). Filed from `/pm-brainstorm for w2` 2026-07-08 — deliberately **not** a w2 milestone because the CR/reconciler must exist first. Promote to a w1 milestone when prioritized.
