Notifications
Clear all
Topic starter
20/08/2026 6:07 pm
TL;DR: Bifrost vs Portkey is framed as a choice between self-hosted performance control and packaged production operations by TruFoundry, while also noting Portkey’s acquisition by Palo Alto Networks and the implications for roadmap ownership, security packaging, and enterprise governance.
NHIMG editorial — based on content published by TruFoundry: Bifrost vs Portkey: Pricing, Gateway Features, and Enterprise Fit Compared
By the numbers:
- Bifrost reports 11 microseconds of overhead at 5,000 RPS in its own benchmarks, which it uses to argue for performance-focused self-hosting.
- Portkey’s Production plan costs $49 per month and includes 100,000 recorded logs, giving teams a published entry point for managed gateway operations.
Questions worth separating out
Q: How should teams govern AI gateways that route model and tool traffic?
A: Teams should treat the gateway as the control boundary for identity, spend, logging, and policy enforcement.
Q: Why do AI gateways create new access control decisions for IAM teams?
A: Because gateways can inject identity context, mediate tool use, and decide which requests reach models or downstream systems.
Q: What breaks when MCP tools are governed separately from model routing?
A: You get partial control.
Practitioner guidance
- Define the gateway control boundary Document which enforcement points belong in the gateway, which belong in IAM or PAM, and which remain application-side.
- Validate MCP tool exposure controls Test whether the gateway can consistently govern tool access, not just model calls, and verify how authorisation is applied to MCP-connected workflows.
- Review deployment and residency assumptions Check whether the gateway must remain inside your VPC, whether logs can stay under your retention rules, and whether a managed cloud option changes your compliance posture.
What's in the full article
TruFoundry's full analysis covers the operational detail this post intentionally leaves for the source:
- Pricing table context for open-source, production, and enterprise tiers that informs procurement decisions
- Detailed feature-by-feature notes on guardrails, logs, traces, budgets, and MCP support across the two platforms
- Additional explanation of the acquisition context and how it may affect roadmap ownership and support expectations
- Practical buyer guidance for choosing between self-hosted control and managed operations in production AI environments
👉 Read TruFoundry’s full comparison of Bifrost vs Portkey for AI gateway governance →
Bifrost vs Portkey: what it means for AI gateway governance?
Explore further
20/08/2026 6:42 pm
AI gateways are becoming identity enforcement points, not just routing infrastructure. Once model traffic, tool calls, budgets, and logs converge in one layer, the gateway starts to function like an access control plane for AI workloads. That makes identity, authorisation, and auditability part of the same design conversation. The practical conclusion is that teams should govern gateways as security controls, not platform plumbing.
A question worth separating out:
Q: When should organisations choose self-hosted AI gateways over managed ones?
A: Choose self-hosted gateways when deployment boundary, residency, and control over runtime behaviour are first-order requirements. Choose managed gateways when operational simplicity, packaged observability, and support matter more than direct infrastructure ownership. The right answer depends on whether policy needs to stay inside your environment or can be delegated.
👉 Read our full editorial: Bifrost vs Portkey shows the governance gap in AI gateways
