Portkey vs TrueFoundry (2026): AI Gateways Compared — and Where Kosmoy Fits

Three shapes on the same ten axes. Portkey (orange) and TrueFoundry (violet) both peak on Gateway & Policy Control and score well on observability; TrueFoundry reaches further on agent containment and (off-radar here) model serving, Portkey on model breadth and prompt tooling. Both cluster low on the compliance and inventory axes — the gateway category's signature. Kosmoy (blue) trades some raw gateway breadth for reach across inventory, compliance and agent containment. Read it as area: the two gateways compete on one spoke; the suite covers the web.

Observability and prompt tooling. Full request/response logging, 21+ analytics metrics, FinOps/executive dashboards (Portkey observability) and a versioned Prompt Engineering Studio give Portkey a deep, integrated operational surface.

Model breadth and low operational overhead. One API to 250+ LLMs / 1,600+ models across 45+ providers, delivered as managed SaaS with an MIT open-source core — no Kubernetes cluster to run to get started, where TrueFoundry is Kubernetes-native.

Turnkey guardrails. 20+ deterministic checks plus LLM-based checks with synchronous blocking (HTTP 446) and streaming output guardrails, integrated in the platform.

A full ML platform, not just a gateway. TrueFoundry adds vLLM/TGI/Triton model serving with autoscaling and canary deploys, fine-tuning jobs and fractional GPUs (MIG/time-slicing) on Kubernetes — deepened by the June 2026 Seldon AI acquisition. Portkey has no serving or fine-tuning layer.

Stronger agent containment and resilience. Per-agent identity with token/cost quotas, cost-velocity circuit breakers and instant tool revocation, plus TrueFailover (January 2026) for degradation-aware multi-model/multi-region failover.

Self-hosted depth and independence. A documented Kubernetes-native air-gapped install with no outbound dependencies for defense and regulated finance, Gartner AI-Gateways recognition, and an independent, actively shipping roadmap — where Portkey's is now inside Palo Alto Networks.

Both Portkey and TrueFoundry answer “how do we route, serve and govern AI traffic?” Neither answers “what AI are we running across the organization, is it compliant against a named framework, and what happens when an agent misbehaves?” TrueFoundry extends the gateway toward ML infrastructure; Kosmoy extends it toward governance. Those are different frontiers.

Kosmoy includes the gateway both products are — one OpenAI-compatible policy point with guardrails, RBAC, budgets and logging — but wraps it in the three layers a gateway leaves out: a risk-tiered inventory of every model, MCP server and agent (including a master agent registry that pulls from Foundry, Bedrock, Vertex, Salesforce and ServiceNow); EU AI Act, ISO 42001 (aligned) and NIST AI RMF evidence built from registry state plus gateway logs; and kernel-enforced Action Capsule containment for agents that act.

So the honest framing is not “Kosmoy beats Portkey and TrueFoundry at being a gateway” — they are capable gateways, and TrueFoundry adds real ML-platform depth Kosmoy does not. It is that a gateway is one spoke. If the requirement is the governance web — inventory, gateway, compliance and containment in one self-hosted platform — that is a suite decision, not a gateway or ML-platform decision.

For a team whose problem genuinely is model traffic — and, for TrueFoundry, model serving — pick on the axis that matters: Portkey for a managed control plane with observability and prompt depth, TrueFoundry for a Kubernetes-native platform that serves and fine-tunes as well as routes. Both offer self-hosted paths and OpenAI-compatible endpoints, so a later move is largely a configuration exercise.

For an enterprise that has to prove control over all of its AI — not just route and serve it — the choice is not between these two platforms but between infrastructure breadth and governance breadth. Kosmoy can sit in front of either: some teams keep TrueFoundry for serving and GPUs while Kosmoy holds the inventory, compliance evidence and containment for what reaches production.