Skip to main content
BeyondGuard installs on-premise via Helm (OpenShift/Kubernetes) or Docker Compose (single-node). Deployment follows a defined process with responsibilities shared between your team and BeyondGuard.

​
Choose a method

Helm

For OpenShift and Kubernetes. Namespace isolation, HPA auto-scaling, ConfigMap/Secret management, and Persistent Volumes.

Docker Compose

For a single node. A provided docker-compose.yml, volume mounts for persistence, and health-check/restart policies.

​
Responsibility matrix

The deployment is a sequential process. Ownership is split between you (your infrastructure team), BeyondGuard, and both working together.

​
Repository access

BeyondGuard issues credentials for two repositories, in this format:
  • Helm repository — username helm-customer-<company>, with an address and password provided to you.
  • Image repository — username docker-customer-<company>, with an address and password provided to you.

​
Install steps

  1. Pull the Helm chart from the BeyondGuard repository.
  2. Edit values.yaml for your environment (image registry, database connections, ingress, PVC storage class, LLM provider, GPU node).
  3. Run helm install into your target namespace.

​
Air-gapped environments

In restricted or air-gapped networks, mirror the BeyondGuard images and Helm charts to your internal registry or artifactory (Harbor, Artifactory, Nexus, and similar are supported), then point the installer at your mirror. Provide your artifactory host and credentials during onboarding so the base images can be pushed there.

On-Prem Requirements

Prerequisites to have in place before installing.

Infrastructure Sizing

Size the cluster and GPU node.

ICAP & Proxy

Add inline proxy inspection.

Quickstart

Send your first request once installed.