DenialOS architecture

DenialOS is implemented as a modular monolith with domain services, a shared tRPC application router, PostgreSQL/Drizzle persistence, Redis/BullMQ workers, and a React/TanStack Router frontend.

!DenialOS architecture

React / TanStack Router
          │
          ▼
      tRPC API
          │
  ┌───────┼─────────────────────────┐
  ▼       ▼                         ▼
Cases   Revenue/RCM          Integration control
  │       │                         │
  │       │                         ├─ connection contracts
  │       │                         ├─ secret references
  │       │                         ├─ adapter packs
  │       │                         ├─ checkpoints
  │       │                         └─ reconciliation
  │       │
  └───────┼───────────────┐
          ▼               ▼
      Evidence / AI     PostgreSQL
          │               ▲
          └──── Workers ──┘
              │
             Redis

External boundaries

External providers are deliberately separated from core domain behavior:

• Clerk authentication
• PostgreSQL
• Redis
• private object storage
• Google Document AI
• Anthropic LLM
• SendGrid
• Paddle
• EHR/vendor APIs.

The presence of a provider configuration does not itself mean that the provider is active or production validated.