Optima Pulse — Monitor • Analyze • ActOptima Pulse — Monitor • Analyze • Act

Technology

Edge-collected telemetry. Tenant-isolated control plane. Honest empty states.

Optima Pulse is built as an edge-collected monitoring and detection spine: collectors at the site, a Go API with Postgres RLS, VictoriaMetrics for metrics, ClickHouse for flows, and NATS for realtime.

Optima Pulse
Optima Pulse analytics sourced from ClickHouse
Analytics and NDR charts read real stores. No synthetic series.

Collection

  • • SNMP (gosnmp) and ICMP from site-bound edge collectors
  • • Syslog and SNMP traps over UDP at the edge
  • • NetFlow, IPFIX, and sFlow into ClickHouse
  • • Network detection telemetry into the NDR workflow
  • • Local buffer and mTLS on the collector path

Control plane

  1. Presentation. NOC Command Center, NMS, topology, flow analytics, NDR, AIOps, automation, and reporting in one React console.
  2. API & identity. Go API, Keycloak/OIDC or local auth, RBAC, and tenant context that is never accepted from the client.
  3. Intelligence. Alert correlation, NDR workers, AIOps, RCA, Copilot, and automation playbooks on the same control plane.
  4. Telemetry stores. Postgres for inventory and detections, VictoriaMetrics for metrics, ClickHouse for flows, NATS for realtime.
  5. Edge collection. Site-bound collectors for SNMP, ICMP, syslog, traps, and NetFlow/IPFIX/sFlow with local buffer and mTLS.

Engineering constraints that show up in the product

No invented telemetry

Empty metrics or flows are a valid state. Health, charts, and KPIs do not fabricate availability to look demo-ready.

Tenant isolation

Every operational object carries tenant_id with FORCE RLS. Tenant context is never accepted from the client.

Realtime, not polling the UI

NATS and a WebSocket hub push NOC, NDR, and operational updates. The console is not a refresh loop against Postgres.

Multi-store by workload

Inventory and detections in Postgres, metrics in VictoriaMetrics, high-volume sessions in ClickHouse, evidence blobs in object storage when used.

RBAC that matches the nav

Command Center, NMS, NDR, NEM, AIOps, automation, and administration are permission-gated — empty groups are dropped, not left as a shell.

Hybrid-ready

SaaS, on-prem, and hybrid control planes with data residency routing for teams that cannot send every packet to a public cloud.

Next step

Explore the deployment model

View Deployment