
Kaeso
A fast, open-source AI gateway built in Rust
About Kaeso
Most teams wiring LLMs into production end up in one of two places. Some use a hosted gateway like OpenRouter or Portkey, which means your traffic runs through someone else's infrastructure. Others build a homegrown proxy that slowly collects scattered API keys, cost spreadsheets and Slack alerts. Kaeso pitches a third option: "the open-source AI gateway you run yourself." It's a Rust gateway that sits in the request path, a console for keys, routing, limits and logs, and one API your apps call instead of talking to each provider directly. The site promises "nothing new for your apps to learn," which is the right goal for a gateway.
The sharpest contrast with the hosted options is identity. Kaeso lets you connect an OpenID Connect identity provider to each organization, verify your email domains, and require single sign-on or two-factor authentication. All of that is in the MIT-licensed code, and the site says there's "no enterprise edition to buy." Plenty of infrastructure tools put SSO behind a sales call, so this is a real point in Kaeso's favor. Compared with LiteLLM, the other well-known self-hosted proxy, Kaeso leans harder on the console. The demo shows requests and error rates, tokens split into input, cache read, cache write, output and reasoning, and cost broken down by project, model and member. There's also a Playground where you can send a prompt and then find it in the request logs.
The catch is maturity. The latest release is 0.4.2, which lets organization admins add their own providers and rotate keys in one step. Version 0.4.0 added the option to plug in ChatGPT accounts as OpenAI provider keys and Grok accounts as an experimental provider key, so projects can draw on those subscription plans instead of API accounts. That's a clever idea, but it also shows how fast the product is still changing. You'll be operating pre-1.0 software on your own infrastructure, and the public pages don't list which providers or routing rules are supported. If you want full control of your keys and logs and you have someone who can run it, Kaeso is worth a serious look.
Key features
Self-hosted Rust gateway
Kaeso puts a Rust gateway in the request path between your apps and your model providers, and you run it on your own infrastructure.
Single sign-on with no enterprise tier
You can connect an OpenID Connect identity provider, verify email domains, and require SSO or two-factor authentication, all in the MIT-licensed code.
Usage and cost console
The console tracks requests, errors, tokens by kind (input, cache read, cache write, output, reasoning) and cost, broken down by project, model and member.
Projects with per-project spend
Traffic is grouped into projects such as a checkout assistant or support triage bot, so you can see exactly which workload is driving your bill.
Provider and key management
As of 0.4.2, organization admins can add their own providers and rotate keys in one step from the console.
Subscription accounts as provider keys
Version 0.4.0 lets you add ChatGPT accounts as OpenAI provider keys and Grok accounts as an experimental provider key, so projects can use those plans instead of API accounts.
Best for
- platform teams that want LLM keys and logs on their own servers
- companies that need SSO on AI tooling without an enterprise contract
- engineering orgs running several LLM-powered projects with separate budgets
- teams that want per-member and per-model cost visibility
Skip if
- Skip this if you don't want to run and patch infrastructure yourself. A hosted gateway like OpenRouter is less work.
- Skip this if you need a stable 1.0 product with a long track record. Kaeso is on version 0.4.2.
- Skip this if you need a confirmed list of supported providers before you commit. The public pages don't spell it out.
Pros & cons
Pros
- SSO, email domain verification and enforced 2FA ship in the MIT-licensed code, with no enterprise edition to buy.
- The console's token breakdown separates cache reads, cache writes and reasoning tokens, which matters for actual cost tracking.
- Cost reporting by project, model and member makes it easy to find the workload eating your budget.
- The interactive demo with sample data lets you click through projects, the Playground and request logs before you install anything.
- One-step key rotation in 0.4.2 removes a tedious manual chore.
Cons
- It's pre-1.0 software. Three releases (0.4.0 to 0.4.2) landed in a few days, so expect frequent changes.
- You're responsible for hosting, uptime and upgrades, since there's no mention of a managed option.
- The public material is thin on specifics. Supported providers, routing rules and limit configuration mostly live in the docs or show up after you deploy.
- Using ChatGPT and Grok subscription accounts as provider keys is clever, but the Grok support is labeled experimental, and you'll want to check each provider's terms first.
Frequently asked questions
Is Kaeso free?
Yes. Kaeso is open source under the MIT license, and the site says there's no enterprise edition to buy, so SSO and 2FA enforcement are included.
How is Kaeso different from LiteLLM?
Both are self-hosted gateways, but Kaeso is built around a Rust gateway and puts more weight on its console, with SSO, per-project cost and token-kind breakdowns built in. LiteLLM has been around longer, so it's the safer pick if maturity matters most.
Should I pick Kaeso or a hosted gateway like OpenRouter?
Pick OpenRouter if you want zero infrastructure work. Pick Kaeso if you want your keys, logs and request data to stay on servers you control.
Which identity providers work with Kaeso's single sign-on?
Kaeso supports any OpenID Connect identity provider, connected per organization. You can also verify email domains and require SSO or two-factor authentication for everyone.
Can I use my ChatGPT subscription through Kaeso?
Since version 0.4.0, you can add ChatGPT accounts as OpenAI provider keys and Grok accounts as an experimental provider key. That lets your projects draw on those plans instead of separate API accounts.
How Kaeso compares
Kaeso vs LiteLLM
LiteLLM is the more established self-hosted proxy, while Kaeso is newer but includes SSO and a more polished cost console in its MIT-licensed code.
Kaeso vs OpenRouter
OpenRouter wins on convenience because there's nothing to host, but Kaeso is the better fit if your traffic and keys must stay on your own infrastructure.
Kaeso vs Portkey
Portkey is a strong choice for a hosted gateway with observability, while Kaeso makes more sense if you want similar visibility without sending requests through a third party.
Reviews
Sign in to leave a review.
No reviews yet, be the first.
More like KaesoAll code & developer tools
Google Antigravity SDKgoogle.comFree planGoogle’s AI Agent SDK for Autonomous DevelopmentCode & DeveloperAI Agents-33.0% search trend, 3 moNo reviews yet
Claudeclaude.aiFree planAnthropic's helpful, harmless, and honest AI assistant.FeaturedChatbot & AssistantsWriting & Content-4.9% search trend, 3 moNo reviews yet
ContextSnipergithub.comFree planSmart task-driven LLM context optimizerCode & DeveloperN/ANo reviews yet
DeepSeekdeepseek.comFree planStrong open reasoning models.FeaturedChatbot & AssistantsCode & Developer+16.8% search trend, 3 moNo reviews yet
Hugging Facehuggingface.coFree planThe home of open AI.Code & DeveloperResearchN/ANo reviews yet
Cursorcursor.comFree planThe AI-first code editor.FeaturedCode & Developer-39.7% search trend, 3 moNo reviews yet