Skip to content

Architecture

SilentPulse is designed as a modular, scalable system for monitoring security visibility.

┌─────────────────────────────────────────────────────────────┐
│ Frontend │
│ (React / Next.js) │
└─────────────────────────┬───────────────────────────────────┘
│ REST API
┌─────────────────────────▼───────────────────────────────────┐
│ API Server │
│ (Go) │
└──────┬──────────────────┬───────────────────┬───────────────┘
│ │ │
▼ ▼ ▼
┌──────────────┐ ┌──────────────┐ ┌──────────────────────┐
│ PostgreSQL │ │ Redis │ │ External Systems │
│ + AGE │ │ (Cache) │ │ (Splunk, Kafka, etc) │
└──────────────┘ └──────────────┘ └──────────────────────┘
▲ ▲
│ │
┌──────┴──────────────────┴───────────────────────────────────┐
│ Workers │
│ (Collectors + Scheduler) │
└─────────────────────────────────────────────────────────────┘

The central orchestrator handling:

  • REST API for frontend and integrations
  • Authentication and authorization (RBAC)
  • Flow management
  • Alert handling

Background processes that:

  • Collectors: Query external systems for observation data
  • Scheduler: Evaluate expected vs actual observations, generate alerts
  • Relational data: users, flows, alerts, configurations
  • Graph data: asset relationships, dependency mapping
  • Observation cache (what assets were seen)
  • Worker coordination
  • Real-time metrics
  1. CMDB Sync imports assets into SilentPulse
  2. Flows define which assets should report to which systems
  3. Workers collect observations from external systems
  4. Scheduler compares expected vs actual, generates alerts
  5. Notifications dispatch alerts to configured channels

SilentPulse uses a modular architecture:

ModuleDescriptionLicense
CorePipeline monitoring, alerts, flowsOpen Source
MITREATT&CK technique mappingOpen Source
BehavioralAnomaly detection, TimeTravelProfessional
AI AssistantNatural language analysisEnterprise