runelayvs
agentgatewayCompare · 15 Nov 2026
An agentgateway alternative for your own agents
Runelay, an open source MCP gateway, and agentgateway both put MCP servers behind one endpoint. agentgateway is a proxy written in Rust for MCP, A2A and LLM traffic, set up with a config file or on Kubernetes; Runelay is an app for one person's agents, with a catalog, skills and memory. This page lists what differs, with sources.
Runelay vs agentgateway at a glance
| Runelay | agentgateway | |
|---|---|---|
| Made for | One person’s own agents | Securing and observing agent traffic to tools, other agents and LLMs |
| Runs on | Your computer or server | Standalone binary or Docker with a YAML config, or Kubernetes with its Gateway API control plane |
| Open source | Yes, MIT | Yes, Apache 2.0, a Linux Foundation project |
| Price | Free | No price found on the pages read |
| How MCP servers connect | Remote MCP URL, local command or OpenAPI spec | MCP over stdio, SSE and Streamable HTTP, plus REST APIs exposed as MCP tools through OpenAPI |
| Auth and policies | Owner account on your instance | JWT, API keys, basic auth and MCP auth with OAuth providers such as Auth0 and Keycloak; RBAC with CEL policies |
| OAuth to services | One-click OAuth from the catalog, Google and GitHub through the Runelay broker | Not found on the pages read on 15 Nov 2026 |
| Skills for agents | ✓ | Not found on the pages read on 15 Nov 2026 |
| Memory across agents | ✓ | Not found on the pages read on 15 Nov 2026 |
| Imports your agent setup | ✓ | Not found on the pages read on 15 Nov 2026 |
agentgateway column from github.com/agentgateway/agentgateway, agentgateway.dev/docs and Standalone docs, read on 15 Nov 2026.
Runelay fits when
- You want an app with a catalog and one-click sign-in to your accounts, not a proxy to configure.
- Your agents should share accounts, skills and memory, not only tools.
- You want a desktop app on your computer or a single container on your server.
- You already have MCP servers in your agents and want to import them with
runelay migrate.
agentgateway fits when
- You want one proxy written in Rust for MCP, A2A and LLM traffic, with an OpenAI-compatible API across providers.
- Access must follow fine-grained policies: JWT, API keys, RBAC with CEL, rate limiting, CORS and TLS.
- You run Kubernetes and want to configure it through the Gateway API, with OpenTelemetry metrics, logs and tracing.
- You need guardrails and LLM spend controls, or routing to self-hosted models by GPU and KV cache use.
Questions
Is Runelay built on agentgateway?
No. Runelay is a separate MIT project written with Bun, Hono, SQLite and React. agentgateway is an Apache 2.0 project written in Rust and hosted by the Linux Foundation.
Do I need Kubernetes to run an MCP gateway?
Not with Runelay: the desktop app runs on your computer, and on a server it is one container. agentgateway also runs as a standalone binary or in Docker, and has a Kubernetes mode with the Gateway API.
Can I move from agentgateway to Runelay?
Runelay accepts any remote MCP URL, local command or OpenAPI spec, so you can add the servers you use one by one. runelay migrate imports what is configured in your agents, not an agentgateway config file.