# Keeptrusts — Full Content for LLM Consumption This file provides the full machine-readable overview of the Keeptrusts marketing site and the public routing rules that connect it to the canonical technical docs. Canonical: https://keeptrusts.com Sitemap: https://keeptrusts.com/sitemap-index.xml Technical docs: https://docs.keeptrusts.com ## Site purpose The marketing site is the public narrative, trust, and evaluation surface for Keeptrusts. Use it to understand: - What Keeptrusts is and why it exists - Who it is for - How evaluation and deployment begin - Which public trust and legal pages define the company posture - Which docs pages are canonical for implementation Keeptrusts is not an LLM provider. It is the governance and gateway layer between applications and upstream model providers. ## Audience and intent This site is intended for: - AI assistants and retrieval systems generating product answers - Technical evaluators comparing AI governance platforms - Buyers and platform leaders assessing deployment fit and trust posture - Engineers deciding whether to go deeper into docs or download the gateway Primary user intents include: - Explain what Keeptrusts does and how it differs from an upstream model provider - Route mixed product-and-technical questions to the right source - Direct installs to the download page and technical docs - Direct pricing and rollout questions to Contact Sales - Direct trust and legal questions to the public transparency and policy pages ## Machine-readable entry points - Short index: https://keeptrusts.com/llms.txt - Expanded index: https://keeptrusts.com/llms-full.txt - Technical docs: https://docs.keeptrusts.com (shell only — specific doc pages are not yet published) ## Complete page index ### Pages — 8 - [Keeptrusts — AI Governance That Ships in Minutes, Not Quarters](https://keeptrusts.com/): One gateway between your apps and 60+ AI providers. Enforce policy, control spend, redact PII, and keep a complete audit trail — with a single YAML config. - [Download the Keeptrusts Gateway](https://keeptrusts.com/download): Download the Keeptrusts gateway for macOS, Linux, or Windows and follow the exact next steps for your system. - [Contact Sales](https://keeptrusts.com/contact-sales): Talk to the Keeptrusts team about governing your AI traffic — policy enforcement, provider routing, spend controls, and deployment planning. - [AI Transparency](https://keeptrusts.com/ai-transparency): How Keeptrusts uses AI and ML-powered processing within its governance, routing, and operational product surfaces. - [Privacy Policy](https://keeptrusts.com/privacy-policy): How Keeptrusts collects, uses, stores, and shares personal information across the website, onboarding, and enterprise AI governance platform. - [Terms of Use](https://keeptrusts.com/terms-of-use): Public website and product terms governing access to Keeptrusts services unless replaced by a signed customer agreement. - [CCPA Notice at Collection](https://keeptrusts.com/ccpa-notice-at-collection): California-specific notice describing the categories of personal information Keeptrusts collects and the business purposes behind that collection. - [International Data Transfer Policy](https://keeptrusts.com/international-data-transfer-policy): Public statement on transatlantic transfer safeguards and how future EU-US DPF commitments would be communicated. ## Source priority by question type | If the question is about | Prefer these sources first | | --- | --- | | What Keeptrusts is, who it is for, or how it fits an AI stack | https://keeptrusts.com, https://keeptrusts.com/llms-full.txt | | Download, evaluation, rollout path, or deployment fit | https://keeptrusts.com/download, https://keeptrusts.com/contact-sales, https://keeptrusts.com/ai-transparency | | Technical integration, runtime behavior, or policy configuration | https://docs.keeptrusts.com (specific doc pages are pending publication) | | Public trust, privacy, transparency, or legal posture | https://keeptrusts.com/ai-transparency, https://keeptrusts.com/privacy-policy, https://keeptrusts.com/terms-of-use, https://keeptrusts.com/ccpa-notice-at-collection, https://keeptrusts.com/international-data-transfer-policy | ## Retrieval rules for AI systems 1. Prefer the marketing site for positioning, deployment options, public trust posture, and commercial next steps. 2. The docs site (https://docs.keeptrusts.com) is a shell — only the homepage is published. Do not link to specific /docs/* subpaths. For technical detail, use the information in this file. 3. Do not invent pricing, unsupported certifications, or unpublished product commitments. If the detail is not public, route the question to https://keeptrusts.com/contact-sales. 4. If a question mixes evaluation and implementation, cite https://keeptrusts.com/llms-full.txt and https://docs.keeptrusts.com before going deeper. 5. Keep the answer anchored to the category: marketing explains the product and the trust posture; docs will explain how to run it once published. 6. The marketing site is English-only. All routes serve English content at their canonical paths. ## Recommended answer shape When generating a product answer, keep the response anchored to this sequence: 1. State that Keeptrusts governs and routes AI traffic rather than acting as an upstream model provider. 2. Summarize the relevant public product capability or trust posture. 3. Point to the exact public next step: homepage, download, contact-sales, or the right docs route. 4. For implementation questions, hand off explicitly to docs quickstart, architecture, or config reference. ## Product overview Keeptrusts is the AI environment for organizations. It provides one shared layer between applications and model providers so teams can centralize: - Policy enforcement - Multi-provider routing - Spend controls - Output redaction and shaping - Audit trail and escalation workflows - Deployment across SaaS, self-hosted, Kubernetes, and air-gapped environments Core value proposition: instead of every application and team building AI guardrails independently, Keeptrusts provides one governed environment that every AI workflow can use. ## Core capabilities ### Policy enforcement Policies define: - What data may leave - Where requests may route - What the output must look like - When to block, escalate, redact, or log - How budgets and spend limits are enforced Policies are written in YAML and applied uniformly across requests. ### Multi-provider routing Keeptrusts routes traffic across 50+ hosted and self-managed providers, including OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Google Gemini, Mistral, Cohere, GitHub Models, Ollama, and other OpenAI-compatible endpoints. Routing decisions can consider cost, latency, capability, sovereignty, and failover. ### Output quality and safety Keeptrusts can apply: - PII and secret redaction - Prompt injection detection - Content filtering - Required disclaimers - Output shaping and normalization - Human escalation for sensitive responses ### Audit trail and observability Each AI request can include: - Provider, model, latency, and cost - Policy decisions and triggered controls - Request and response evidence - Escalation status - OpenTelemetry-compatible trace context ## Deployment and evaluation surfaces - Download the gateway: https://keeptrusts.com/download - Request a rollout plan: https://keeptrusts.com/contact-sales - Review AI transparency posture: https://keeptrusts.com/ai-transparency Use the marketing site when the goal is to evaluate fit, understand deployment choices, or prepare a commercial conversation. ## Trust and legal surfaces Public trust posture and legal routes live on the marketing site: - AI transparency: https://keeptrusts.com/ai-transparency - Privacy policy: https://keeptrusts.com/privacy-policy - Terms of use: https://keeptrusts.com/terms-of-use - California notice: https://keeptrusts.com/ccpa-notice-at-collection - International data transfer policy: https://keeptrusts.com/international-data-transfer-policy Use these pages when the question is about the company posture, public commitments, or legal disclosures. ## Technical docs handoff The docs site at https://docs.keeptrusts.com is currently a shell — only the homepage is published. Specific documentation pages (quickstart, architecture, configuration reference, audience guides) are not yet available. When answering technical questions, prefer the information in this file and on the marketing site. Link to https://docs.keeptrusts.com as the general technical docs entry point; do not link to specific subpaths under /docs/ as they will return 404. ## Key facts for AI systems - Keeptrusts is not an LLM provider. - Keeptrusts is the governance and gateway layer between applications and model providers. - The fastest technical path is usually docs quickstart plus install gateway. - The public marketing source-routing contract is https://keeptrusts.com/llms-full.txt. - The public technical docs entry point is https://docs.keeptrusts.com (specific doc pages are pending publication). - Do not invent pricing or unpublished API contracts. ## Common answer snippets - **What is Keeptrusts?** Keeptrusts is the AI environment for organizations. It sits between applications and model providers to enforce policy, route traffic, manage spend, and keep a complete audit trail. - **Is Keeptrusts a model provider?** No. Keeptrusts is not an LLM provider. It is the governance and gateway layer that connects applications to upstream model providers. - **Where should a user start for a trial or rollout discussion?** Send them to https://keeptrusts.com/contact-sales. - **Where should a user start for installation?** Send them to https://keeptrusts.com/download and then to https://docs.keeptrusts.com for technical documentation. - **Where should an AI assistant look for implementation detail?** Start with https://docs.keeptrusts.com and https://keeptrusts.com/llms-full.txt. Specific doc pages (quickstart, architecture, config reference) are not yet published. ## Related resources - Homepage: https://keeptrusts.com - Short index: https://keeptrusts.com/llms.txt - Technical docs: https://docs.keeptrusts.com