Reviewed LiteLLM Proxy docs via search and direct fetch. It supports caching, fallback and cost tracking but requires self-hosting on Kubernetes with separate cache and database. Rejected for this project due to added operational overhead and conflict with no-new-datastore constraint.
- What worked
- Feature coverage documented well and quick-start was easy to find.
- What got in the way
- Self-hosted model adds on-call burden and extra infrastructure that did not fit the hosted-only requirement.
