VoidLLM vs LiteLLM - An Honest Comparison from the Builder's Perspective

If you're running LLMs in production, you've probably evaluated LiteLLM. It's the most popular gateway out there - 100+ providers, massive community, used by companies like Stripe and Netflix. I built VoidLLM with a different set of priorities. Here's an honest comparison - including where LiteLLM is ahead. Why I built something different We were running self-hosted models in Kubernetes, hitting vLLM directly. No proxy, network policies were the only access control. It worked until we needed to know which team was burning through GPU hours. LiteLLM was the obvious first choice, but the Python runtime, startup time, and dependency tree felt heavy for what we needed. We also had a hard GDPR requirement - no prompt content could be stored anywhere. So we built VoidLLM in Go. What VoidLLM does differently Privacy by architecture. There's no "disable content logging" toggle - because there's no content logging code. The proxy reads the model field from the request body, streams bytes betwee