This dashboard is a demo of the local console. The validator itself runs entirely on your side: it reads config exports, never touches an SBC, and needs zero outbound network. Four ways to run it, all starting from the source tree (design-partner tarball or repository checkout).
Python 3.10+ or Docker / Podman
1 runtime dependency (cryptography)
0 outbound connections required
non-root container · uid 10001
Step 0 · verify what you received (every path)
The source ships with a SHA-256 manifest covering every file. Verify before you build.
tar -xzf sbc-validator-0.16.4-src.tar.gz && cd sbc-validator-0.16.4
shasum -a 256 -c SHA256SUMS # every file, against the manifest
Path 1 · plain pip — any Python 3.10+ host
python3 -m venv .venv && .venv/bin/pip install .
.venv/bin/sbc-validator demo # the full mixed-vendor showcase, locally
Path 2 · fully offline — isolated environments
# on a connected machine:
pip download . -d wheels/
# carry wheels/ across the air gap, then:
pip install --no-index --find-links wheels/ sbc-autoops-validator
Path 3 · container — Docker or rootless Podman, same image
docker build -t sbc-validator . # or podman build, identical
docker run --rm --network none sbc-validator demo # the air-gap claim, proven on your hardware
The audit artifact — identical from every path
Every run path writes the same single source of truth: results/<sbc>/<timestamp>.json, history-preserving. In containers, mount it out or it dies with the container:
docker run --rm --network none -v "$PWD:/work" sbc-validator \
validate /work/configs/teams.ini --out /work/results --html /work/report.html
# in CI: upload results/ as a pipeline artifact (see examples/ci/)
Path 4 · your CI/CD — the pre-deploy gate
A drop-in pipeline example ships at examples/ci/sbc-pre-deploy-gate.yml. The non-zero exit blocks a PR before a non-compliant config reaches the change window.
sbc-validator validate config.ini \
--ruleset rulesets/ms_direct_routing_2026-06.json --fail-on review
Then explore
sbc-validator validate · walk · simulate · explain · diff · fleet
sbc-validator serve --results results # this console, live on your own results