Portkey Is Becoming Part of Palo Alto Networks: What AI Gateway Buyers Should Know

What is happening with Portkey?

The short answer: On April 30, 2026, Palo Alto Networks announced its intent to acquire Portkey, one of the leading AI-first gateways, for $140 million per PANW’s 10-Q filing. The deal is expected to close in Palo Alto’s fiscal Q4 2026. Portkey will become the AI gateway for Prisma AIRS, Palo Alto’s AI security platform. For Palo Alto customers, that’s a deeper security integration. For everyone else evaluating AI gateways, it changes what Portkey is: a component of a cybersecurity platform rather than an independent infrastructure layer.

This post lays out the facts, what they validate about the category, and the questions buyers should be asking now. We’re a competitor, so weigh our perspective accordingly. We’ve kept the analysis to verifiable facts plus clearly labeled opinion. For the full competitive landscape, see our 2026 enterprise AI gateway comparison.

What did Palo Alto Networks actually announce?

The facts from the announcement and filings:

• Intent to acquire announced April 30, 2026; expected close in Palo Alto’s fiscal Q4 2026, subject to customary conditions.
• Total consideration of $140 million in cash and replacement awards, per Palo Alto’s SEC 10-Q.
• Portkey “will serve as the AI Gateway for Prisma AIRS,” described as the central control plane to monitor, route, and govern AI agent traffic within Palo Alto’s AI security platform.
• Palo Alto stated it will continue to support existing and new Portkey customers, with benefits from “tighter integration with Prisma AIRS.”

What does the acquisition validate?

Three things, and they matter for every buyer in this category:

1. The AI gateway is now recognized as mission-critical infrastructure. Palo Alto’s own framing calls the AI gateway the control plane for autonomous agents. When the largest cybersecurity company buys into a category, the category is real.
2. Agent traffic governance is the battleground. The acquisition rationale centers on agents as “highly privileged insiders” whose traffic must be monitored and governed. That is exactly the problem enterprise gateways exist to solve.
3. AI-first gateways needed a bigger platform to serve enterprises. Portkey was arguably the most enterprise-ready of the AI-first generation of gateways. Its path to enterprise scale ran through acquisition by a platform company rather than independent growth. That says something about how hard enterprise-grade is to retrofit.

What should current Portkey customers consider?

If you’re running Portkey today, nothing breaks tomorrow. Palo Alto has committed to supporting existing customers. But acquisitions of this shape have predictable dynamics worth planning for:

• Roadmap reorientation. The stated destination is Prisma AIRS integration. Expect the roadmap to prioritize security platform use cases. Features that served Portkey’s original developer and platform-team audience may receive less investment. Industry reviews were already flagging post-acquisition continuity as an open question for teams committed to the managed tier.
• Packaging and pricing changes. Standalone products absorbed into platforms commonly migrate toward platform bundles over time. If you are not a Palo Alto shop, model what your renewal looks like inside a Prisma-centric portfolio.
• The open-source core vs. the hosted tier. Portkey’s gateway core is Apache 2.0, but most differentiated value (observability, semantic caching, guardrails, compliance) lives in the hosted tier, which is the part most subject to integration decisions.

None of this is criticism of Portkey, which built a genuinely good product. It’s diligence any infrastructure buyer should do when a vendor’s ownership and mission change.

What does this mean if you’re evaluating AI gateways right now?

Our opinion, stated plainly: the acquisition sharpens a question every buyer should ask. Is your AI gateway a traffic-and-governance problem or a security product?

We think it’s the former. Routing, failover, cost attribution, onboarding, and policy enforcement are traffic infrastructure concerns. Security is one policy domain among several that the gateway enforces, alongside budgets, access, and resilience. A gateway owned by a security vendor will naturally see the world through a security lens, and if your primary pains are cost visibility, provider resilience, and standardized developer onboarding, that lens may not match your priorities.

It also raises the neutrality question. The value of a gateway grows with the breadth of what it connects: every provider, every framework, every cloud, every adjacent tool. Independence is a feature. For working definitions of what an LLM gateway, AI gateway, and MCP gateway actually are, see our explainer on gateway types.

How does Tetrate compare for teams reassessing their options?

Tetrate’s position is the inverse of the Palo Alto/Portkey construction: we are a traffic-infrastructure company that added AI governance, not a security company absorbing a gateway.

• Open foundation, by its co-creators. Tetrate Agent Router is built on Envoy AI Gateway, the first CNCF-backed open-source AI gateway, co-developed by Tetrate and Bloomberg, with no commercially gated features in the open core.
• Independent and neutral. Provider-neutral, model-neutral, framework-agnostic, and not owned by a model provider, cloud, or security platform.
• Enterprise architecture, not enterprise packaging. Dedicated instances with data planes in your own AWS, Azure, or GCP VPC or on-prem, one logical control plane, SSO/LDAP, per-team cost attribution, MCP catalogs, and inline guardrails built on the FINOS AI Governance Framework.
• Security as enforced policy, not as the product. PII redaction, prompt-injection blocking, and transaction controls run in the request path, and existing guardrail solutions plug in, so security teams keep their tools while engineering keeps the control plane.

Frequently asked questions

Has the Portkey acquisition closed? As of this writing, the deal was announced April 30, 2026 and is expected to close in Palo Alto Networks’ fiscal fourth quarter of 2026, subject to customary closing conditions. Check current filings for status.

Will Portkey continue as a standalone product? Palo Alto has stated it will support existing and new Portkey customers and that Portkey will serve as the AI gateway for Prisma AIRS. The long-term standalone packaging is not publicly detailed.

Is Portkey’s open-source gateway affected? The open-source core is Apache 2.0 licensed, which protects existing code. Future investment priorities for the open-source project versus the platform integration are the open question.

Should I migrate off Portkey? Not reflexively. If you’re a Palo Alto customer consolidating on Prisma AIRS, the integration may serve you well. If you chose Portkey as neutral infrastructure, it’s reasonable to re-run your evaluation with ownership and roadmap direction as criteria. Because most gateways, including ours, are OpenAI-compatible, switching costs are primarily in policy migration rather than application changes.

Tetrate Agent Router Enterprise is the independent, Envoy-based AI gateway: CNCF open-source foundation, in-VPC deployment, per-team cost attribution, and inline guardrails. Book a demo if you’re re-running your gateway evaluation.

Sources

• Palo Alto Networks press release (April 30, 2026)
• Palo Alto Networks Q3 FY2026 10-Q (Portkey acquisition, $140M)
• ChatForest Portkey review (post-acquisition continuity analysis)