# Architecture overview — DBAOps Sovereign™

**RHOYLLE INNOVATION EMPIRE LLC** · **DBAOps Sovereign™** 1.3.0  

High-level **logical** architecture (deployment topology varies by customer).

```mermaid
flowchart LR
  subgraph targets["Managed SQL Server instances"]
    SQL1[(Instance A)]
    SQL2[(Instance B)]
  end

  subgraph collect["Collectors"]
    PS[PowerShell collectors]
  end

  subgraph control["Customer network — control plane"]
    API[REST API Node.js]
    WEB[React Fleet Command]
    REPO[(SovereignRepository SQL)]
  end

  SQL1 --> PS
  SQL2 --> PS
  PS -->|HTTPS ingest JWT or key| API
  WEB -->|HTTPS JWT| API
  API --> REPO
```

## Components

| Component | Responsibility |
|-----------|----------------|
| **SovereignRepository** | System of record: fleet, telemetry snapshots, coverage facts, license, audit, config, baseline. |
| **REST API** | Auth, licensing, ingest, dashboards’ data, OpenAPI contract, health/readiness. |
| **Fleet Command (React)** | Operator UI; static build served by customer web tier. |
| **Collectors** | Read DMV / msdb / volume stats; POST to API. |
| **Reverse proxy (typical)** | TLS termination, optional WAF — **not** shipped in repo. |

## Trust boundaries

- **Ingest** path: authenticated by **API key** and/or **Operator JWT**; must reach only customer **API** endpoint.  
- **SQL targets**: collectors use **customer-approved** credentials (e.g. Windows integrated).  
- **Repository**: holds operational metadata — classify per your **data governance** policy.

---

© 2026 RHOYLLE INNOVATION EMPIRE LLC.
