Some teams can’t send prompts or tool outputs to a third party. For them, Sigil runs entirely inside their own network. This guide takes you from an empty cluster to your first trace.
Before you start
A Kubernetes cluster (1.27+) with at least three nodes.
A Postgres 15 database and an S3-compatible bucket.
A Sigil Scale licence key.
Install the chart
bash
helm repo add sigil https://charts.sigil.dev helm install sigil sigil/control-plane \ -f values.yaml -n sigil --create-namespace
Point values.yaml at your database and bucket. The chart creates the router, the trace collector and the dashboard.
Connect your agents
Set SIGIL_ENDPOINT to your internal URL. The SDK works the same way it does with Sigil Cloud.
Operating it
The control plane is stateless apart from Postgres and the bucket, so upgrades are a helm upgrade away. We publish a new chart with every release, usually weekly.
Our security review took one meeting, because nothing leaves our VPC.
