Requirements¶

EnforceGate vX runs on any x86-64 platform and requires no proprietary hardware.

The vX edition of EnforceGate is designed to be deployed and operated as a container or as a virtual appliance on commodity hardware. Systems with Intel® Streaming SIMD Extensions (SSE) are recommended for optimal evaluation throughput.

EnforceGate vX scales up to 10 Gbps of concurrent HTTP traffic and beyond. Actual performance varies with the underlying hardware resources — particularly CPU processing power, memory bandwidth, and the active SSL inspection mode. ¹

Hardware¶

EnforceGate vX can be deployed on any x86-64 host that meets these minimum requirements:

The default container resource limits in the shipped docker-compose.yml target a small/medium deployment:

Without these limits a runaway proxy can saturate the host on a policy-compile loop or a connection flood.

Software¶

The software requirements vary by deployment method:

• Virtual appliance: VMware ESXi 8.0+, KVM with QEMU 7.0+, or Hyper-V Server 2019+. The OVA includes the host OS, Docker, and the pre-pulled standalone bundle — no extra host preparation required.
• Docker: Docker Engine 27+ and Docker Compose v2.x on a Linux kernel 6.x or newer.

License¶

Pro is generally available today and bundles 25 concurrent connector sessions per engine — comfortable for a typical small deployment, where the standalone bundle spawns 5 connector processes by default. Business (40 sessions) and Enterprise (50) are in development.

Business and Enterprise are in development — see Editions for the feature matrix and enforcegate.com for current availability.

There is no per-byte, per-user, per-endpoint, or per-connector-session metering on any edition — the deployment cost follows how many instances you run, not the traffic they carry. See Licensing for the fail-open behaviour on the paid tier (paid editions never brick when a license lapses or the Control Server is temporarily unreachable).