Skip to main content

Component diagram

Reference architecture for a production OpenBox deployment. Simplified from openbox-k8s-cluster-prod snapshot (2026-07-03) for readability.

Multi-container openbox-core pod​

openbox-core runs 5 containers in a single pod:

  • openbox-core-service-server — HTTP API :8086
  • openbox-core-service-governance-worker — Temporal SDK worker
  • openbox-core-service-attestation-worker — Temporal SDK worker
  • openbox-core-service-observability-worker — Temporal SDK worker
  • openbox-core-service-scheduler — cron + workflow scheduler

They share pod lifecycle, filesystem, and localhost. Scaling openbox-core from 1 → 5 pods scales all 5 container instances 5 → 25.

Out of scope of this diagram​

Not shown: Datadog / observability stack, GitOps (ArgoCD), age-service, Cloudflare, edge protection (WAF/Shield), admin access (Verified Access / VPN). Those are your decisions — see AWS integration surface for the OpenBox-required interface.