Deployment Topology

Startup dependencies and runtime paths across Kaizen's complete service set

Deployment Topology Startup dependencies and runtime paths across Kaizen's complete service set Frontend · :8080 · KAIZEN APPLICATION SERVICES Frontend :8080 API Backend · :8000 · KAIZEN APPLICATION SERVICES · 15m start period API Backend :8000 15m start period PostgreSQL · :5432 · KAIZEN APPLICATION SERVICES PostgreSQL :5432 SeaweedFS · :8333 · KAIZEN APPLICATION SERVICES SeaweedFS :8333 Agent Runtime · :8090 · KAIZEN APPLICATION SERVICES Agent Runtime :8090 Sandbox Controller · :8085 · SANDBOX PLANE Sandbox Controller :8085 Background Worker · :9100 · KAIZEN APPLICATION SERVICES Background Worker :9100 Document Worker · :9100 · KAIZEN APPLICATION SERVICES Document Worker :9100 Valkey · :6379 · KAIZEN APPLICATION SERVICES Valkey :6379 Document Extractor · :9998 · KAIZEN APPLICATION SERVICES Document Extractor :9998 Sandbox Worker · created on demand · SANDBOX PLANE Sandbox Worker created on demand Egress Proxy · :8000 · SANDBOX PLANE Egress Proxy :8000 API proxy system of record startup check turn admission callbacks sandbox lease durable tasks ingestion ledger KAIZEN APPLICATION SERVICES SANDBOX PLANE Legend Frontend Backend Database Cloud Security Message bus

Startup

  • • Backend waits for PostgreSQL and sandbox controller
  • • Object-store reachability is checked during the long start period
  • • Workers wait for durable and ephemeral stores

Runtime

  • • Agent runtime calls back for every protected effect
  • • Workers use PostgreSQL for durable truth
  • • Valkey remains ephemeral

Isolation

  • • Controller creates workers on demand
  • • Sandbox egress can reach only the proxy
  • • Failure never falls back to in-process execution