GoModel open-source gateway featured

GoModel, an open-source AI gateway written in Go, surfaced in developer discussions on May 18 and May 19 as engineers compared tools that sit between applications and large-model providers. The project’s GitHub page describes it as a lightweight, OpenAI-compatible API layer for providers including OpenAI, Anthropic, Gemini, Groq, xAI, Azure OpenAI and Ollama. A Hacker News post tied to the project said it was built to track AI usage and cost per client or team, switch models without changing app code, and debug request flows. The attention around GoModel sits inside a broader market for AI gateways and control planes. Startups including R9S and Portkey are pitching similar infrastructure: one API in front of multiple models, centralized routing rules, spend tracking and request governance. Their public repositories and documentation show how quickly that layer is becoming a product category rather than a one-off internal tool. (github.com) ### Why did GoModel show up in the first place? GoModel’s Hacker News post identified a specific operator problem: too many provider APIs, too little visibility into usage, and too much friction in switching models. The post said the software sits between an app and providers such as OpenAI and Anthropic and was built by a Warsaw-based solo founder, Jakub, with contributors since December. The same post listed cost tracking, model switching and request debugging as the initial use cases. (github.com) GitHub showed 883 stars, 60 forks and a latest commit dated “yesterday” when the repository was crawled on May 19. The repository description says GoModel offers observability, guardrails, streaming, costs and usage tracking through a unified API. ### What does GoModel actually put in front of model APIs? The repository says GoModel presents an OpenAI-compatible interface while routing requests to multiple upstream providers. (news.ycombinator.com) The listed providers include OpenAI, Anthropic, Gemini, DeepSeek, xAI, Groq, OpenRouter, Z.ai, Azure OpenAI, Oracle and Ollama. That design makes the gateway a control point. A team can keep one application-side API shape while changing providers, adding policies or collecting logs in one place. (github.com) The Hacker News description specifically framed the software as a way to switch models without rewriting application code. ### Where do R9S and Portkey fit into the same conversation? R9S’s public repository for open-next-router describes the software as a lightweight, DSL-driven LLM gateway for routing, patching provider quirks and normalizing APIs across channels. (github.com) A separate usage and cost-calculation document says the system extracts token metrics, multiplies them by per-token prices and records the results in access logs for observability and spend tracking. (news.ycombinator.com) Portkey’s documentation describes its gateway as the base layer for guardrails that can inspect requests and responses in real time. Its “Request Parameters Check” documentation says users can allow or block tool types, function names, top-level request keys and specific parameter values before a request reaches a model. ### What kind of controls are these companies exposing? (github.com) Portkey’s current docs say guardrails can deny a request, log the result, create an evaluation dataset, fall back to another model or prompt, or retry the request. Separate Portkey pages describe model rules for team-specific model policies and cost control, plus integration-level controls to enable or disable models and configure pricing. (docs.portkey.ai) Portkey also documents enterprise access controls around organizations, API keys and provider permissions. Its model catalog pages say organizations can store provider credentials once, share them across workspaces and decide which models each workspace can use. ### Where can readers watch this category develop next? GitHub and product docs are the clearest next checkpoints. (docs.portkey.ai) GoModel’s repository showed fresh dashboard-related commits on May 18, while R9S’s open-next-router repository showed an update three hours before it was crawled on May 19. Portkey’s docs were updated in May 2026 across gateway, model catalog and guardrails pages, giving readers a live record of which controls vendors are adding to this layer. (docs.portkey.ai) (github.com)