Skip to main content

Start from one of these shapes rather than from a blank values file. Each one is a supported combination of the three planes, with a known footprint and an install guide you can follow from top to bottom.

If the terms control plane, data plane and inference plane are new, read the three planes first. Every shape here uses the same chart; what changes is which planes you run and which ones NeuralTrust runs for you in the EU or US region.

​
At a glance

Node counts are the minimum of an autoscaled node pool with the Firewall on CPU. Running the Firewall in your cluster adds nodes to any shape; the full table, including GPU pools, is in Capacity.

​
1. Hybrid

The default, and the shortest path to production. You run TrustGate and TrustGuard in one cluster; NeuralTrust runs the console, analytics and the ML detectors in your region. Hybrid architecture: your environment holds one cluster running TrustGate, TrustGuard, data-plane-api and DataAgent, with recommended Redis and PostgreSQL datastores below it. Your apps send requests to TrustGate on :8081 for LLM traffic and :8082 for MCP; TrustGate calls out to LLM providers and asks TrustGuard to evaluate them. TrustGuard sends text to the NeuralTrust inference plane, a NeuralTrust-operated Firewall of ML detectors at firewall.neuraltrust.ai (EU) or firewall.us.neuraltrust.ai (US), over outbound 443; the Firewall is stateless and stores nothing, and a note shows it can run in-cluster instead with global.firewall.deploy: true. The cluster also opens outbound 443 connections to NeuralTrust SaaS for AgentGateway and TrustGuard config sync, telemetry ingest and DataBridge retrieval, carrying metadata only; nothing dials in. Hybrid architecture: your environment holds one cluster running TrustGate, TrustGuard, data-plane-api and DataAgent, with recommended Redis and PostgreSQL datastores below it. Your apps send requests to TrustGate on :8081 for LLM traffic and :8082 for MCP; TrustGate calls out to LLM providers and asks TrustGuard to evaluate them. TrustGuard sends text to the NeuralTrust inference plane, a NeuralTrust-operated Firewall of ML detectors at firewall.neuraltrust.ai (EU) or firewall.us.neuraltrust.ai (US), over outbound 443; the Firewall is stateless and stores nothing, and a note shows it can run in-cluster instead with global.firewall.deploy: true. The cluster also opens outbound 443 connections to NeuralTrust SaaS for AgentGateway and TrustGuard config sync, telemetry ingest and DataBridge retrieval, carrying metadata only; nothing dials in.

​
2. Gateway only

TrustGate on its own, governing LLM and MCP traffic between your applications, agents and model providers, with no TrustGuard in the path.

​
3. Detection only

TrustGuard on its own, as a detection API your applications, your existing gateway or your agent hooks call synchronously before they decide how to enforce.

​
4. Hybrid, region resilient

Two Hybrid clusters in two regions, active/passive, for a request path that has to survive losing a whole cloud region. Two Hybrid data-plane clusters in active/passive across two regions. Clients reach global LLM and MCP URLs that a customer-operated traffic manager points at the active cluster. Both clusters pull the same gateway-scoped configuration from NeuralTrust SaaS over outbound 443 and keep their own last-known-good copy. Both use one shared writable PostgreSQL primary with a cross-region read replica promoted on failover, while each cluster runs its own region-local Redis. Only the active cluster runs DataAgent. Two Hybrid data-plane clusters in active/passive across two regions. Clients reach global LLM and MCP URLs that a customer-operated traffic manager points at the active cluster. Both clusters pull the same gateway-scoped configuration from NeuralTrust SaaS over outbound 443 and keep their own last-known-good copy. Both use one shared writable PostgreSQL primary with a cross-region read replica promoted on failover, while each cluster runs its own region-local Redis. Only the active cluster runs DataAgent. Your cloud regions and the NeuralTrust region are independent: two clusters in two of your regions still enrol into the one NeuralTrust region your tenant lives in.

​
5. Self-hosted

