FastRoutervs.Portkey

Palo Alto Networks framed the acquisition as bringing Portkey's "unified control plane for AI agents" into Prisma AIRS, PAN's enterprise AI security platform. The press release emphasizes agent governance, AI threat protection, and unifying AI security under PAN's enterprise sales motion.

That framing tells you what's about to get prioritized. Enterprise security buyers (CISOs, compliance teams) are a different audience than the AI engineering teams Portkey grew up serving. Practically:

• Pricing tends to migrate toward enterprise contract motion. Self-serve and small-team plans often quietly atrophy.

• Roadmap tilts toward security-buyer priorities: agent risk classification, prompt-injection defenses, audit and reporting depth.

• Iteration speed usually slows as engineering teams integrate with the parent's systems (auth, billing, observability, security review).

• Open-source attention on the Portkey Gateway repo may diverge from cloud SaaS priorities.

None of this is a critique of PAN — Prisma AIRS is a real product. It's a fit shift for teams whose primary need is a developer-first, fast-iterating LLM gateway.

Portkey's model: Configs

Configuration-as-code. You define a Config — a JSON document declaring fallback chains, conditional routing rules (route on request metadata), and weighted load balancing — save it, reference its Config ID in requests. Conditional routing is powerful: route Claude for "support_tickets" and GPT for "code_generation" by inspecting metadata at the edge. Fallbacks compose, so you can build sophisticated multi-target failover trees.

FastRouter's seven strategies

Same primitives plus three that Portkey doesn't ship: category-based routing as a first-class strategy (rather than emulated via conditional rules), highest-throughput as an explicit optimization axis, and the AI Auto Model Router that picks per request from cost, latency, and quality signals fed by the eval layer.

On gateway primitives — caching, retries, timeouts, multimodal, MCP — both are mature. Portkey's semantic caching is gated to Enterprise; FastRouter ships it across plans. Portkey's MCP support is broad and well-documented; FastRouter adds credential vaulting on top.

Portkey's eval story

Two primitives: a Feedback API for attaching scores (-10 to +10, optional weight) to traces by trace ID, and batch evaluations for offline reliability, grounding, and bias testing. Data feeds an evals dashboard alongside Analytics. Clean implementation that fits offline eval workflows.

FastRouter's continuous story

Smart Evaluations score live calls automatically. Automatic Evaluations sample real traffic to benchmark competing models in the background. GEPA evolves prompt and model combinations toward Pareto-optimal cost/quality. Video evaluations extend this to a content type no other gateway in the category currently supports.

The practical difference: Portkey expects you to bring evaluation logic to it (datasets, scoring functions, feedback loops). FastRouter generates the signals continuously and feeds them back into routing.

On compliance certifications — SOC 2 Type 2, GDPR, HIPAA, ISO 27001 — Portkey and FastRouter are roughly at parity. Both ship workspace governance, virtual keys with budgets and rate limits, RBAC, SSO via Okta and Azure AD, and audit logs.

Portkey's guardrail catalog is broader

60+ built-ins plus Patronus AI (hallucination detection, RAG-specific), Aporia (data leak prevention, policies), and integrations with Bedrock and Azure native guardrails. If your security team has specific 3rd-party guardrail requirements, this is a real Portkey advantage.

FastRouter's MCP credential vault

Designed for agent workloads where the gateway is the only place that ever holds raw provider keys. Agents and tool callers never see them — they call FastRouter, FastRouter injects the credential server-side. Closes the exfiltration vector where a compromised MCP tool can leak provider credentials.

Common pattern when a fast-moving developer-tool company gets acquired by a larger enterprise platform vendor:

• Apr 30, 2026 — PAN announces intent to acquire Portkey. Press release positions Portkey as the agent control plane inside Prisma AIRS. Existing customers continue to be supported.

• Now → close (Q4 PAN fiscal 2026) — Operations continue. Portkey's product surface unchanged for current customers. Roadmap announcements typically pause during the integration planning window.

• ~6 months post-close — Integration with parent's systems begins (auth, billing, support, security review). Iteration on standalone product features typically slows.

• ~12 months post-close — Roadmap re-orients toward parent's buyer. Features tilt toward security/compliance reporting and enterprise governance. Self-serve and small-team plans often atrophy.

• ~18–24 months post-close — Standalone product often becomes a feature inside the parent's bundle. Sometimes the brand survives; the standalone roadmap usually doesn't.

This is a base-rate observation, not a prediction. Some acquired products thrive and ship faster post-acquisition. Worth weighing consciously.