TrueFoundry AI Gateway Cloud platform

Overview

Interpret these fields: Self-hosted vs managed LLM gateways · Who still owns your LLM gateway?

What kind of product Category ?

Cloud platform Not verified

Marketplaces resell many providers behind one key. Gateways add governance on top. Open-source projects you run yourself. Cloud platforms are hyperscaler surfaces. Inference providers host models on their own hardware.

Who runs it Deployment model ?

Managed or self-host Not verified

Managed means the vendor operates it. Self-host means you run it on your own infrastructure. Both means you can choose.

Licence Licence ?

Proprietary Verified Aug 29, 2026

Proprietary products cannot be inspected or forked. Open licences such as MIT and Apache-2.0 let you audit, modify, and run the code without permission.

Company Company ?

TrueFoundry Not verified

The organisation that maintains the product.

Who you would be signing with Vendor status ?

Independent company Not verified

Whether the product is still an independent company, has been acquired, is a large cloud vendor’s product line, is run by a software foundation, or has been put into maintenance mode. Maintenance mode means bug fixes and security patches only — no new features.

Last shipped an update Latest release ?

2026-08-21 Not verified

The date of the most recent release or version tag. A product that has not shipped in a year is a different risk from one that shipped last week, regardless of what its marketing site says.

GitHub stars GitHub stars ?

Not published Not verified

A rough proxy for community size on open-source projects. Not a quality measure.

Cost

Interpret these fields: How LLM gateway pricing works · LLM gateway spending limits: stop a runaway agent bill? · Choosing a gateway for realtime voice agents

Markup on model prices Token markup ?

Not published Not verified

How much the product adds on top of what the underlying model provider charges. Zero means you pay the same per-token price you would pay the model provider directly.

Fee to add funds Credit purchase fee ?

Not published Not verified

A percentage charged when you top up your balance, separate from token prices. It is easy to miss because it does not appear on the per-token price list.

Monthly cost per person Seat fee ?

Not published Not verified

A recurring per-user platform charge that applies regardless of how much you use the models.

Can use your own provider accounts BYOK supported ?

Yes Verified Aug 29, 2026

Bring Your Own Key: you keep direct contracts with OpenAI, Anthropic and others, and the gateway only routes traffic. This preserves negotiated rates and committed-spend discounts.

Cost of using your own accounts BYOK terms ?

You connect your own provider accounts and keys; TrueFoundry bills by request tier, not tokens. Not verified

What the product charges to route traffic through your own provider keys.

Free tier Free tier ?

Developer plan $0/month: 50,000 requests/month, 3 users, 50,000 MCP tool calls, up to 10 saved prompts. Verified Aug 29, 2026

What you can do without paying, useful for evaluation.

Enterprise plan from Enterprise plan from ?

Not published Not verified

Annual entry price for the enterprise tier, where one is published or credibly reported.

Cost to run it yourself Self-host cost ?

No open-source edition; the data plane is proprietary. Vendor estimates roughly $600-$1,000/month of your own hosting cost to run the gateway (or control plus gateway) plane in your cloud, on top of the plan fee; fully managed SaaS carries no hosting cost. VPC, on-prem, air-gapped and multi-cloud installs are enterprise deployments, and a third-party review notes Helm-based ops effort is required. Verified Aug 29, 2026

What self-hosting actually costs once you account for infrastructure and any paid tier.

How the vendor makes money Pricing model ?

Flat monthly platform fee Not verified

The shape of the vendor’s bill: does the routing layer charge a percentage on top of tokens, a flat monthly fee, both, neither (because inference is the product), or nothing at all (open source with no paid tier).

How pricing works, briefly Pricing model detail ?

Free developer tier + flat monthly platform fee + per-unit usage overage + enterprise quote + optional self-host infra cost. Developer $0/mo, Pro $499/mo, Pro Plus $2,999/mo, Enterprise custom. TrueFoundry does not resell inference. Not verified

A one-paragraph description that covers the caveats a pricing category cannot: introductory rates, per-feature meters, tier gating, and pricing that resets on a specific date.

Minimum commitment Minimum commitment ?

None stated. Enterprise implied custom. Not verified

Whether the vendor requires a minimum contract term, a minimum spend, or a provisioned-capacity purchase to get its published rate.

Charges that fire after you go over an allowance Overage terms ?

Request overage priced in blocks: 2M requests and 5 API keys for additional $499/month; Pro Plus 'contact sales'. Self-hosting adds ~$600–$1,000/month of infrastructure cost when you self-host the Gateway or both the Control and Gateway planes. Log/trace retention overage and export cost not stated. Not verified

The line items that scale with usage after an included allowance is exhausted — log storage, extra requests, per-feature meters, data export — which is where cost estimates usually go wrong.

Prompt cache offered Cache mechanism ?

Both exact and semantic Not verified

Whether the gateway offers its own response cache, what kind of match it does (exact request, prefix, semantic), or simply passes provider caching through unchanged.

