Getting Started¶
EnforceGate vX is designed for rapid, seamless deployment and is typically operational within minutes.
EnforceGate vX ships in three editions — Pro (available now), Business and Enterprise (in development). Every deployment activates once against the Exosys Control Server on first boot, then runs fully air-gapped; the engine never phones home per request. See Editions for the feature-by-edition mapping.
Before proceeding, ensure that your system meets the minimum hardware requirements.
Distributions¶
-
Virtual appliance
Deploy our pre-built virtual appliance. The appliance bundles the EnforceGate standalone container, automatic boot at host startup, and a guided installer.
-
Docker
Deploy the EnforceGate standalone bundle (three services + four named volumes, plus an optional toolbox sidecar for operator scripting) using Docker Compose.
What you get¶
Either path produces the same runtime: a single Alpine container (the enforcegate service) running the engine, the Squid connector, and Squid itself supervised inside the container, plus two always-on sidecars — a TLS terminator publishing :80+:443, and the Python captive portal on internal :8000 — and one optional fourth sidecar, the toolbox, off by default and enabled at install time or via eghost toolbox enable. The host exposes:
:3128— Squid HTTP/HTTPS proxy.:80+:443— TLS terminator serving the captive portal and the (bump-mode) self-service CA install page.
See architecture for the full runtime topology.
Next steps¶
Once installed, drive the deployment with the eghost operator CLI:
- Verify status — run
eghost statusandeghost version. - Configure components — review the default
engine.confandsquid-connector.conf(defaults are usually fine). - Define policies — use
eghost policy new,eghost policy edit,eghost policy list. - (Optional) Enable SSL inspection — choose
peekorbumpmode and acknowledge the binding conditions forbump.
eghost (no argument) shows a one-screen dashboard summarising the deployment.