Every plane in your cluster except the ML detectors. The console, product control planes and analytics run next to the data plane; the only connection to NeuralTrust is TrustGuard’s scoring call to the hosted inference plane. Self-hosted architecture: the platform runs in your environment. Clients call TrustGate on :8081 for LLM traffic and :8082 for MCP, and TrustGate calls TrustGuard on :8081. An in-cluster control plane — console and API on :8000, AgentGateway admin on :8080, and the TrustGuard control plane on :8080 — serves configuration to TrustGate and TrustGuard. TrustGate and TrustGuard emit OTLP to a collector on :4317 and :4318 that writes to in-cluster ClickHouse; DataCore and AlertEngine read from it. PostgreSQL and Redis are recommended datastores outside the cluster, and there is no DataAgent. The one connection that leaves your environment by default is TrustGuard calling the NeuralTrust inference plane over outbound 443: a hosted, stateless Firewall of ML detectors at firewall.neuraltrust.ai (EU) or firewall.us.neuraltrust.ai (US) that scores text and stores nothing. A note shows the Firewall can run in-cluster instead with global.firewall.deploy: true. Self-hosted architecture: the platform runs in your environment. Clients call TrustGate on :8081 for LLM traffic and :8082 for MCP, and TrustGate calls TrustGuard on :8081. An in-cluster control plane — console and API on :8000, AgentGateway admin on :8080, and the TrustGuard control plane on :8080 — serves configuration to TrustGate and TrustGuard. TrustGate and TrustGuard emit OTLP to a collector on :4317 and :4318 that writes to in-cluster ClickHouse; DataCore and AlertEngine read from it. PostgreSQL and Redis are recommended datastores outside the cluster, and there is no DataAgent. The one connection that leaves your environment by default is TrustGuard calling the NeuralTrust inference plane over outbound 443: a hosted, stateless Firewall of ML detectors at firewall.neuraltrust.ai (EU) or firewall.us.neuraltrust.ai (US) that scores text and stores nothing. A note shows the Firewall can run in-cluster instead with global.firewall.deploy: true.

​
6. Self-hosted, air-gapped

Architecture 5 with the Firewall in your cluster and images from your own registry. Nothing connects to NeuralTrust at runtime. The steps are the Self-hosted install with the air-gapped settings from its Network section and Mirror to your own registry.

​
7. Multi-cluster, one console

A central control plane you run, with data planes in other clusters enrolled into it. Each data plane keeps its raw payloads; the console, alerting and cross-cluster reporting live in one place. Central control plane architecture: remote Hybrid clusters each run the request path — TrustGate on :8081 and :8082 and TrustGuard on :8081 — with their own recommended PostgreSQL and Redis, where raw payloads are stored. Each remote cluster opens four outbound connections on 443 to your central cluster: one config-sync endpoint each for AgentGateway and TrustGuard, the telemetry ingest gateway, and DataBridge. The central cluster runs the console and API on :8000, both product control planes on :8080, a collector on :4317 and :4318, ClickHouse, DataCore, and AlertEngine, plus recommended PostgreSQL and Redis of its own, and never dials into a remote one. TrustGuard calls the NeuralTrust inference plane over outbound 443: a hosted, stateless Firewall of ML detectors at firewall.neuraltrust.ai (EU) or firewall.us.neuraltrust.ai (US). It is the only connection that leaves your environments by default, and a note shows the Firewall can run in-cluster instead with global.firewall.deploy: true. Central control plane architecture: remote Hybrid clusters each run the request path — TrustGate on :8081 and :8082 and TrustGuard on :8081 — with their own recommended PostgreSQL and Redis, where raw payloads are stored. Each remote cluster opens four outbound connections on 443 to your central cluster: one config-sync endpoint each for AgentGateway and TrustGuard, the telemetry ingest gateway, and DataBridge. The central cluster runs the console and API on :8000, both product control planes on :8080, a collector on :4317 and :4318, ClickHouse, DataCore, and AlertEngine, plus recommended PostgreSQL and Redis of its own, and never dials into a remote one. TrustGuard calls the NeuralTrust inference plane over outbound 443: a hosted, stateless Firewall of ML detectors at firewall.neuraltrust.ai (EU) or firewall.us.neuraltrust.ai (US). It is the only connection that leaves your environments by default, and a note shows the Firewall can run in-cluster instead with global.firewall.deploy: true. The data planes here are installed exactly like a TrustGate or TrustGuard data plane, pointed at your domain instead of at NeuralTrust.

​
Make any of them resilient

Every architecture starts at tier 1 of the availability ladder — one cluster, replicas across three zones, managed PostgreSQL and Redis — and that is enough for most deployments. Climb further only for a failure you actually have to survive.

High availability

The four tiers, what each survives, and what changes per deployment model.