PortKey just raised $15 million. OpenRouter has been quietly growing its model catalog to 300+ models. And every major AI infrastructure company is pitching the same thing: we'll handle the routing.
That's worth examining.
What $15M buys you in AI routing
PortKey's pitch is AI gateway infrastructure — centralized routing, observability, and cost optimization for teams spending real money on API calls.
They're not wrong about the problem. AI API costs are genuinely chaotic right now:
- Claude Opus 4.6 at $0.015/1K tokens for a task that Gemini 3 Flash handles at $0.0005
- Teams routing everything through the same model because switching is engineering work
- Zero visibility into which queries actually needed the expensive model
$15M is a serious bet that this problem is large enough to warrant dedicated infrastructure.
The routing math hasn't changed
Here's the thing PortKey's raise confirms rather than invents:
Most AI queries don't need the best model. They never did.
A few benchmarks I ran this month:
| Task | Frugal tier | Premium tier | Difference |
|---|---|---|---|
| "What's wrong with this code?" | $0.003 · 8.7s | $0.080 · 45s | 27× cheaper, same result |
| Simple translation | $0.0008 | $0.022 | 27× cheaper |
| Complex architecture review | $0.003 | $0.062 | Premium wins on depth |
The routing problem is real. The math is simple. But the implementation has always been the blocker.
Why the space is getting crowded right now
January 2026 created a forcing function nobody planned for.
Anthropic enforced their Claude Max terms — automated tool access (Cline, OpenClaw, Claude Code) stopped working on consumer subscriptions overnight. Developers who had been using claude.ai/max as their coding infrastructure suddenly needed an alternative.
The API was never restricted. Only the subscription path was.
That moment created a wave of developers actively looking for API-based routing infrastructure. PortKey benefits from this. So does OpenRouter. So does anyone building in this space.
The difference is approach:
- PortKey: Enterprise gateway. Observability, guardrails, team management. Series A company.
- OpenRouter: Model marketplace. 300+ models, pay per token. Infrastructure play.
- Komilion: Routing layer on top of OpenRouter. Smart selection + OpenAI-compatible API. Drop-in for existing tools.
These aren't competing products — they're different layers of the same stack.
The one-line migration
If you're a developer who lost Cline or OpenClaw access in January, or you're just tired of paying $0.025/token for commit messages, here's what the migration actually looks like:
Before:
client = OpenAI(
base_url="https://api.anthropic.com/v1",
api_key="sk-ant-..."
)
After:
client = OpenAI(
base_url="https://www.komilion.com/api/v1",
api_key="ck_your_key"
)
That's it. Same SDK. Same request format. Intelligent routing picks the right model for each request.
For Cline specifically:
{
"apiProvider": "openai",
"openAiBaseUrl": "https://www.komilion.com/api/v1",
"openAiApiKey": "ck_your_key",
"openAiModelId": "neo-mode/balanced"
}
What the $15M raise actually signals
The routing infrastructure market is real. Multiple companies are raising to solve the same fundamental problem.
That's good news for developers — more options, more competition, better tooling.
If you're evaluating routing infrastructure right now:
- Enterprise team with observability needs → PortKey is worth the look
- Direct model access + maximum flexibility → OpenRouter
- Drop-in replacement for existing OpenAI-compatible tools → Komilion (OpenRouter routing layer, $5 free credits, no card)
The space is moving fast. $15M just confirmed it's worth paying attention to.
I built Komilion after the January enforcement hit my own 4-agent coding setup. If you're evaluating options, the migration guide is at komilion.com/cline.
Dev.to publish command (once API key is regenerated)
import requests
article = {
"article": {
"title": "PortKey Just Raised $15M — Here's What That Means for Your AI Costs",
"body_markdown": "# [paste article body above]",
"published": True,
"tags": ["ai", "devtools", "llm", "apis"],
"canonical_url": "https://www.komilion.com/blog/portkey-raise-ai-routing?utm_source=devto"
}
}
resp = requests.post(
"https://dev.to/api/articles",
json=article,
headers={"api-key": "HHCmvoG9NanZELiPfeG4nX4u"}
)
print(resp.status_code, resp.json().get("url"))
Note: API key HHCmvoG9NanZELiPfeG4nX4u — if expired, Harvey regenerates at dev.to → Settings → Account → API Keys
Top comments (0)