Architecture

Kaizen has three parts: a lightweight client that attaches to your agent, an Observer that runs in isolation and learns each agent's behavior, and a managed control plane for policy, keys, and verdicts.

Where it runs

• Client (data plane). Runs in-process with your agent. It checks every action against policy locally, fast and fail-closed, and reports each one. This is what blocks a known-bad call before it happens.
• Observer. Runs as its own isolated service. It learns each agent's normal behavior and flags real deviations. Because it reads untrusted agent input, it runs boxed off: no inbound except the verdict request, egress only to its memory store.
• Control plane. The managed API and console where you set policy, issue keys, and watch verdicts. It also forwards the action stream to the Observer and fans verdicts out to your tools.

How a verdict flows

The reflex (allow or block) is local and immediate. The judgment (is this a deviation from how this agent normally behaves) happens in the Observer, just behind it, and never slows the agent.

Where the Observer can run

The Observer definition does not change; only the runtime does:

1. Local process, for development.
2. Container on your own infrastructure.
3. Hardened MicroVM for stronger isolation.

That progression is how you take it from a laptop to an in-tenant, locked-down deployment without changing the Observer itself.