Get Started · Self-Serve

From zero to first signal in five minutes.

Drop our read-only collector into a dev cluster. See your first workload graph before your coffee gets cold.

Helm chart, Terraform module, or a single curl install. No agents on the GPU nodes.

Workloads, runtimes, and routing layers populate within minutes. No manual instrumentation.

Pick the signals that matter. Slack, email, or webhook — your team's existing flow.

Option 1 · Kubernetes Job (no local install)

Runs inside your cluster as a one-off Job, using its own scoped RBAC role. Self-deletes after 10 minutes.

kubectl apply -f deploy/rbac.yaml
kubectl apply -f deploy/scan-job.yaml

Option 2 · CLI on your machine

Reads your existing kubeconfig. Use pipx if you have any pydantic v1 dependencies elsewhere — it avoids the conflict.

pipx install piqc
piqc scan

Option 3 · Docker

No local Python needed — mount an exported static kubeconfig into the container.

docker run --rm -v ~/.kube/config:/root/.kube/config:ro
  ghcr.io/paralleliq/piqc scan

All three produce the same read-only scan and a cost report in your terminal — no signup, no account. Full options and flags are in the piqc README.