Back to News
Advertisement
SSilenN about 4 hours ago 11 commentsRead Article on github.com

DE version is available. Content is displayed in original English for accuracy.

Hi HN, we built an open source model gateway. It's a single place to manage our own self hosted, frontier, and open source models in one place.

It’s is rust native, built for concurrency, and implements all the config quirks across models and providers (streaming formats, tool calls, model parameters, rate limits, and different error behavior).

The gateway adds under 1 ms for BYOK requests and under 2 ms when Experiential supplies the provider key. It has every major inference provider, and 1000+ models refreshed daily via a codex agent that opens a PR.

Compared to other similar projects we’re open source, take no markup, allow you to mix local models with a marketplace, and use your traffic to (opt in) train you a model. Simple routing doesn’t warrant a 10% token markup.

The way we do this is given standardized OTel traces, we mine representative real tasks, use text world models to simulate rollouts for various models, apply an LLM judge, and fit a nearest neighbor classifier on top of an embedding of a prompt to decide the optimal model for each request. Usually this can map out a better pareto curve on cost/quality than just calling single models but it’s not perfect.

Using these simulations we can also do things like suggesting cache hit optimizations, new model suggestions, and training models.

It’s open source, so you can deploy it on your own infrastructure, use our hosted version with 0 markup, or read how we design for maximum availability on our website.

Advertisement

⚡ Community Insights

Discussion Sentiment

100% Positive

Analyzed from 118 words in the discussion.

Trending Topics

#model#caching#performance#switch#task#actually#more#works#major#advantage

Discussion (11 Comments)Read Original on HackerNews

Areibman•about 3 hours ago
Could you say more about how caching works? One major advantage of sticking with a single model is saving money on cached input tokens. I'd imagine if you swap between a bunch of models, you may improve performance but cost would would balloon out of control
SilenN•about 3 hours ago
The trick is to rarely switch, or switch at task boundaries. Often the conclusion of routing is actually "this one model is actually at the pareto front for this task, just use it always".
purplecats•about 3 hours ago
and caching is related to performance too ofc
cheema33•about 1 hour ago
I have not tried it yet. Is it similar to LiteLLM? If so, what sets it apart?
kfallah15•42 minutes ago
Router and model optimization from traffic is the main differentiator
23david•about 2 hours ago
Super interesting and congrats on the release. Curious if you initially had this in Python and then rewrote in Rust?
SilenN•about 2 hours ago
Yep! If you look at the commit history that's exactly what happened.
ashermania•about 3 hours ago
Finally an open source tool doing this!