Keeptrusts is the AI environment for organizations. It sits between your application and AI providers to route traffic, enforce policy, improve output quality, and keep a complete, queryable request history. It is not a model or provider — it is the infrastructure layer that connects, governs, and observes AI traffic.

Why do teams add Keeptrusts?

Teams add Keeptrusts when there is no shared environment for routing, guardrails, spend control, and audit history. Without one, each application starts becoming its own AI platform — rebuilding the same policy and observability logic independently. Keeptrusts provides that shared layer once, for every workflow.

Does Keeptrusts work with major AI providers?

Yes. Keeptrusts supports 50+ hosted and self-managed providers, including OpenAI (GPT-4, GPT-4o, o1, o3), Anthropic (Claude), Azure OpenAI, AWS Bedrock, Google Gemini, Mistral, Cohere, GitHub Models, and local models served via Ollama or vLLM.

How quickly can Keeptrusts be deployed?

Most teams connect a first workflow in under a day. Keeptrusts runs in cloud (SaaS), on-premises, Kubernetes clusters, or fully air-gapped environments. Applications typically only need to change one environment variable — the base URL — with no other code modifications.

How is Keeptrusts different from a regular API gateway?

Traditional API gateways handle authentication and routing for REST traffic. Keeptrusts understands AI request semantics — it evaluates the content of prompts and responses to enforce policies such as PII redaction, harmful-content blocking, compliance disclaimers, and escalation to human review. These are not possible with a generic proxy.

Does Keeptrusts support HIPAA, GDPR, and the EU AI Act?

Yes. Keeptrusts ships with policy templates for HIPAA (PHI redaction, audit trail), GDPR (data minimization, erasure workflows, cross-border routing restrictions), EU AI Act (human oversight, risk classification logging, Article 13 transparency), and financial services regulations including FINRA and SEC requirements.

What happens to prompts and responses — does Keeptrusts store them?

By default yes — this forms the audit trail. Keeptrusts can be configured to skip storage, to mask specific fields before storage, or to apply a retention window for automatic deletion. For air-gapped deployments, data never leaves the customer's network.

Does Keeptrusts increase AI response latency?

In most environments, negligibly. The Keeptrusts gateway is a Rust binary with a very low-overhead policy evaluation path. The additional round-trip latency is typically 1–5ms depending on policy complexity.

Can Keeptrusts work with local or self-hosted models?

Yes. Any model served via an OpenAI-compatible HTTP endpoint — including Ollama, vLLM, llama.cpp server, and LM Studio — works with Keeptrusts. The gateway treats them identically to hosted providers.

What AI governance policies can Keeptrusts enforce?

Keeptrusts can enforce policies including: PII and secret redaction from inputs and outputs, content classification and blocking, provider and model routing (including failover), spend limits per team or use case, mandatory disclaimers on AI-generated content, escalation to human review, prompt-injection detection, data sovereignty routing (keeping requests in specific geographic regions), and output format normalization.

One AI
Every Model
Every Provider

Keeptrusts is superpowering the future of Value creation using AI.

Talk to Us

One AI Every Model Every Provider

One AI
Every Model
Every Provider