Aimeterly hit Hacker News today as a Show HN launch, pitching per-user cost dashboards that run directly on Claude Code's built-in OpenTelemetry instrumentation. The pitch is aimed at engineering teams who want to know exactly which developers are driving up LLM spend — without bolting on custom logging or scraping CLI output after the fact. The architectural choice matters here. Because Anthropic ships native OTel support in Claude Code, Aimeterly can consume standard telemetry spans and correlate them back to individual users, sidestepping the brittle screen-scraping that plagued earlier AI cost-tracking tools. That's a clean bet on OpenTelemetry as the stable substrate for agent observability — if the vendor keeps emitting those spans consistently. The timing is sensible too. As coding agents move from novelty to daily driver inside engineering orgs, finance teams are asking pointed questions about token burn per engineer. A tool that answers 'who spent what' straight from first-party telemetry has a much cleaner story than one reconstructing usage from logs after the damage is done. That said, the launch signal is minimal so far: the HN post sits at one point with zero comments as of this writing. The source material also doesn't reveal pricing tiers, deployment requirements, which OTel exporters Aimeterly supports out of the box, or how it handles attribution when a single user runs multiple concurrent sessions — all open questions that will matter for anyone evaluating it.
Key Takeaways
- Aimeterly builds per-user cost dashboards directly on Claude Code's built-in OpenTelemetry support, avoiding screen-scraping and log reconstruction.
- The integration path is notable: native OTel spans give third-party tools a stable foundation instead of brittle vendor-specific interfaces.
- Launch traction is thin — 1 point and 0 comments on the Show HN post at time of writing.
- Missing from the announcement: pricing, supported exporters, deployment details, and multi-session attribution edge cases.
The Bottom Line
Per-user cost visibility is becoming table stakes for teams running coding agents in production, and Aimeterly's bet on native OTel telemetry is the right instinct. But with almost no launch signal or product detail public yet, it still has to prove the execution — dashboards are easy, accurate attribution at scale is not.