duo-infra-cost-efficiency

Make infrastructure spend visible, attributable and cuttable without slowing the company down — hourly per-dimension cost tagging, pushing the number into channels engineers already read, defining a win as waste removed rather than spend removed, pricing tech debt in dollars, auditing internal fan-out and cache TTLs, relaxing freshness so caching becomes legal, and deterministic entity-level sampling. Use when someone says our cloud bill is out of control, we cannot tell which team or feature is spending, costs jumped last month and nobody knows why, our LLM spend grows faster than usage, how do we justify infrastructure work to leadership, our analytics queries are slow and expensive, or should we just buy more capacity. For the architectural fix itself, route to duo-backend-architecture.

Version

2.0.0

License

MIT