Everyone wants to be the AI gateway
Blog post from Lago
AI gateways are increasingly important control points between applications or agents and the models, tools, APIs, or resources that execute requests, but the term covers several distinct functions rather than a single product category. Recent reported acquisitions and product launches, including Stripe’s potential purchase of OpenRouter and Palo Alto Networks’ acquisition of Portkey, reflect competition to control this middle layer, where providers can influence routing, policy, security, observability, cost, and access decisions. The text identifies four overlapping gateway roles: model routing across providers, traffic control and technical governance, agent access management for tools and credentials, and commercial control over what customers may consume under payment or entitlement rules. Although products in these categories are converging in features, they differ in buyers, distribution channels, business incentives, and the customer relationships they own. Lago argues that commercial control is an underdeveloped function requiring a separate layer that evaluates contracts, commitments, credits, pricing, and balances in real time, while execution gateways continue to provide usage and cost data; its integrations with services such as Cloudflare AI Gateway are intended to apply customer-specific billing policies without replacing the underlying execution infrastructure.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| MCP | 3 | 8,729 | 854 | 211 | -20% |
| LLM | 1 | 5,068 | 1,020 | 229 | -34% |
| Observability | 1 | 3,175 | 737 | 186 | -24% |
| Platform Engineering | 1 | 1,191 | 259 | 79 | -17% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.