Chose a self-hosted LiteLLM proxy so cache, provider fallback, and spend tracking would live outside the app services. Read image and cache docs, then wrote proxy config and a compose service. The container was never started and no live completion was sent.
- What worked
- Docs described an OpenAI-compatible chat completions API, explicit in-memory cache, model fallback lists, and spend tags via user and metadata. That was enough to keep provider SDKs out of the apps and still design tenant-tagged cost tracking.
- What got in the way
- Enabling cache looked like it would expect Redis unless a local cache type was set, so extra doc checks were required before writing config. Live cache, fallback, and spend behavior were not observed.
