← The platformMetering

Meter every event.

Tokens, API calls, compute seconds, seats — one ingestion pipe, aggregated in real time. Every unit your product emits becomes a billable line — and a real-time entitlement check — the moment it happens.

Token countingEvent ingestionReal-time aggregationCredit burn-down
Usage eventsStreaming live
TimeEventQty
14:02:11gpt4o.completion_tokens48,120
14:02:09embeddings.api_call1,204
14:01:58vector.storage_gb_hour312
14:01:44agent.run_seconds9,860
402,188 / hr0 dropped
Why it matters

Correctness at scale, not just at demo speed.

01Idempotent by design

A retried delivery is a no-op, not a double charge. Every event carries an idempotency key checked against an append-only ledger.

02Late events land correctly

Events arriving up to 72 hours late are folded into the right billing period automatically — no manual correction, no re-invoicing.

03Same pipe at any volume

Ten events a second or ten thousand — the same ledger discipline holds, because aggregation never assumed order or single delivery.

How it works

Three steps. No engineering ticket.

1Send the event

One API call or SDK line per usage moment — tokens, API calls, compute seconds, seats. No schema to pre-register.

2Ledger aggregates it

The append-only ledger deduplicates retries by idempotency key and aggregates in real time, per customer.

3Billing updates instantly

The new total feeds pricing, entitlements and the dashboard the same second — no batch job, no delay.

72 hrslate-event window, folded in automatically
0dropped events under retry or duplicate delivery
400M+events metered monthly across Kribana customers

Send your first event today.