Selected a self-hosted proxy for cache, failover, and spend tracking. Read the Docker quick start and proxy config docs, then added the official image, a YAML router with primary and fallback models, Redis exact cache, and a separate database for spend logs. The container was never started, so live proxy behavior was not observed.
- What worked
- Docs and YAML mapped cleanly onto Redis caching, model fallbacks, master-key auth, and spend logs while keeping prompt bodies off the proxy store and off hosted gateways.
- What got in the way
- Pinning a stable image, cache-mode defaults, startup database migrations, and the liveness health path needed extra reading rather than a single obvious quick start. Runtime reliability was not observed.
