Operators & Self-Hosting

Deploy your own Gate Kali sidecar for personal use, a team, or a multi-tenant gateway. Manage tenants, policies, custom detectors and telemetry from the admin dashboard.

1. Deployment shapes

●

Single-user sidecar

Run on the local machine with Docker or the install script. The extension talks to 127.0.0.1:8002.

●

Hosted sidecar

Run on a VPS with HTTPS. Users connect via a shared client token and https://api.example.com.

●

Multi-tenant gateway

Central proxy in front of multiple services. Callers authenticate with per-tenant API keys.

2. Docker sidecar

Clone the repo and start the local stack:

git clone https://github.com/Evansone001/gate-kali.git
cd gate-kali
docker compose up -d --build
# http://127.0.0.1:8002

Health check:

curl http://127.0.0.1:8002/health
Persistence: set NEXA_GUARD_REDIS_URL to keep the token vault across restarts. The Docker compose file wires Redis automatically.

3. Public hosted sidecar

For a public HTTPS endpoint, deploy the Docker image behind a reverse proxy with automatic TLS.

  1. Create the sidecar container and bind mount data + secrets volumes.
  2. Generate a client token and admin key once, persist them outside the container.
  3. Use nginx-proxy + acme-companion or Caddy to terminate TLS.
  4. Put the container on the same Docker network as the reverse proxy.

Key environment variables:

VariablePurpose
NEXA_GUARD_LOCAL_CLIENT_TOKEN_FILEPath to a file containing the shared client token.
NEXA_GUARD_ADMIN_API_KEYEnables the /admin dashboard and admin API.
NEXA_GUARD_TENANT_DB_PATHSQLite path for tenant/policy state.
NEXA_GUARD_REDIS_URLOptional Redis for the token vault.
Secrets on reruns: generate the token and admin key once and mount them as files. Don't let Docker regenerate them on every restart.

4. Gateway mode

Run as a centralized edge gateway for multiple services or tenants:

NEXA_GUARD_REQUIRE_API_KEY=true
NEXA_GUARD_TENANT_API_KEYS='{"sk-acme":"acme","sk-globex":"globex"}'
NEXA_GUARD_TENANT_POLICIES='[{"rule_id":"acme-uncloak-deny","effect":"deny","tenant_id":"acme","actions":["uncloak"],"priority":10}]'

Callers send x-api-key; the key maps to a tenant and its policies.

5. Admin dashboard

Visit https://your-sidecar/admin and enter your admin key. From the dashboard you can:

Custom detectors are compiled into the detector tables used by the Rust core, Python proxy and extension.

6. Enterprise Chrome policy

For managed fleets, deploy the extension via Chrome policy so users can't remove or reconfigure it:

{
  "3rdparty": {
    "extensions": {
      "8a7d5921fca6d3c0e729e638d5d838d1c4f54afd671e8fac4249d825354399a7": {
        "nexa_guard_enabled": true,
        "nexa_guard_fail_mode": "block",
        "nexa_guard_api_base": "https://guard.corp.example",
        "nexa_guard_custom_terms": ["Project Falcon", "ACME-SECRET"]
      }
    }
  }
}

Managed values override anything the user can change in the popup. See docs/enterprise-deployment.md in the repo for Windows GPO and Firefox policies.