Skip to content
OpsTech Docs

System map

The system map shows every service, the persistent stores it writes to or reads from, and which third-party APIs it calls. Auto-derived from the x-opstech-side-effects taxonomy carried by every OpenAPI operation in opsclaw-product/tools/api-inventory/openapi-declared/.

Updated on every push to opsclaw-product:main touching the inventory.


      
        mmdc render failed: Command failed: npx --no-install mmdc -i "/home/runner/_work/opstech-site/opstech-site/docs-site/.mermaid-cache/9a94ab4c2ee7ac35.mmd" -o "/home/runner/_work/opstech-site/opstech-site/docs-site/.mermaid-cache/9a94ab4c2ee7ac35.svg" -b transparent 2>&1
System map: services → persistent stores. Public-edge services have the 🌐 prefix; internal-only services have 🔒.

How to read

  • 🌐 services are reachable from the public DNS surface (platform.opstech.dev, opsclaw-qa.opstech.dev, …).
  • 🔒 services are internal (cluster-only, no edge routing).
  • Cylinder nodes are persistent stores (Postgres, Cloudflare, Stripe, …).
  • Edge colors reflect the dominant action class of the service (red = mutating, blue = calling, green = read-only). See the legend below.

Companion diagrams