NeuralTrust | Platform for Agent Security.

TrustGate is a single static binary plus two datastores. Because the planes are selected by an argument, you scale Admin, Proxy, and MCP independently.

Topology

Plane	Argument	Scale for
Admin	`admin`	Config throughput (low — runs migrations on boot).
Proxy	`proxy`	Request volume (high — your data plane).
MCP	`mcp`	Agent/tool traffic.

Single-node setups can run admin + proxy together with ./trustgate run.

Docker

The published image runs one plane per container:

# Builder: golang (CGO_ENABLED=1)
# Runtime: distroless nonroot
EXPOSE 8080 8081 8082
ENTRYPOINT ["/app/trustgate"]
CMD ["proxy"]

Compose files: docker-compose.yaml (infra only — Postgres and Redis), plus docker-compose.api.yaml (admin + proxy) and docker-compose.frontend.yaml. make up brings up the full stack. The image is linux/amd64.

The Compose quick path focuses on admin + proxy (8080/8081). For MCP (8082), run the mcp plane (Kubernetes/chart) or add an MCP service yourself.

Kubernetes

Manifests live under k8s/ (kustomize); each plane is its own Deployment with the matching args (["admin"], ["proxy"], ["mcp"]):

kubectl apply -k k8s/

Provide configuration via a ConfigMap + Secret (see Configuration); secrets.env.example lists what each plane needs.

Health & readiness

Every plane exposes probes for orchestration:

GET /healthz     # liveness
GET /readyz      # readiness (dependencies reachable)
GET /__/version  # build version, commit, date

Point your load balancer at /readyz so a plane only receives traffic once Postgres and Redis are reachable.

Configuration

Server security

Introduction

Getting started

Core concepts

Routing

Policies

MCP

Observability

Operate

Admin API

API reference

Deployment

Topology

Docker

Kubernetes

Health & readiness

​Topology

​Docker

​Kubernetes

​Health & readiness

Topology

Docker

Kubernetes

Health & readiness