Prompts never collected
Only usage metadata leaves your app - never prompts, completions, or user content.
OkOvia collects usage metadata from your apps, backends, and GPUs, attributes every consumption to a product operation, and combines cost with your revenue rules. You see cost by feature, model, customer, and provider; revenue and margin by feature, channel, and customer — and, with client-side evals, quality.
checkout · GPT-4o · 1,840 tokens · cost $0.0012 · revenue $0.004 · margin 70%
Revenue calculated from the rules your team configures.
<script async src="https://okovia.com/js/okovia.js" data-key="vik_pub_…"></script> okovia("track", "checkout", { model: "gpt-4o" });
Attributed cost, revenue, and gross margin by feature — with drill-down to each individual operation.
op_7K9x · checkout · GPT-4o · 1,840 tokens · $0.0012 → $0.004 · 70%
Demonstrative data — the layout mirrors the real dashboard.
Instrument once. OkOvia prices and attributes everything from there.
Install the tag, SDK, or connector. OkOvia receives usage metadata — never prompts or completions by default.
Tie each consumption to a feature, operation, customer, plan, channel, or environment.
OkOvia applies your price and revenue rules to show attributed cost and margin, continuously.
Costs come from instrumented usage and your price rules; revenue from the rules you configure. Anything not instrumented or configured is not included.
Honest status per surface — nothing is listed as ready before you can actually install it.
Only usage metadata leaves your app - never prompts, completions, or user content.
Sensitive fields are redacted before anything is sent, on the client and on the server.
Cloud GPU metering runs as a connector inside your infrastructure - keys never reach OkOvia.
APM tools watch latency and errors. Cloud dashboards show aggregate infra bills. OkOvia is the only one that ties usage to per-feature cost and margin.
| Capability | OkOvia | APM / error tools | Cloud billing | DIY logging |
|---|---|---|---|---|
| Per-feature AI cost | ✓ | — | — | ~ |
| Gross margin (revenue-aware) | ✓ | — | — | — |
| One-line instrumentation (drop-in tag + typed SDKs) | ✓ | ~ | — | — |
| Cloud GPU metering (RunPod/AWS/GCP/Azure) | ✓ | — | ~ | ~ |
| Local vs API inference | ✓ | — | — | — |
| On-device privacy redaction | ✓ | ~ | — | ~ |
| Real-time | ✓ | ✓ | — | ~ |
| Client-side quality evals (only the score leaves) | ✓ | — | — | ~ |
| Budget caps & automatic model fallback (policies) | ✓ | — | ~ | — |
✓ native · ~ partial/manual · — not supported
Usage metadata only: model, tokens, latency, status, feature. Prompts and completions are never collected by default, and sensitive fields are redacted before sending.
From the revenue rules your team configures per feature, plan, or operation. OkOvia never guesses it.
It's free while in beta.
Cloud GPU usage (RunPod, AWS, GCP, Azure) is metered today through a connector you host yourself.
Free while in beta. Install the SDK, send a test event, and watch cost and margin appear in minutes.