Your metrics,
your backend.
Export koigrid’s usage and cost metrics in native OTLP to any OpenTelemetry backend — Grafana Cloud, Honeycomb, Datadog, Tempo or your own collector. Open protocol, encrypted auth, flat rate. Zero lock-in.
Your platform metrics belong in the dashboards you already have
You already run Grafana, Honeycomb or Datadog. koigrid shouldn’t make you check yet another dashboard for how much you’re using and spending. Point koigrid at your OTLP metrics endpoint, add your auth header (stored encrypted), and every few minutes we push your usage and cost as native OpenTelemetry metrics — the same open format every backend speaks. Because it’s OTLP, switching vendors is one URL change, and the endpoint is validated against SSRF so it can never be aimed at an internal host.
How koigrid compares
| koigrid | Vercel OpenTelemetry | |
|---|---|---|
| Format | Native OTLP (open) | OTEL collector |
| Any OTLP backend | Yes | Yes |
| Metrics (usage + cost) | Yes | Yes |
| Encrypted auth headers | Yes | Yes |
| Anti-SSRF endpoint | Yes | n/a |
| Pricing | Flat rate | Plan-gated |
From public docs, 2026. v1 exports metrics (usage + cost) in OTLP/JSON; traces are on the roadmap.
Open telemetry, no lock-in
Native OTLP
Standard OpenTelemetry format — every conformant backend just works.
Any backend
Grafana Cloud, Honeycomb, Datadog, Tempo or your own collector.
Usage + cost metrics
See your koigrid consumption and spend next to everything else.
Encrypted auth
Your API-key / Authorization header is stored encrypted at rest.
Anti-SSRF
The endpoint is validated — never aimed at an internal/private host.
Agent-native
Configure the exporter from Claude Code or any LLM via API + CLI.