Agentgateway

Name: Agentgateway
Brand: Solo

Leader

Reimagining infrastructure for cloud & AI

Est 2017|Valuation $1B|Raised $171.8M|9 Ref Customers

LinkedIn 19K|Website|Web traffic 43K|FTEs 180|HQ Cambridge, MA

MarketsFoundation Models Agent Builder Platforms API & AI Gateways with MCP MCP Gateways Dedicated Enterprise MCP Gateways MCP Security Gateways

Platform CoversAI Security Platforms MCP Gateway AI Agent Authentication and Authorization

01Competitive Landscape

| Aspect | Agentgateway (Solo.io / Linux Foundation project) | LiteLLM | Portkey | |--------|---------------|----------------|----------------| | Starting Price | Open source available; enterprise pricing not publicly listed | Open source + paid offerings (varies by vendor packaging) | Commercial SaaS (pricing varies by vendor) | | Recommended For | Teams needing MCP/A2A and tool governance with a Kubernetes-native gateway option and an open-source project model | Teams seeking a straightforward LLM proxy for routing and provider failover with fast time-to-value | Teams seeking a commercial control plane for LLM calls with productized UI and governance features | | Key Strength | Protocol-aware gateway for agentic workloads (MCP/A2A), emphasis on governance and observability, open-source project under a foundation | Fast time-to-value for typical LLM gateway use cases; community adoption varies | Productized user interface and commercial features; broader gateway suite orientation | | Key Weakness | Limited third-party review footprint; enterprise pricing unclear; likely heavier platform engineering requirements than managed SaaS gateways | May require operational work to achieve billing-grade attribution and enterprise governance | Potential for vendor lock-in depending on deployment model; may focus primarily on LLM call governance | - Direct competitors and differentiators - LLM gateway specialists such as LiteLLM and Portkey are commonly discussed in community comparisons; Agentgateway emphasizes protocol-aware governance for agentic workloads beyond basic LLM routing. - API gateway and edge vendors (Kong, Cloudflare, Vercel) are extending into AI gateway functionality and may be preferred when organizations want to retain existing edge/network vendor tooling. - Pricing comparison - Agentgateway - Open-source distribution is available with no licensing fee. - Enterprise distribution pricing was not publicly listed and requires engagement with vendor sales. - Many competing SaaS-focused gateways publish entry pricing intended to reduce friction for evaluation and early adoption. - Market share and adoption trends (directional) - The AI gateway / agent gateway category remains fragmented, with community commentary indicating varying levels of production adoption across organizations. Independent industry research highlights enterprise concerns about API key management and governance gaps for agent fleets, which supports demand for control-plane–style solutions in general but does not validate specific product adoption.

01Competitive Landscape

Aspect	Agentgateway (Solo.io / Linux Foundation project)	LiteLLM	Portkey
Starting Price	Open source available; enterprise pricing not publicly listed	Open source + paid offerings (varies by vendor packaging)	Commercial SaaS (pricing varies by vendor)
Recommended For	Teams needing MCP/A2A and tool governance with a Kubernetes-native gateway option and an open-source project model	Teams seeking a straightforward LLM proxy for routing and provider failover with fast time-to-value	Teams seeking a commercial control plane for LLM calls with productized UI and governance features
Key Strength	Protocol-aware gateway for agentic workloads (MCP/A2A), emphasis on governance and observability, open-source project under a foundation	Fast time-to-value for typical LLM gateway use cases; community adoption varies	Productized user interface and commercial features; broader gateway suite orientation
Key Weakness	Limited third-party review footprint; enterprise pricing unclear; likely heavier platform engineering requirements than managed SaaS gateways	May require operational work to achieve billing-grade attribution and enterprise governance	Potential for vendor lock-in depending on deployment model; may focus primarily on LLM call governance

Direct competitors and differentiators
- LLM gateway specialists such as LiteLLM and Portkey are commonly discussed in community comparisons; Agentgateway emphasizes protocol-aware governance for agentic workloads beyond basic LLM routing.
- API gateway and edge vendors (Kong, Cloudflare, Vercel) are extending into AI gateway functionality and may be preferred when organizations want to retain existing edge/network vendor tooling.
Pricing comparison
- Agentgateway
  - Open-source distribution is available with no licensing fee.
  - Enterprise distribution pricing was not publicly listed and requires engagement with vendor sales.
- Many competing SaaS-focused gateways publish entry pricing intended to reduce friction for evaluation and early adoption.
Market share and adoption trends (directional)
- The AI gateway / agent gateway category remains fragmented, with community commentary indicating varying levels of production adoption across organizations. Independent industry research highlights enterprise concerns about API key management and governance gaps for agent fleets, which supports demand for control-plane–style solutions in general but does not validate specific product adoption.

Aspect

Agentgateway (Solo.io / Linux Foundation project)

LiteLLM

Portkey

Starting Price

Open source available; enterprise pricing not publicly listed

Open source + paid offerings (varies by vendor packaging)

Commercial SaaS (pricing varies by vendor)

Recommended For

Teams needing MCP/A2A and tool governance with a Kubernetes-native gateway option and an open-source project model

Teams seeking a straightforward LLM proxy for routing and provider failover with fast time-to-value

Teams seeking a commercial control plane for LLM calls with productized UI and governance features

Key Strength

Protocol-aware gateway for agentic workloads (MCP/A2A), emphasis on governance and observability, open-source project under a foundation

Fast time-to-value for typical LLM gateway use cases; community adoption varies

Productized user interface and commercial features; broader gateway suite orientation

Key Weakness

Limited third-party review footprint; enterprise pricing unclear; likely heavier platform engineering requirements than managed SaaS gateways

May require operational work to achieve billing-grade attribution and enterprise governance

Potential for vendor lock-in depending on deployment model; may focus primarily on LLM call governance