Discount on cached input Cache-read discount ?

Not published Not verified

How much cheaper cached tokens are than fresh input, when the vendor publishes a single figure. Bundled-inference clouds usually price this per model instead of as one number.

Premium on cache writes Cache-write premium ?

Not published Not verified

How much more the first write of a cached prefix costs versus a plain input token. A high write premium and a low hit rate can leave you paying more than you save, so this matters as much as the read discount.

Who captures the cache saving Cache economics ?

Exact ('Simple caching') and semantic caching both listed as features; provider passthrough not stated. No cached-token pricing published. TrueFoundry charges per request/platform, not per token, so caching cuts your provider bill and you keep the saving — but cached requests presumably still consume the tier's request allowance, and the feature list does not mark which tier includes semantic caching. Not verified

Whether the customer keeps the full saving from caching or the vendor captures part of it — and any conditions attached (write premium, storage fees, best-effort hits).

What you can split spend by Cost attribution ?

'Cost per team/user/model/application' plus custom metadata and metadata filtering. Per-key, per-tag and per-customer not stated. Not verified

The dimensions the vendor documents for splitting spend — per key, per user, per team, per tag, per customer. Matters if you need to chargeback internally or bill an end customer.

How you get cost data out Cost export ?

'Export to custom storage buckets', 'Data Lake Export', 'Connect multiple storage bucket' and 'Export to other monitoring platforms'. CSV, cost API and webhook export not stated; export pricing not stated. Not verified

The mechanisms the vendor publishes for exporting cost and usage data: CSV, an API, webhooks, S3, a data warehouse, or nothing at all. Any per-unit price is included.

Who pays the model bill BYOK mode ?

Your keys only Not verified

Whether you bring your own provider accounts (BYOK), buy inference from this vendor, or can do either. This is the single biggest commercial difference between these products: it decides who holds the contract with the model provider and who carries the spend.

Catalog

Interpret these fields: LLM gateway model counts: what “500+” means · Model aliases and deprecations: build an endpoint inventory · Choosing a provider for Qwen, DeepSeek, GLM or Kimi

Models available Models available ?

~1,000 Verified Aug 29, 2026

How many models you can call, shown as a range because several vendors publish different totals on different pages. Vendor-reported either way, so counts are not directly comparable — some count every provider variant of the same model separately.

Model providers reachable Upstream providers ?

27 Not verified

How many distinct model providers or labs you can reach, shown as a range where the vendor’s own pages disagree. More providers usually means better redundancy when one has an outage.

Works with standard OpenAI code OpenAI-compatible API ?

Yes Verified Aug 29, 2026

If yes, you can usually switch to it by changing one base URL, and switch away just as easily. This is the main defence against lock-in.

OpenAI chat endpoint POST /v1/chat/completions ?

Yes Not verified

The endpoint almost every application ports first. "Not documented" means the vendor never states it, which is different from a documented no.

Anthropic messages endpoint POST /v1/messages ?

Yes Not verified

Whether Anthropic-shaped calls work without rewriting them. Several products support this only as SDK compatibility or provider passthrough rather than a native endpoint — the detail page says which.

OpenAI Responses endpoint POST /v1/responses ?

Not documented Not verified

The newer stateful OpenAI surface. Support is much thinner across this market than chat completions.

Embeddings endpoint POST /v1/embeddings ?

Yes Not verified

Whether you can generate vectors through the same gateway, or need a second integration for retrieval workloads.

Image generation endpoint POST /v1/images/generations ?

Yes Not verified

Whether image models are reachable through the same surface as text.

