If you don't run your own LLM proxy, how do you even know what's going on?
amrrs · hn · 2026-10-19
An HN discussion paired with a blog post arguing that developers should self-host an LLM proxy gateway to observe real usage. Relying solely on vendor dashboards hides actual token spend, failed requests, and model behavior differences; a self-run proxy gives unified logging, routing, and cost accounting, with discussion around setups like LiteLLM.
More from coding & agent
- Claude Code Pushes Urgent Security Update Across All Installations — umeshonai · 2026-10-23
- Claude cut a 2.6-hour video export to 20 minutes — but only after being told to rebuild the server — byhewar · 2026-10-23
- 3 flight-booking rules my AI agent checks that I'd never do by hand — Efistoffeles · 2026-10-23
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23