LLM engineers are trading blind.

Which provider is degraded right now? What does this model actually cost when you factor in overhead, not just token price? If traffic shifts between providers, what happens to cost and latency? Is your stack dangerously concentrated on one provider?

These are operational questions every production LLM system has. Nobody's built the tooling for them until now, so most teams either fly blind or patch together status pages, spreadsheets, and gut feel.

We built the LLM Ops Toolkit to fix that:

1. Provider uptime monitor across 18+ LLM providers, live status in one view 2. Cost calculator that includes overhead, not just raw token pricing 3. Routing simulator to model cost and latency impact before you shift traffic 4. Model diversity audit to surface concentration risk before it becomes an incident

Free, open-source, no signup. Dashboard is at tools.lamatic.ai

The routing simulator is the most experimental piece and has the roughest edges. Genuinely curious how others think about provider concentration risk.

We've been treating it as dependency risk in software but that framing may not hold at scale.

Also live on Product Hunt today: producthunt.com/products/lamatic-ai