Skip to content
SiteSwarm Platform Documentation

Adr 0004 Central Command Center Architecture

Central Command Center Architecture

1. Executive Summary & Objective

As the SiteSwarm client fleet grows, operating dozens of independent client deployments requires a unified internal control plane (apps/command-center) so agency staff can inspect fleet health, review client telemetry, and access client administrative tools from a single secure interface without managing stateful servers.

2. Core Architectural Boundaries

The Command Center is a monorepo application in apps/command-center running on serverless Cloudflare Workers behind Cloudflare Zero Trust (Access) and communicating with internal services via Cloudflare Service Bindings.

flowchart LR
    Staff["Authorized Staff"] --> Access["Cloudflare Zero Trust"]
    Access --> CommandCenter["Command Center\n(apps/command-center)"]
    CommandCenter -->|"Service Bindings"| PlatformServices["Platform & Client Services\n(Health, CMS, Telemetry)"]
  1. Zero-Trust Perimeter Authentication: Access to apps/command-center is gated at the edge by Cloudflare Zero Trust identity policies and verified JWT assertions.
  2. Modular Operational Views: Functional domains (fleet health overview, tenant directory, CMS launchpad, telemetry) are structured as isolated view modules so capabilities can be added incrementally without monolithic coupling.
  3. Service Binding Integration: Rather than duplicating database logic inside the Command Center, the application queries backing platform services and tenant health endpoints over internal Service Bindings.
  4. Provider-Agnostic Observability Seams: Dashboard views sit behind clean adapter boundaries so underlying telemetry or alerting providers can evolve without rewriting the UI.

3. Decisions Intentionally Deferred

  • Analytics Ingestion Backend: Selecting the long-term clickstream storage backend is deferred behind an abstract analytics adapter.
  • Automated Incident Paging Ladders: Complex multi-tier on-call escalation schedules are deferred until fleet scale requires them.
  • Automated Billing & Subscription Hooks: Subscription billing automation inside the Command Center is deferred.