Deployment

Deploy RADAR self-hosted beside your existing agent stack. Evidence stays in your infrastructure — VPC, on-prem, or air-gapped.

System model

Three deployment principles:

Sidecar. RADAR runs beside your LLM gateway and tool infrastructure. It observes without intercepting the execution path.
Your infrastructure. All evidence stays inside your VPC, on-prem, or air-gapped network. No cloud dependency.
No execution ownership. RADAR does not run agents, orchestrate workflows, or replace your existing stack.

Docker Compose

Recommended for evaluation and mid-scale production. RADAR runs as a single service with local volume storage.

services:
  radar:
    image: akioudai/radar:latest
    ports:
      - "8080:8080"
    volumes:
      - radar-data:/data
    environment:
      - RADAR_LICENSE_KEY=${RADAR_LICENSE_KEY}
      - RADAR_RETENTION_DAYS=30
    restart: unless-stopped

volumes:
  radar-data:

Kubernetes

For enterprise deployments requiring auto-scaling, rolling updates, and service mesh integration.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: radar
spec:
  replicas: 2
  selector:
    matchLabels:
      app: radar
  template:
    spec:
      containers:
      - name: radar
        image: akioudai/radar:latest
        ports:
        - containerPort: 8080
        env:
        - name: RADAR_LICENSE_KEY
          valueFrom:
            secretKeyRef:
              name: radar-secrets
              key: license-key
        - name: RADAR_RETENTION_DAYS
          value: "90"
        volumeMounts:
        - name: evidence-storage
          mountPath: /data
        resources:
          requests:
            memory: "2Gi"
            cpu: "500m"
          limits:
            memory: "4Gi"
            cpu: "2"
        livenessProbe:
          httpGet:
            path: /health
            port: 8080
      volumes:
      - name: evidence-storage
        persistentVolumeClaim:
          claimName: radar-evidence

Use persistent volumes for evidence retention. RADAR does not require external network access after deployment. For air-gapped environments, ensure the image is in your private registry.

Air-gapped

RADAR is designed for zero-trust environments. No external API calls, no telemetry, no cloud dependencies.

Name
No egress required
Description
RADAR does not phone home. All evidence processing, retention, and export is local.
Name
Offline license validation
Description
License keys validated at startup with optional offline activation for air-gapped networks.
Name
Local storage only
Description
All traces, findings, and exports reside on local or networked storage inside your security perimeter.

Deployment checklist →