VernLLM (@VernLLM) header
VernLLM (@VernLLM) profile picture

The LLM call framework | Resilience, observability and control for every call Managed by @BuddoYap

Joined October 2026
Photo by VernLLM (@VernLLM)Photo by VernLLM (@VernLLM)Photo by VernLLM (@VernLLM)Photo by VernLLM (@VernLLM)Photo by VernLLM (@VernLLM)Photo by VernLLM (@VernLLM)Photo by VernLLM (@VernLLM)Photo by VernLLM (@VernLLM)Photo by VernLLM (@VernLLM)
Your LLM call fails behind a gateway and all you get back is a 502. Was it the AI provider? A 429? A 200 that said "N/A"? VernLLM runs in your app, so you see the real error, and keeps the call working: it retries, falls back in order and catches 200s that lie. npm i vern-llm
2
2
1
3
574
Purple, Red, Green, Pink, Yellow and Brown.
3
𝗔dapters, 𝘐ntegrations and E̲xtensions.
1
2
116
VernLLM retweeted
Building with AI? Before paying for a gateway, check out vern-llm. Genuinely advanced circuit breaking, rate limits, and multi-provider fallback, all in your own process. vernllm.dev
3
1
1
38
VernLLM retweeted
Your LLM call fails behind a gateway and all you get back is a 502. Was it the AI provider? A 429? A 200 that said "N/A"? VernLLM runs in your app, so you see the real error, and keeps the call working: it retries, falls back in order and catches 200s that lie. npm i vern-llm
2
2
1
3
574
Hit your AI provider's rate limit and your retries keep you stuck there? The retry budget in VernLLM fixes that. Use it today with "npm i vern-llm".
1
1
2
92
VernLLM reached 10k+ npm downloads. Advanced logging and routing middleware for LLMs is coming soon.
1
1
56
VernLLM retweeted
VernLLM is improving more on AEO now
1
2
139
VernLLM reached 10k+ downloads on npm!
1
1
1
3
197
VernLLM retweeted
Normal circuit breakers trip on any error. For LLMs that's wrong: bad JSON or a caller's 400 isn't an outage. VernLLM's breaker counts only real provider failures, catches empty 200s and stalled streams, and falls back across providers. Use it today with "npm i vern-llm".
4
4
5
96
Normal circuit breakers trip on any error. For LLMs that's wrong: bad JSON or a caller's 400 isn't an outage. VernLLM's breaker counts only real provider failures, catches empty 200s and stalled streams, and falls back across providers. Use it today with "npm i vern-llm".
4
4
5
96
VernLLM retweeted
RPM + TPM + concurrency with adaptive AIMD is rare, even for a resilient rate-limiter package.
Rate-limiting LLM calls is a pain. Why not try "npm i vern-llm" and fix it?
2
1
2
60
VernLLM retweeted
Your LLM will go down. Your app doesn't have to. VernLLM retries the failing provider, falls back to the next, and after 3 failures opens the circuit so later calls skip it in 0ms. pnpm add vern-llm vernllm.dev How do you handle provider outages today?
9
2
1
11
156