opsmeter

Hi HN,

I’m building Opsmeter, a tool to understand and control AI costs in LLM applications.

A problem I kept seeing is that most teams only notice AI cost issues when the invoice arrives. Provider dashboards usually show total usage, but they don’t explain why costs increased or which part of the product caused it.

Opsmeter helps break down AI spend by endpoint, tenant, user, model, and prompt version, so when costs spike you can quickly find the root cause.

A few things we focused on:

No proxy required. Cross-provider cost attribution. Budget alerts and spend monitoring. Request-level visibility into where costs come from.

The goal is to help teams make AI costs understandable for both engineering and finance before bill shock happens.

I’d love feedback from people building with LLMs.

How are you tracking AI costs today? What’s the hardest part of understanding cost spikes? Would you want this as observability, governance, or both?

Website: https://opsmeter.io Docs: https://opsmeter.io/docs

Hi HN — I built Opsmeter, a lightweight LLM telemetry tool focused on cost attribution + budget control.

Provider dashboards mostly show totals. Opsmeter shows what caused the bill by breaking spend down by endpointTag, promptVersion, and optionally userId — plus latency and success/error rates.

It’s no-proxy: Opsmeter doesn’t sit in your request path. After each LLM call, you send a small telemetry payload to /v1/ingest/llm-request (provider, model, endpointTag, promptVersion, token counts, latency, status). Opsmeter normalizes cost via a provider/model pricing table and surfaces trends + regressions.

Links:

Home: https://opsmeter.io

Docs: https://opsmeter.io/docs

Pricing: https://opsmeter.io/pricing

If you try it and share anonymized screenshots/feedback, I’m happy to help you interpret the results — e.g.

which endpoints drive spend

which prompt versions increased tokens/cost (deploy regressions)

which users (optional) are the biggest cost drivers

suggested budget thresholds (80% warning / 100% exceeded) and alerting setup

Feedback welcome — especially on what you’d want next: staying telemetry-first, and potentially adding an optional gateway mode later.