Skip to content
Kaeso logo

Kaeso

Routes application calls to AI model providers through one self-hosted Rust gateway that holds provider keys, enforces rate and budget limits, and logs usage.

Actively maintained

Kaeso: data, price, alternatives
At a glancechecked Oct 24, 2026

1.2k installs/mo

Emerging

For
Organizations running several AI apps that want a self-hosted gateway for provider keys and single sign-on.
Activity
Actively maintainedrelease 9 days ago · site updated 10 days ago
How it runs
Self-hostedAPI
Used for
  • route every app's model calls through one API
  • track requests, tokens and cost per project
  • review requests and errors in the request logs
Worth knowingcomputed from what we read · each with its source
  • Publishes llms.txt, a file written for AI assistantskaeso.app ↗
  • Launched on Product Hunt on Oct 24, 2026Product Hunt ↗
Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare Kaeso with

Pick up to two.

All 10 alternatives to Kaeso →

All Developer tools tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Kaeso for?

Sign in to leave a note
Questions this page answers
  • What is Kaeso?

    Routes application calls to AI model providers through one self-hosted Rust gateway that holds provider keys, enforces rate and budget limits, and logs usage. It is listed in the Atlas under Developer tools.

  • Who is Kaeso for?

    Organizations running several AI apps that want a self-hosted gateway for provider keys and single sign-on.

  • Do people use Kaeso?

    Emerging: 1.2k installs/mo (npm).

  • Is Kaeso still maintained?

    Actively maintained: release 9 days ago · site updated 10 days ago.

  • What are alternatives to Kaeso?

    In Developer tools, by use: Kong Inc., Experiential Labs, Busbar, VoidLLM, OwlVigil.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk