Zerker Launches Open-Source AI Gateway for Self-Hosted Agent Traffic
Key Takeaways
- ▸Open-source, self-hosted gateway for routing and monetizing AI agent traffic with no external key custody
- ▸Enforces OIDC authentication and payment authorization at request time; no keys ever held or transmitted by the gateway
- ▸Single binary deployment with no runtime dependencies; runs on-premises, in VPC, or air-gapped
Summary
Zerker has released an open-source AI gateway designed to route, authenticate, and monetize agent API calls while maintaining full control and key custody on the operator's infrastructure. The gateway sits in front of agent traffic (HTTP or MCP protocol), enforcing OIDC authentication and payment authorization at request time without ever holding cryptographic keys or sensitive credentials. Built as a single binary with no external runtime dependencies (no JVM, Python, or sidecars), the gateway runs entirely on user-owned hardware—on-premises, in a VPC, or air-gapped—with optional Postgres backend for persistence.
The platform uniquely combines three capabilities that Zerker argues no competitor fully offers: self-hosting, the ability to charge for API calls, and the structural guarantee that the operator never holds keys. The comparison matrix highlights gaps in existing solutions: ContextForge and Lunar offer self-hosting but cannot charge; Cloudflare charges but cannot be self-hosted; MCPay does both but delegates settlement to an external facilitator. The gateway enforces OIDC configuration at startup with no bypass mechanism, ensuring authentication is never skipped—even in development (which uses a throwaway mock issuer).
- Positions as uniquely combining self-hosting, payment capability, and key-custody separation—a gap in the current competitive landscape
- Includes settlement and verification logic as separate, operator-controlled components; operators can run the entire stack themselves
Editorial Opinion
Zerker's architecture reflects a meaningful shift in how infrastructure for AI agents should be built: prioritizing operator control and security by structural design rather than trust. The refusal to start without OIDC, the separation of verification from custody, and the no-bypass-flag principle embed safety into the binary itself—not as documented best practices or configurable safeguards. In a space where hosted gateways dominate (Cloudflare) and open offerings leak key management (MCPay), Zerker's bet that users will pay for the burden and uptime of self-hosting in exchange for zero key custody is both refreshing and realistic.