Audio endpoints POST /v1/audio/* ?

Yes Not verified

Speech-to-text and text-to-speech. Frequently the first gap in an otherwise complete gateway.

Batch jobs endpoint POST /v1/batches ?

Yes Not verified

Asynchronous bulk processing, usually at a discount. Commonly undocumented, and commonly the reason a migration stalls late.

Needs the vendor’s own code library Requires a vendor-specific SDK ?

No Verified Aug 29, 2026

A proprietary client library spreads through your codebase and has to be torn out again if you leave. “No” is the better answer here, and it means the standard OpenAI client works.

You can export your request history Logs / usage data export ?

Yes Verified Aug 29, 2026

Whether you can get your own request logs, traces, or usage records back out — through an API, a bulk export, or a download. Decides whether you leave with your history or abandon it.

Settings can live in version control Declarative config-as-code ?

Yes Verified Aug 29, 2026

Whether routing, fallback, and budget rules can be declared in a file you keep in Git, rather than existing only as settings clicked into a hosted dashboard.

Embeddings Embeddings ?

Yes Verified Aug 29, 2026

Text-to-vector models, needed for search and retrieval features.

Image generation Image generation ?

Not published Not verified

Whether image models are reachable through the same interface.

Speech and audio Speech and audio ?

Not published Not verified

Text-to-speech or transcription models through the same interface.

Video generation Video generation ?

Not published Not verified

Whether video models are reachable through the same interface.

Batch processing Batch processing ?

Not published Not verified

Submitting large jobs for cheaper, slower processing. Often 50% off for work that is not time-sensitive.

Routing & reliability

Interpret these fields: How LLM gateway failover actually works · Does your LLM gateway promise any uptime? · Is routing destroying your prompt cache? · Changing models without breaking production · Choosing a gateway for realtime voice agents

Uptime it promises in writing Contractual SLA uptime ?

99.9% Not verified

The uptime percentage in a published, contractual service level agreement. A public status page is not an SLA — it reports what happened, it does not promise anything or pay you back when it breaks.

Automatic failover Automatic failover ?

Yes Verified Aug 29, 2026

When a model provider goes down or rate-limits you, traffic moves to a backup automatically instead of returning errors to your users.

Load balancing Load balancing ?

Yes Verified Aug 29, 2026

Spreads requests across several providers or keys to raise your effective rate limit.

Rule-based routing Conditional routing ?

Yes Verified Aug 29, 2026

Send different requests to different models based on rules — for example a cheap model for free users and a strong model for paying ones.

Response caching Response caching ?

Yes Verified Aug 29, 2026

Reuses the answer when the exact same request comes in again, which cuts both cost and latency.

Similar-question caching Semantic cache ?

Yes Verified Aug 29, 2026

Reuses an answer when a new question means roughly the same thing as an earlier one. Saves far more than exact-match caching but can return subtly wrong answers if tuned loosely.

Where you set the timeout Request timeout surface ?

Not documented Not verified

`not_documented` as a request-timeout key. What exists are SLA thresholds used for health, not for aborting a request: `sla_cutoff.time_to_first_token_ms` and `sla_cutoff.time_per_output_token_ms` ([TrueFoundry virtual models / fallback](https://www.truefoundry.com/docs/ai-gateway/fallback)).

Where a request timeout can be set: per request, in a config file, in the vendor dashboard, or nowhere. Nine of the twenty products documented here do not describe a request timeout at all, so the worst case of a hung upstream call is unknowable from the docs.

Where you set retries Retry policy surface ?

In config Not verified

`config_file` (also editable in the UI). `retry_config` with `attempts` (**default `0`**), `delay` (**default `100` ms**), and `on_status_codes` (**default `["429","500","502","503"]`**). Retries occur on the same target; backoff beyond the fixed `delay` is not documented ([TrueFoundry routing config](https://www.truefoundry.com/docs/ai-gateway/load-balancing-overview), [TrueFoundry virtual models / fallback](https://www.truefoundry.com/docs/ai-gateway/fallback)).

Where retry count and backoff are configured. Worth knowing alongside billing: a retried streaming call can be charged more than once.

Where you set fallbacks Fallback surface ?

In config Not verified

ORDERED for priority-based routing (`priority`, lower number = higher priority, `0` highest); fallback targets come from `load_balance_targets`, gated by `fallback_status_codes` (default `["401","403","404","408","429","500","502","503"]`) and `fallback_candidate` (default `true`). Ordering depends on strategy: latency-based puts lower-latency targets first; weight-based sticky routing tries remaining healthy targets in sequence and that order is explicitly "not weight-based" ([TrueFoundry virtual models / fallback](https://www.truefoundry.com/docs/ai-gateway/fallback)).

Where the fallback chain is defined. Almost every product claims fallback; the useful question is whether you can change it from code or only by hand in a dashboard.

Shape of the fallback chain Fallback shape ?

Ordered list Not verified

An ordered list tries targets in sequence; a weighted split sends a percentage of traffic to each, which is what you need to trial a new model on 5% of requests. Weighted splits are much rarer than the marketing implies.

Upstream health tracking Health checks / circuit breaking ?

In config Not verified

`config_file`, and it is passive health tracking plus cooldown ejection. The gateway "continuously monitors every target", marks failing targets unhealthy, moves them to the end of the list as last resort, and recovers automatically. Failure-based cooldown: 5xx/429/401/403, default threshold 2+ failures in a rolling 2-minute window. SLA-based cooldown (priority routing only) via `sla_cutoff.time_per_output_token_ms` / `time_to_first_token_ms`, averaged over a 3-minute rolling window using up to 10 samples with a minimum of 3; TTFT samples only come from streaming requests and TPOT samples require at least 30 output tokens ([TrueFoundry virtual models / fallback](https://www.truefoundry.com/docs/ai-gateway/fallback)). TrueFoundry's blog additionally describes classic circuit-breaker states (`closed`/`open`/`half_open`) as a pattern, but states no configuration keys for it ([TrueFoundry LLM failover blog](https://www.truefoundry.com/blog/llm-failover-load-balancing-provider-outages)).

Whether the product notices a failing upstream and stops sending traffic to it, and whether you can tune the thresholds. This is what turns a provider outage into a blip rather than a sustained error rate, and only four of the twenty expose it.

Cross-region failover you control Multi-region failover surface ?

In config Not verified

SaaS requests are auto-tagged with `tfy_gateway_region` and `tfy_gateway_zone`, and you route on them with `metadata_match` (documented examples `US → azure-us/gpt-4o`, `EU → azure-eu/gpt-4o`, `IN → azure-in/gpt-4o`, and `metadata_match: {tfy_gateway_zone: SFO}`), with a catch-all `priority: 1` target as the cross-region fallback. Both are true here: TrueFoundry runs multiple SaaS gateway regions AND you configure the cross-region target chain yourself ([TrueFoundry virtual models / fallback](https://www.truefoundry.com/docs/ai-gateway/fallback)). Multiple gateways can also be deployed cross-region under one control plane ([TrueFoundry gateway plane architecture](https://www.truefoundry.com/docs/platform/gateway-plane-architecture)).

Whether you can define what happens when a region degrades. A vendor running many regions is not the same as a vendor letting you configure failover between them; only three document a user-controlled mechanism.

Where you set load balancing Load balancing surface ?

In config Not verified

Weights supported: `routing_config.type` of `weight-based-routing` (integer `weight` 0–100, must sum to 100), `priority-based-routing`, `latency-based-routing` ("No weights needed", selection by recent TPOT), and `complexity-based-routing` (`simple`/`medium`/`complex`). Targets are catalog identifiers (`azure/gpt-4o`, `openai/gpt-4o`, `bedrock/llama`, `onprem/llama`), with `metadata_match`, `headers_override` and `override_params` per target; rules are evaluated in order and the first match wins ([TrueFoundry routing config](https://www.truefoundry.com/docs/ai-gateway/load-balancing-overview), [TrueFoundry virtual models / fallback](https://www.truefoundry.com/docs/ai-gateway/fallback)).

Where traffic distribution across upstreams or keys is configured.

Operations

Interpret these fields: LLM gateway observability: traces, logs and export · Changing models without breaking production · Running coding agents through an LLM gateway · Model aliases and deprecations: build an endpoint inventory

Usage dashboards and logs Observability ?

Yes Verified Aug 29, 2026

Built-in visibility into what was sent, what came back, what it cost, and how long it took.

Spending limits Budget controls ?

Yes Verified Aug 29, 2026

Hard caps that stop spend before it becomes a surprise invoice. The single most valuable control for a small team.

Rate limits Rate limits ?

Yes Verified Aug 29, 2026

Caps on request volume per key or per user, useful for protecting against abuse and runaway loops.

Separate keys per team or app Virtual keys ?

Not published Not verified

Issue scoped keys with their own budgets and permissions so you can attribute cost and revoke access without rotating everything.

Prompt versioning Prompt management ?

Yes Verified Aug 29, 2026

Store and version prompts outside your code so they can be changed without a deploy.

Quality testing Evals ?

Not published Not verified

Built-in tooling to score model output against test cases, so you can tell whether a model swap made things better or worse.

MCP support MCP support ?

Yes Verified Aug 29, 2026

Native support for the Model Context Protocol, the emerging standard for connecting models to external tools.

What gets logged Logged content ?

Your choice Not verified

Global logging mode is `HEADER_CONTROLLED` (default behaviour: log unless the header says otherwise), `ALWAYS`, or `NEVER`; logged requests, viewable under AI Gateway → Monitor → Requests, include request content, and sensitive values can be redacted per subject/model/metadata ([Request logging](https://www.truefoundry.com/docs/ai-gateway/request-logging))

Whether full prompts and responses are stored, only metadata, or nothing. Full-body logging is the most useful debugging feature here and the one most likely to need a conversation with your compliance team.

You can turn logging off Body-logging opt-out ?

Yes Not verified

Set the global mode to `NEVER`, or send `X-TFY-LOGGING-CONFIG: {"enabled": false}` (stringified JSON) per request; metrics dashboards remain populated ([Request logging](https://www.truefoundry.com/docs/ai-gateway/request-logging), [Metrics dashboard](https://www.truefoundry.com/docs/ai-gateway/analytics))

Whether prompt and response bodies can be suppressed while still keeping usage metrics. Nineteen of the twenty document a way to do this; the mechanisms range from a per-request header to an organisation-wide setting.

Traces you can take elsewhere Distributed tracing ?

OpenTelemetry Not verified

OpenTelemetry natively for both traces and metrics, with MCP tool and agent spans; trace storage is managed by TrueFoundry ([Export OpenTelemetry data](https://www.truefoundry.com/docs/ai-gateway/export-opentelemetry-data))

Whether the product emits OpenTelemetry, a proprietary format, or nothing. OpenTelemetry means the traces land in the tooling you already run instead of only in the vendor’s dashboard.

Where telemetry can go Export destinations ?

OpenTelemetry, Datadog, Prometheus, Grafana, S3, Webhook Not verified

OTLP exporters to Grafana Cloud, Datadog (OTLP), and AWS CloudWatch, plus any OTLP endpoint ([Export OpenTelemetry data](https://www.truefoundry.com/docs/ai-gateway/export-opentelemetry-data)); aggregated metrics download as CSV and per-datasource metrics APIs for model, MCP, guardrail, cache, routing, and agent metrics ([Metrics dashboard](https://www.truefoundry.com/docs/ai-gateway/analytics))

Documented sinks for logs and metrics. This is a good proxy for how replaceable the vendor’s own dashboard is: around twenty destinations means you never have to depend on it, while a CSV download means you do.

Can record user feedback Feedback capture API ?

No Not verified

`n.a.` — no feedback/score endpoint documented ([Metrics dashboard](https://www.truefoundry.com/docs/ai-gateway/analytics))

Whether there is an API to attach a rating or score to a logged request, which is what lets production traffic feed quality work later.

Scores live traffic Online eval hooks ?

No Not verified

`n.a.` on the fetched pages; the closest is `audit_mode_blocked`, a guardrail outcome that records what *would* have been blocked without blocking it ([Metrics dashboard](https://www.truefoundry.com/docs/ai-gateway/analytics))

Whether automated scorers can run against real production requests, rather than only against a test set you assemble yourself.

Performance

Delay it adds Proxy overhead ?

3 ms Verified Aug 29, 2026

Extra time the product itself adds to each request, on top of however long the model takes. Usually irrelevant next to multi-second model latency, but it matters for high-volume or streaming-sensitive workloads.

Requests per second ceiling Throughput ?

Not published Not verified

Published sustained request rate before the product becomes the bottleneck. Only relevant at genuinely high volume.

What the request path runs on Architecture class ?

Interpreted proxy Not verified

`interpreted_proxy` (JS/edge runtime). "The AI Gateway is written using the Hono framework", described as "ultra-fast, minimalistic, and is designed for the edge" ([TrueFoundry gateway plane architecture](https://www.truefoundry.com/docs/platform/gateway-plane-architecture)).

The comparable way to talk about latency here. An edge worker, a compiled Go or Rust binary, and a Python proxy have different overhead floors no matter which figures each vendor publishes. Products that never disclose their runtime are recorded as undisclosed rather than assumed.

You can run the request path yourself Self-hostable data plane ?

Yes Not verified

`yes`, but the artifact is not named on the fetched pages. Deployment is documented as SaaS, your VPC, on-prem or air-gapped, running as Kubernetes pods with readiness probes and optional `HTTP_PROXY`/`HTTPS_PROXY`/`NO_PROXY` forward-proxy env vars; no Docker image name or Helm chart name is stated ([TrueFoundry gateway plane architecture](https://www.truefoundry.com/docs/platform/gateway-plane-architecture), [TrueFoundry LLM failover blog](https://www.truefoundry.com/blog/llm-failover-load-balancing-provider-outages)).

Whether the component that actually carries your prompts can run on your own infrastructure. Distinct from a vendor offering a self-hosted control plane while still proxying traffic through their network.

Streaming responses Streaming support ?

Yes Not verified

Supported, with the most precise streaming-fallback semantics in this set: the gateway waits for the "first non-empty stream chunk", and if Anthropic returns `overloaded_error` before that chunk it falls back to the next eligible target. Separate caveat: `prompt_version_fqn` "does not work with agents (when using MCP/tools)". Note also that TTFT SLA samples are only recorded on streaming requests ([TrueFoundry routing config](https://www.truefoundry.com/docs/ai-gateway/load-balancing-overview), [TrueFoundry virtual models / fallback](https://www.truefoundry.com/docs/ai-gateway/fallback)).

Whether token-by-token streaming is documented. The caveats matter more than the yes: some products cannot cancel a stream without still being billed, and several timeout and fallback mechanisms stop applying once the first token has been sent.

Security & compliance

Interpret these fields: LLM gateway compliance: SOC 2, HIPAA and evidence · How LLM gateway guardrails fail · Which LLM gateways store your prompts? · Do you need an MCP gateway as well?

Does your prompt reach their servers Prompt transits vendor ?

Depends how you deploy it Not verified

Three genuinely different data paths: managed SaaS where request and response data flows through TrueFoundry's control plane; gateway-in-your-infrastructure where all LLM traffic stays with you and TrueFoundry is not in the live request path; and fully self-hosted, where everything except the authentication and analytics servers runs on your infrastructure.

Whether the text you send passes through this company’s own infrastructure. If it does, every other promise on this page is a policy commitment rather than a physical impossibility. Self-hosted products can answer no outright.

What they keep if you change nothing Logging default ?

Yes — prompts and replies Not verified

On hosted deployments logging happens unless you suppress it: absent or true in the logging-config header means logging occurs. You can control whether bodies are logged and redact patterns, and a deny rule always wins.

Defaults matter more than options. A product that stores full prompts and replies unless you find the right header will have stored them by the time you read the docs.

How long they keep it Default content retention (days) ?

90 days Not verified

Ninety days for SaaS blob storage, configurable. In self-hosted modes the control plane does no long-term retention.

Default retention for request content, in days. Zero means nothing is kept. Read the note: several products keep nothing as a rule but make timed exceptions for abuse review or specific models.

Could they train on your prompts Training on customer data ?

Not published — silence, not a no Not verified

Neither the security page nor the deployment docs address training.

Whether the vendor may use your prompts and outputs to train models. “Not published” means we could not find any position, which is not the same as a no — ask for it in writing.

Where it runs, and what you can pin Region and residency control ?

You choose the region where the gateway is deployed and where logs and traces are stored, and you can bring your own S3, Azure Blob or GCS bucket. Gateway planes run active-active across multiple regions. Not verified

Which regions are offered and whether you can force processing to stay in one. A global endpoint that silently picks a region is a different compliance story from an endpoint you pin yourself.

Where safety filters run Guardrail execution location ?

Either, depending on deployment Not verified

The gateway plane evaluates PII, prompt-injection and content-filtering policy in memory on the request path — and in self-hosted modes that plane is yours.

A filter that strips personal data only helps if it runs before the data leaves your boundary. If guardrails execute in the vendor’s cloud, the vendor has already received whatever you wanted redacted.

Who else touches the data Subprocessor list ?

https://www.truefoundry.com/docs/platform/security-and-compliance Not verified

The published list of third parties the vendor passes your data to. No list means you cannot know the full chain, which most data-protection agreements require you to.

SOC 2 audited SOC 2 audited ?

Yes Verified Aug 29, 2026

An independent audit of security controls. Enterprise buyers and their procurement teams routinely require it.

Will sign a HIPAA agreement HIPAA BAA ?

Not published Not verified

Required before you may send protected health information through the service. Without a signed BAA, healthcare data is off limits.

GDPR commitments GDPR commitments ?

Yes Verified Aug 29, 2026

Published data processing terms for handling personal data of people in the EU and UK.

Can keep data in the EU EU data residency ?

Not published Not verified

Requests can be processed inside the EU rather than routed to US infrastructure. Often the deciding constraint for European customers.

Does not retain your data Zero data retention ?

Not published Not verified

Prompts and responses are not stored after the request completes. Sometimes a paid add-on rather than the default.

Strips personal data PII redaction ?

Yes Verified Aug 29, 2026

Detects and removes identifiers such as names, emails, and card numbers before the request reaches the model provider.

Content guardrails Content guardrails ?

Yes Verified Aug 29, 2026

Policy checks on inputs and outputs — blocking unsafe content, enforcing formats, or catching prompt-injection attempts.

Runs fully disconnected Air-gapped deployment ?

Yes Verified Aug 29, 2026

Can be deployed in a network with no internet access, which some regulated and defence environments require.

Blocks personal data in prompts PII / DLP enforcement ?

Can block the request Not verified

Built-in PII Detection and Azure AI Language PII/PHI guardrails ([Guardrails overview](https://www.truefoundry.com/docs/ai-gateway/guardrails-overview)). Custom plugins distinguish mutation from validation: a Presidio `POST /pii-redaction` plugin returns `transformed: true` with a full replacement `requestBody` to redact, whereas a Guardrails-AI `POST /pii-detection` plugin "only detects and reports PII without redacting it" ([Custom guardrails](https://www.truefoundry.com/docs/ai-gateway/custom-guardrails))

Whether personal data detection sits on the request path and can stop the call, merely inspects and forwards it, or is not documented. A control that only reports is a logging feature, not a policy control.

Blocks prompt injection Injection / jailbreak enforcement ?

Can block the request Not verified

Azure Prompt Shield is a built-in guardrail integration; external options include Model Armor, Prisma AIRS, CrowdStrike, and NeMo ([Guardrails overview](https://www.truefoundry.com/docs/ai-gateway/guardrails-overview))

Whether injection and jailbreak detection can stop a request. Most products offering this call a partner classifier rather than shipping their own.

Blocks harmful content Toxicity / moderation enforcement ?

Can block the request Not verified

Azure Content Safety moderation and OpenAI Moderations are supported; blocked requests return a configurable `custom_error_message` ([Guardrails overview](https://www.truefoundry.com/docs/ai-gateway/guardrails-overview), [Guardrails configuration](https://www.truefoundry.com/docs/ai-gateway/guardrails-configuration))

Whether hate, violence, sexual and self-harm categories are checked inline and can stop a request, in either direction.

Your own policy rules Custom policy hooks ?

Can block the request Not verified

Policy forms: built-in Regex and Secrets Detection rules, plus custom HTTP plugins bound to lifecycle hooks `llm_input`, `llm_output`, `mcp_tool_pre_invoke`, `mcp_tool_post_invoke`, returning either a validate verdict or a mutated request body ([Guardrails overview](https://www.truefoundry.com/docs/ai-gateway/guardrails-overview), [Guardrails configuration](https://www.truefoundry.com/docs/ai-gateway/guardrails-configuration), [Custom guardrails](https://www.truefoundry.com/docs/ai-gateway/custom-guardrails))

Whether you can add your own rule — a regex, a webhook, or your own classifier — rather than choosing from the vendor library.

Where guardrails run Guardrail execution location ?

Either, your choice Not verified

Whether guardrail evaluation happens inside your infrastructure or on the vendor’s servers. This decides whether the prompt you are trying to protect leaves your network in order to be checked.

If the guardrail itself fails Guardrail failure mode ?

Not documented Not verified

`not_documented` as a global fail-open/fail-closed rule. For custom plugins, HTTP 4xx/5xx from the plugin signals a "processing or dependency failure only; not used for 'PII found' policy outcomes", which separates infrastructure failure from a policy verdict but does not state the resulting request disposition ([Custom guardrails](https://www.truefoundry.com/docs/ai-gateway/custom-guardrails))

What happens when the guardrail service times out or errors: does the request proceed unchecked, or is it blocked? This is the worst-documented field in the entire catalogue — only two vendors state it plainly, which means most teams are running a control whose failure behaviour they cannot know.

Third-party guardrail vendors Guardrail integrations ?

Azure AI Language, Azure Content Safety, OpenAI Moderation, Microsoft Presidio Not verified

Named external guardrail services the product can call. A long list means the product is a router for policy engines rather than a policy engine itself — which also means another vendor bill and another hop.

Fit & integration

Interpret these fields: How much does an LLM gateway lock you in? · Changing models without breaking production · Running coding agents through an LLM gateway · Do you need an MCP gateway as well? · Choosing a gateway for realtime voice agents · Choosing a provider for Qwen, DeepSeek, GLM or Kimi

Work to try it Evaluation work shape ?

Set it up in a cloud console Not verified

The shape of the work on the vendor’s own quickstart, from swapping one base URL through to deploying infrastructure. An ordinal class rather than a duration, because elapsed time depends on accounts and quota we cannot see.

Work to run it Production work shape ?

Deploy it on your infrastructure Not verified

The same scale applied to the vendor’s recommended production path. For several products this is much heavier than the quickstart, which is exactly why both are recorded.

Steps on the quickstart Numbered quickstart steps ?

4 Not verified

A literal count of numbered steps on the vendor’s quickstart, recorded as evidence beside the work shape. Zero means the page publishes no numbered procedure at all. Large counts usually mean interleaved language tracks rather than more work.

Can you self-host it today Self-host install documentation ?

Offered, but no command published Not verified

No literal install command is published on the self-hosting pages; they document topologies and prerequisites only ([Self-hosting of Gateway - TrueFoundry Docs](https://www.truefoundry.com/docs/ai-gateway/gateway-self-hosted), [Deploy AI Gateway - TrueFoundry Docs](https://www.truefoundry.com/docs/platform/deploy-control-plane-and-gateway-plane))

Whether an install command is actually published. Several products advertise self-hosting while publishing no command to start from, which a plain yes/no would hide.

Works with the OpenAI SDK OpenAI SDK drop-in ?

Yes Not verified

Yes. TrueFoundry documents OpenAI-compatible drop-in usage by changing the client `base_url` and API key; the documented SaaS base URL is `https://gateway.truefoundry.ai`, while self-hosted examples use `{GATEWAY_BASE_URL}`. ([TrueFoundry AI Gateway quick start](https://www.truefoundry.com/docs/ai-gateway/quick-start))

Whether an existing OpenAI-compatible client can be pointed at it by changing the base URL and key.

Vercel AI SDK support AI SDK provider package ?

Not documented Not verified

n.a. (not documented)

Whether a first-party AI SDK provider package exists, or only a community package, a documented workaround, or the generic OpenAI provider pointed at a custom base URL.

Python framework integrations Documented Python frameworks ?

LangChain, LangGraph, LlamaIndex Not verified

TrueFoundry documents ready-to-use LangChain and LlamaIndex snippets. The LangChain integration uses `pip install langchain-openai` and the `ChatOpenAI` class; LangGraph examples use `StateGraph`, `MessagesState`, and related workflow APIs. ([TrueFoundry LangChain integration](https://www.truefoundry.com/docs/ai-gateway/langchain))

LangChain, LangGraph, LlamaIndex and similar orchestration frameworks with a documented integration.

Callable from Cloudflare Workers Cloudflare Workers support ?

Not documented Not verified

n.a. (not documented)

Whether the docs show calling this product from your own Worker. Deliberately separated from the several products whose own gateway runs on Workers, which is a fact about their infrastructure and not about your edge compatibility.

Kubernetes install Helm chart availability ?

Official Helm chart Not verified

The AI Gateway can be deployed on Kubernetes using the `tfy-llm-gateway` Helm chart at `https://github.com/truefoundry/infra-charts/tree/main/charts/tfy-llm-gateway`. A separate full TrueFoundry control-plane and gateway-plane installation uses the `truefoundry` chart from `https://github.com/truefoundry/infra-charts/tree/main/charts/truefoundry`. ([TrueFoundry deployment overview](https://www.truefoundry.com/docs/platform/deployment-overview))

Whether a named, published Helm chart exists, versus Helm being referenced with no chart named, versus generic cluster documentation that has nothing to do with this product.

Terraform support Terraform provider or modules ?

Terraform code in the repo only Not verified

TrueFoundry states that its software ships with OpenTofu/Terraform code, but no official Terraform provider, module, or Terraform Registry name is documented. ([TrueFoundry deployment overview](https://www.truefoundry.com/docs/platform/deployment-overview))

Whether you can declare this in code: an official provider, official modules, resources inside a hyperscaler’s provider, a community provider, or only Terraform code shipped in a repo.

Reuses your cloud identity Cloud IAM reuse ?

Reuses your cloud identity Not verified

Yes for platform-level cloud access: TrueFoundry documents AWS IAM Roles for Service Accounts (IRSA, `sts:AssumeRoleWithWebIdentity` with the `eks.amazonaws.com/role-arn` annotation) and GCP GKE Workload Identity; Azure is listed as "Coming Soon". ([TrueFoundry docs - access cloud services with IAM](https://www.truefoundry.com/docs/access-data-from-s3-or-other-clouds-services))

Whether you can authenticate with IAM roles, workload identity or managed identities instead of another long-lived API key. Distinguished from products that only accept static upstream provider credentials.

Fits behind your API gateway API gateway integration ?

Not documented Not verified

n.a. (not documented)

Whether AI traffic can go through a gateway you already run, and who documented that — the product’s vendor or the gateway’s.

MCP support MCP surface shape ?

MCP gateway or registry Not verified

TrueFoundry documents an MCP Gateway that centralizes access to MCP servers, with dynamic tool discovery and invocation, a curated registry, and support for remote, virtual, OpenAPI, and stdio MCP servers over streamable HTTP. It also documents centralized authentication and combining tools from multiple MCP servers through Virtual MCP Servers. ([TrueFoundry MCP Gateway overview](https://www.truefoundry.com/docs/ai-gateway/mcp/mcp-overview))

Which kind of MCP support this is: a gateway that governs many MCP servers, a hosted MCP server you connect to, MCP tools accepted inside the completion API, or client tooling. These are different products behind one acronym.

Needs your own provider key Upstream provider key required ?

Required Not verified

Effectively yes to have any model: "Select the provider you want to add models from and add models after providing API Key," though the page does not state a first-call rule explicitly ([Quick Start Guide: Setup & Integration - TrueFoundry Docs](https://docs.truefoundry.com/gateway/quick-start))

Whether an upstream provider account and key must exist before your first call works. A prerequisite rather than a step, and it can differ between the hosted and self-hosted forms of the same product.

Gate before models work Model access gate ?

Not documented Not verified

n.a. (not documented) on the quickstart, self-hosting or pricing pages ([Quick Start Guide: Setup & Integration - TrueFoundry Docs](https://docs.truefoundry.com/gateway/quick-start), [Deploy AI Gateway - TrueFoundry Docs](https://www.truefoundry.com/docs/platform/deploy-control-plane-and-gateway-plane))

Whether an enablement click, a quota grant, a paid tier or an approval form stands between a valid key and a working model call.

Official client languages First-party client SDK languages ?

Python, Node.js, Go, Rust, Java Not verified

Documented client and integration formats include OpenAI SDK, LangChain, LangGraph, Google ADK, LlamaIndex, Go-OpenAI, Rust-OpenAI, LangChain4j, Node.js, cURL, REST, and streaming APIs. Official OpenAI Agents SDK packages are `openai-agents` for Python and `@openai/agents` for JavaScript/TypeScript; documented classes include `Agent`, `Runner`, `OpenAIChatCompletionsModel`, and `AsyncOpenAI`. ([TrueFoundry OpenAI Agents SDK integration](https://www.truefoundry.com/docs/ai-gateway/openai-agents-sdk))

Languages with a first-party client library. An empty list can still mean the product is usable from any language via an OpenAI-compatible SDK.

Additional charges

These are the fees that do not appear on a per-token price list, and they are where estimates usually go wrong.

• Pro plan $499/month (1M requests, 10 users)
• Pro Plus plan $2,999/month (1M requests, 25 users)
• Request/key overage $499/month per additional 2M requests and 5 API keys