Self-Hosted Deployment
QuantumVerifi can be deployed in your own cloud environment or air-gapped infrastructure. Self-hosted deployment gives you full control over data residency, network access, and compliance requirements.
Architecture Overview
A self-hosted Scout deployment consists of these components:
| Component | Purpose | Replicas |
|---|---|---|
| API Server | REST API, authentication, job coordination | 2+ |
| Worker | Runs analysis workflows, LLM orchestration | 2+ (auto-scaled) |
| Web Frontend | Next.js dashboard and analysis UI | 2+ |
| PostgreSQL | Analysis results, billing, compliance data | 1 (managed recommended) |
| Redis | Job queues, caching, real-time events | 1 |
| Object Storage | Test artifacts, evidence chains, training data | S3-compatible |
| LLM Gateway | Multi-provider routing with failover | 1 |
Optional components:
- Temporal — Durable workflow orchestration (recommended for production)
- Qdrant — Vector database for RAG-enhanced generation
- V-JEPA Server — GPU-accelerated visual AI (requires NVIDIA GPU)
Deployment Options
Kubernetes (Recommended)
Scout ships as a set of container images with Kubernetes manifests. Supports any Kubernetes distribution:
- AKS (Azure Kubernetes Service) — production-tested
- EKS (AWS Elastic Kubernetes Service)
- GKE (Google Kubernetes Engine)
- Self-managed Kubernetes clusters
Manifests use Kustomize for environment-specific configuration. ArgoCD is supported for GitOps deployments.
Docker Compose
For evaluation or small-team deployments, a Docker Compose configuration is available that runs all components on a single host.
Prerequisites
- Kubernetes 1.28+ (or Docker Compose for evaluation)
- Container registry access (images provided via Azure Container Registry)
- PostgreSQL 15+ (managed or self-hosted)
- Redis 7+ (managed or self-hosted)
- S3-compatible object storage (Azure Blob, AWS S3, MinIO)
- LLM API access (Azure OpenAI, Anthropic, or self-hosted via Ollama)
Configuration
All configuration is managed through environment variables and Kubernetes ConfigMaps/Secrets.
Required Secrets
| Secret | Description |
|---|---|
DATABASE_URL | PostgreSQL connection string |
REDIS_URL | Redis connection string |
LLM_API_KEY | API key for your LLM provider |
AUTH_SECRET_KEY | Authentication provider secret |
ENCRYPTION_KEY | Token encryption key |
Sandbox Execution
Tests run in isolated sandbox containers. Self-hosted deployments support:
| Provider | Description |
|---|---|
| Kubernetes Jobs | On-demand pods per test run (recommended) |
| Docker-in-Docker | Container-based isolation |
| Local | Host execution (testing only) |
Each sandbox gets a fresh filesystem, pre-installed language runtimes, and network isolation.
Air-Gapped Mode
For environments with no internet access, Scout supports fully offline operation:
- Offline LLM — Use Ollama with locally-hosted models (Qwen, CodeLlama)
- Offline training — QLoRA fine-tuning runs on local GPU infrastructure
- No telemetry — All analytics and observability stay within your network
- Container mirroring — Images served from your internal registry
Health Monitoring
| Endpoint | Path | Purpose |
|---|---|---|
| API Server | /health | Liveness and readiness checks |
| Web Frontend | / | Frontend availability |
| LLM Gateway | /health | LLM provider connectivity |
Getting Started
- Contact us for access to container images and deployment manifests
- Review the Architecture Overview for detailed component diagrams
- Configure your environment variables and secrets
- Deploy using Kustomize or Docker Compose
- Verify health endpoints and run your first analysis
For deployment assistance, reach out to [email protected].