Platform / Self-hosted runner

Self-hosted runner

The self-hosted runner performs scanning and hearings on your infrastructure. Available on Scale.

What runs where

With the runner deployed, your source never leaves your network. The runner clones, scans, and calls the model vendors directly with your own keys. Only verdict metadata — file paths, vote counts, timings — returns to Dicast so the dashboard and struck record work.

Component	Hosted	Self-hosted runner
Source and diffs	Dicast infrastructure	Your network only
Model inference	Dicast’s vendor accounts	Your vendor accounts
Verdict metadata	Dicast	Dicast
Struck record contents	Dicast	Your choice, per repository

Deploying

# Kubernetes
helm repo add dicast https://charts.dicast.dev
helm install dicast-runner dicast/runner \
  --set workspace=acme \
  --set runnerToken=$DICAST_RUNNER_TOKEN

# Docker
docker run -d \
  -e DICAST_WORKSPACE=acme \
  -e DICAST_RUNNER_TOKEN=$DICAST_RUNNER_TOKEN \
  ghcr.io/dicast/runner:1

The runner needs outbound HTTPS to your model vendors and to api.dicast.dev. It does not accept inbound connections.

Requirements

4 vCPU and 8 GB memory per concurrent hearing; one replica handles roughly 40 pull requests per hour.
Ephemeral disk for clones, sized to your largest repository.
Network access to your Git host, including self-managed GitLab or Bitbucket Data Center.