Skip to content

Infrastructure and Local Operations

Intended topology

flowchart LR
  classDef default fill:#1e293b,stroke:#38bdf8,stroke-width:2px,color:#f8fafc
  classDef highlight fill:#065f46,stroke:#34d399,stroke-width:2px,color:#f0fdf4
  Docker["Docker Compose"]:::highlight --> Postgres["Postgres"]
  Docker --> MinIO["MinIO + console"]
  Docker --> Redis["Optional Redis"]
  Docker --> Backend["Product backend"]
  Docker --> Executor["Fastify executor"]
  Backend --> Graph["LangGraph deployment"]
  Graph --> Executor
  Executor --> VM["Microsandbox"]
  linkStyle default stroke:#64748b,stroke-width:2px

Local workflow

The plan/README use cp .env.example .env, just up, just setup, and just start. Expected endpoints are frontend :5173, backend docs :8000/docs, and MinIO console :9001. The executor service has its own Bun/TypeScript build and test lifecycle.

Deployment considerations

The product backend should be the only public entry point. Executor and MinIO should remain internal. Postgres must support both product metadata and LangGraph checkpoint tables. Redis is optional until distributed coordination is needed.

Operational gaps

The source does not establish production deployment manifests, backup policy, observability, rate limits, or cost controls. The implementation plan calls these out as future hardening work.