Skip to main content
TrustGate (open source, Apache-2.0) is a purpose-built reverse proxy for LLM and agent traffic. Point any OpenAI-, Anthropic-, or Responses-API client at it and TrustGate normalizes, routes, load-balances, governs, and observes every call — without changing your application code beyond its base URL and consumer credentials. You operate TrustGate from the NeuralTrust console: create gateways, connect providers, define consumers and routing, attach policies, and copy connection snippets. Day-to-day configuration does not require calling a control-plane API.

​
Why a gateway

Putting TrustGate between your apps and your model providers gives you one control point for:
  • Multi-provider access — first-class adapters for OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Google Gemini, Vertex AI, Groq, Mistral, and DeepSeek (plus any OpenAI-compatible endpoint), behind one OpenAI-compatible surface.
  • Smart routing & load balancing — simple routing, fallback chains, round-robin, weighted, least-connections, random, and smart routing by complexity label (Simple / Medium / Hard).
  • Cost & abuse control — request rate limiting, token/dollar LLM Budget, and request-size guards.
  • Tool & prompt governance — allow-list, validate, and reshape the tools an agent can call; inject and version system prompts; restrict which models a consumer may reach.
  • Guardrails — built-in TrustGuard, OpenAI Moderation, Azure Content Safety, and AWS Bedrock guardrail policies to inspect prompts and responses inline.
  • Multi-tenancy & auth — per-gateway consumers authenticated by API key, OAuth2, or OIDC, with policies scoped globally or per consumer.
  • Observability — rich per-request telemetry (model, tokens, cost, latency breakdown, routing attempts, policy chain) exported with OpenTelemetry and used by detection alerts.
  • Agent tooling — a dedicated MCP plane exposes MCP servers and tools to agents with full OAuth2 support.

​
The building blocks

Configure everything in the console under TrustGate. Six objects make up a gateway:

​
How a request flows

A client never names a provider URL or key — it names a model (or uses auto when load balancing / smart routing is enabled), and the gateway resolves the registry, applies policies, and forwards. See Architecture for the full lifecycle.

​
Where to go next

Console map

Sidebar areas — Registry, Identity, Consumers, Policies, Activity, Playground, Settings.

Quickstart

Create a gateway, connect a provider, and send your first request from the console.

Core concepts

Gateways, registries, consumers, auth, policies, roles.

Admin API

REST control plane for automation and self-hosted setups.