Product Architecture

VNetArmor is deployed in front of websites, APIs, and online services. It receives client traffic, evaluates configured controls, and forwards allowed traffic to upstream applications.

graph LR
  C[Client] --> E[Load Balancer / DNS]
  E --> CORE[VNetArmor Core]
  CORE --> APP1[Web App]
  CORE --> APP2[API Service]
  MGR[Managerd] --> CORE
  WGUI[WebGUI] --> MGR
  GUI[Desktop GUI] --> MGR
  PORTAL[Customer Portal] --> MGR

Core responsibilities

Core handles the live traffic path. It provides frontend HTTP/HTTPS listeners, protocol hardening, L4 ACL decisions, GEO policy checks, route selection, rate limiting, WAF evaluation, backend health awareness, and JSON logging.

Managerd responsibilities

Managerd provides the management layer. It connects to Core over local IPC, exposes remote gRPC APIs, supports mTLS, and enables operational tools such as vnetarmorctl, WebGUI, and desktop GUI.

WebGUI and GUI responsibilities

WebGUI and GUI are operator-facing management tools. They do not sit in the customer traffic path. They connect to Managerd to view status, trigger reloads, inspect events, and manage policy/configuration workflows.

Portal responsibilities

The customer portal is used for software downloads, license status, entitlement control, update visibility, and support access. Production customer traffic should not depend on the portal being in the data path.