Palo Alto Bought Portkey. Enterprise Routing Is Now a Security Product.
The May 29, 2026 acquisition of Portkey by Palo Alto Networks shows that at enterprise scale, 'routing' is being absorbed into governance, DLP, and compliance stacks — not sold as a standalone smart-picker. The durable surface is control, not intelligence.
On May 29, 2026, Palo Alto Networks announced it would acquire Portkey. The deal closed the same day the market digested the intent letter from late April. For anyone tracking the router category, the move was less about “better model selection” and more about who now owns visibility into AI traffic at scale.
Portkey was never primarily a “pick the best model” engine. It was an observability and gateway layer. Palo Alto wanted the pipe.
What Portkey actually sold
Before the acquisition, Portkey’s surface was:
- A gateway that sat in front of LLM calls.
- Observability, logging, and tracing for every prompt and completion.
- Basic routing, fallbacks, and cost controls.
- Enterprise features around access control and audit.
The value was not in magical intelligence that chose the right model better than a human with a policy file. The value was seeing what was flowing through the models — who was calling what, how much, with what data.
That is exactly the surface a security company wants when AI usage moves from experiments to production workloads handling regulated data.
Why PANW wanted it
Palo Alto’s statements and the product positioning made the intent clear. Lee Klarich (Chief Product Officer) and the acquisition narrative emphasized “visibility into AI traffic” and integrating AI usage into the broader Prisma AIRS (AI Runtime Security) story.
This was not about replacing your local router with a smarter one. It was about:
- DLP scanning prompts and responses at the gateway.
- Compliance logging and retention for every AI interaction.
- Governance policies that apply across the enterprise, not per-developer.
- Feeding AI traffic into the same security fabric that already handles network, endpoint, and cloud.
In other words: routing at this scale is becoming a security and compliance product, not a developer productivity tool.
The implication for OSS and local tools
When the big money moves from “smart router” startups to security incumbents buying gateways for visibility, it tells you where the durable enterprise surface lives.
For open-source and local-first tools, the lesson is the same one the rest of the graveyard has taught:
- The intelligence layer (model selection, learned routers, preference models) has repeatedly proven fragile and low-moat.
- The control layer (policy you own, keys you own, logs you keep locally, no phone-home) is what survives provider changes and company pivots.
Portkey’s acquisition does not kill local routing. It clarifies what enterprises are actually willing to pay for at scale: governance and visibility, not a better picker.
RoutePlane as the local control plane
We build RoutePlane as a single-binary daemon that runs on your machine or in your environment. It does not phone home. Your routing policy is a YAML file you control. Your keys never leave your boundary unless you send them to the provider.
When enterprise teams need the security stack (DLP, audit, Prisma-style governance), they can layer that on top — or buy the PANW offering. When they need a router that keeps working when the catalog changes, when a provider bans a path, or when they are offline, the local control plane is still there.
We are not competing to be the enterprise gateway that Palo Alto just bought. We are the escape hatch and the honest local surface that does not pretend to be the security product.
What this means if you route your own traffic
If your organization is evaluating routers today, ask the question the acquisition forces:
- Do you want the router that becomes part of someone else’s compliance and DLP product?
- Or do you want the router whose only job is to apply your policy to your keys, locally, with no hidden dependencies?
The category is consolidating. Some of it is going into marketplaces (OpenRouter). Some of it is going into security platforms (Portkey → PANW). The part that remains independent and durable is the one that treats the router as infrastructure you own, not intelligence you rent.
CTA: Enterprise teams still need a local router they control. If you route your own traffic and want the control plane that does not phone home, see pricing or the activation guide.
Sources and references (as of 2026-07): Palo Alto Networks acquisition announcement for Portkey (April 30 intent, May 29 2026 close); public statements from Lee Klarich and Rohit Agarwal on AI traffic visibility and Prisma AIRS integration; Portkey pre-acquisition product pages (observability + gateway positioning); trillions of tokens referenced in enterprise AI traffic discussions. Specific internal metrics from the acquired company are not public.