The LLM-gateway you pick in July 2026 is not the one you'd have picked in January, because four of the options moved under you. TensorZero shut down. Helicone was acquired by Mintlify and slid into maintenance mode. Palo Alto Networks announced its intent to acquire Portkey. And LiteLLM — the default everyone reaches for — shipped malware to PyPI. A market that looked settled six months ago is a different map now, and the thing that changed the math is a Go-based newcomer called Bifrost.

Here's the decision, starting with the news that forces it.

What actually happened in 2026#

That churn is the reason the boring "which gateway" question got interesting.

The features already converged — so stop comparing them#

All three of the survivors do the same core things: an OpenAI-compatible API over many providers, automatic fallbacks and load balancing, semantic caching, budget and spend controls, and MCP support. If you build a feature-comparison spreadsheet, the columns come out nearly identical. That's the tell. When everyone ships the same feature list, the decision drops down a layer — to what the proxy is actually made of.

"Which gateway?" has quietly become "which language do you trust in your hot path, and which vendor is still standing?"

The real axis: Go vs Python in your hot path#

A gateway is a thin proxy that sits in front of every model call. Its overhead is a tax you pay on every request, so the runtime substrate matters more than any feature.

Migrating is a base-URL swap#

Because all three are OpenAI-compatible, moving between them is a configuration change, not a rewrite. If you point an OpenAI client at LiteLLM today:

from openai import OpenAI
client = OpenAI(base_url="http://localhost:4000", api_key="sk-litellm")

then trialing Bifrost is the same client with a different base URL:

from openai import OpenAI
# Bifrost speaks the OpenAI API — same SDK, new endpoint
client = OpenAI(base_url="http://localhost:8080/v1", api_key="sk-bifrost")

That near-zero switching cost is what makes the runtime axis actionable: you can benchmark the same traffic through each proxy on your own box and read the latency and memory numbers yourself before committing.

The decision#

The larger point is that gateways stopped being a feature race and became an infrastructure decision. The winner isn't the one with the longest feature list — every survivor has the same list. It's the one whose runtime you'd trust in your hot path and whose vendor you expect to still be there next quarter. In 2026, that question has a much shorter list of good answers than it did in January.