SaaS: nothing to install
In the NeuralTrust console, open TrustGate, select New Gateway, and then select SaaS. NeuralTrust provisions and operates the data plane; you can continue directly to Quickstart.Private (Hybrid): install the data plane
Private keeps management in the NeuralTrust SaaS control plane while LLM and MCP traffic pass through a data plane in your environment.1
Create the Private gateway
In the NeuralTrust console, select New Gateway → Private and enter a name.
2
Choose a runtime
- Kubernetes — recommended for production.
- Docker — recommended for local evaluation and development.
- Manual — for custom deployment systems.
3
Deploy and bootstrap
Follow the generated instructions to deploy the data plane. Enter one bootstrap
Dataplane URL, then select Save and Finish.
4
Set service URLs
Open Settings → Agent Gateway → General and set or verify the separate
LLM URL and MCP URL. Then return to the provider, request, and trace flow in
Quickstart.The generated Docker quick path exposes the LLM/proxy service only. Use Kubernetes or a
full deployment when you need MCP.
Hybrid deployment
The full Private data-plane install, from architecture to high availability.
Choose a model
Compare SaaS, Hybrid, External, and a central control plane.
Configuration
Configure the services in your environment.
Secrets
Supply deployment credentials securely.
Cloud notes
EKS, AKS, GKE, and vanilla Kubernetes particularities.
Troubleshooting
Install, pod, and config-sync failures.
Advanced: open-source self-hosting
The public TrustGate repository also supports fully self-managed deployments. That path is separate from NeuralTrust console onboarding. Day-to-day product guides in these docs assume the console (SaaS or Private data plane managed from NeuralTrust). For operators running the binary yourself, see TrustGate on GitHub and the control-plane API. The repository quick start (scripts/install.sh or make up) gives you:
- A local stack of Postgres and Redis plus the three TrustGate planes in Docker.
Kafka is not part of it. The Postgres role and database are both
trustgate. - Planes on
:8080(admin),:8081(proxy / LLM), and:8082(MCP), each with/healthz. - A generated
SERVER_SECRET_KEY. It is required — at least 32 random bytes — and the process refuses to start without it. The installer andmake upcreate it for you; supply your own elsewhere withopenssl rand -base64 32.