Show HN: I stopped using an LLM gateway and put rate-limits/fallback in-process

The LLM call framework. Resilience, observability, and control for AIs. - LakBud/vernLLM
4 points by Buddo 46 days ago github.com 1 comments
Summary not yet generated for this article.

Original Text

Sup HN. I built VernLLM cuz every LLM gateaway I looked at, meant adding a network hop just to get rate limiting, multi provider fallback, circuit breaking and other features.

Needing to take a whole seperate service just to deploy, monitor and trust with my API keys is just annoying since my whole tech stack was just TypeScript and Node.

VernLLM does the same job within your LLM calls, but its in process instead. Its supports OpenAI-compatible APIs, Anthropic, Gemini and Bedrock providers.

I would also argue that the features VernLLM provides is more developed then any other gateaway out there when it comes to resilience and customization.

The tradeoff vs a gateaway is that it has no centralized policy across multiple apps or languages so if you want that then its better to use a gateaway instead.

Here is the docs for more info: https://vernllm.dev

Comments (1 of ) ⌛

Loading more comments... ⌛
Scroll down to load more comments
No comments available.
Type to search HN and engineering blog articles
Press Escape to close  |  ↑↓ to navigate  |  Enter to open