Deployment Models

VNetArmor can be deployed as Linux packages or containers. The correct model depends on operational ownership, patching process, networking, and how traffic reaches your applications.

Single-host package deployment

graph LR
  Internet --> Core[VNetArmor Core on Linux host]
  Core --> App[Application on same or remote network]
  Managerd --> Core

Use this for simple deployments, labs, controlled production environments, or when the operations team prefers system packages and systemd services.

Container deployment

graph LR
  Internet --> Core[VNetArmor Core container]
  Core --> App[Application container or service]
  WebGUI --> Managerd[Managerd container]
  Managerd --> Core

Use this when the environment already uses Docker or container orchestration. Mount configuration, logs, certificates, and license data as persistent volumes.

HA deployment

graph TD
  Client --> LB[External Load Balancer]
  LB --> Core1[Core node 1]
  LB --> Core2[Core node 2]
  Core1 --> AppPool[Backend pool]
  Core2 --> AppPool
  Managerd --> Core1
  Managerd --> Core2

For HA, keep configuration under version control and use consistent certificates, policy files, and backend definitions across nodes. Health checks should target a lightweight path such as /health.

Example hostnames

Role	Example
Protected website	www.example.com
Protected API	api.example.com
Core node	core01.example.local
Managerd node	manager01.example.local
WebGUI	admin.example.local
Portal	portal.example.com