Edgee

Edgee is an agent gateway for teams running coding agents or AI apps. It sets token budgets, reroutes to open weight models mid-task, trims and shortens payloads, and reports cost per developer, repo and PR, with BYOK and on-premise options.

Edgee is an agent gateway: it sits between coding agents or AI applications and LLM providers, then routes, compresses and meters every request. The stated goal is cost control, with the vendor claiming reductions of up to 70 percent through a combination of budget-driven routing and token compression. Rather than swapping models by hand, teams set a token budget per developer, per squad or for the whole organization, and Edgee moves traffic to cheaper open weight models as that budget fills. The switch can happen mid-task and, according to the homepage, without quality loss or an interrupted session. The routing layer doubles as a resilience layer. If a provider goes down or a plan cap is reached, requests continue on the next model allowed by the policy. Compression works in two stages: input-side trimming of tool result payloads and output-side brevity, described as semantically lossless for coding tasks. Observability attributes cost and usage to a person, a repository, a pull request or a model, so engineering leaders can inspect spend before the invoice arrives. Open weight models such as GLM, Kimi and MiniMax are served at what the site calls turbo speed for a flat monthly price, and a catalog covers frontier and open weight models across major providers with live pricing and context sizes. The product targets engineering teams running Claude Code, Codex, Copilot, Cursor, OpenCode and similar agents, plus teams shipping their own AI applications. Onboarding is a CLI install followed by launching the agent through the gateway, which the site puts at roughly five minutes with no application code changes. Keys can be Edgee's own or bring-your-own for billing control and custom models. An on-premise option runs the same gateway inside a private network via Docker Compose or Helm, connected or air-gapped, keeping prompts, completions and provider keys local. Edgee is best understood as infrastructure rather than an agent itself. Teams comparing it with per-provider dashboards or simple API proxies get policy-driven routing and compression in one place, but they also take on a gateway dependency in the request path that has to be evaluated against their own workloads.