Installation

Install the CLI with npm, pnpm, Homebrew, or curl, then add Cirvix to a Docker or Kubernetes deployment.

The CLI is a single static binary. Every install path below produces the same cirvix command; pick the one that matches how your team already installs tools.

Package managers

Manager	Command
npm (no install)	npx @cirvix/agent-control scan
npm (persistent)	npm install -g @cirvix/agent-control
pnpm	pnpm add -g @cirvix/agent-control
Homebrew	brew install cirvix/tap/cirvix
curl	curl -fsSL cirvix.com/install \| sh

TerminalShell

$ cirvix --versioncirvix 0.9.2 (private-beta)

Docker

The gateway runs as a sidecar container next to your agent, sharing enough of the network path to enforce egress without changing application code. See Docker for the full sidecar pattern.

TerminalShell

$ docker run --rm \    -v $PWD/policies:/etc/cirvix/policies:ro \    -v $PWD/cirvix.policy.json:/etc/cirvix/cirvix.policy.json:ro \    cirvix/cirvix:latest gateway \      --servers /etc/cirvix/mcp.json \      --policy /etc/cirvix/cirvix.policy.json

Kubernetes and Helm

A Helm chart installs the gateway as an injected sidecar, or as a DaemonSet in namespaces where a sidecar per pod is impractical.

TerminalShell

$ helm repo add cirvix https://charts.cirvix.com$ helm install cirvix cirvix/cirvix-gateway \    --namespace cirvix --create-namespace \    --set policy.source=git \    --set policy.repo=github.com/your-org/policies

Note

Kubernetes deployment is in active development for private beta — the chart installs a working gateway today; DaemonSet and LSM enforcement modes are landing incrementally. Current status is tracked on the Integrations page.

Verify

TerminalShell

$ cirvix --version && cirvix scan

QuickstartScan a machine, write a policy, and run a governed call.DockerThe sidecar pattern in full, with environment variables.KubernetesChart values, sidecar injection, and egress NetworkPolicy.

Edit this page on GitHub

Was this page helpful?