In week one. Not year one.
01
Idle licences and shelfware surface on the utilisation view before the renewal invoice arrives.
02
Runaway consumption trips a budget alert in real time instead of a surprise at month-end.
03
Every OwnIQ call is metered per tenant, so AI spend is attributable from day one.
And the Zylo renewal stops being a line item — the replacement is an asset you own. Run your numbers →

What sets it apart
Per-tenant, per-app quotas with atomic Redis counters and TTL windows
Utilisation, budget, and anomaly views across every connected product
Cohort metering — every OwnIQ request emits a usage event for billing
Spot idle licences and runaway consumption before the invoice does
Key Capabilities
Quota Service
Atomic Redis counters with TTL buckets enforce per-app, per-tenant limits in real time.
Cost & Utilisation
Track spend and usage across every connected app, surfacing idle seats and shelfware.
Anomaly Alerts
Detect runaway consumption and budget breaches before the invoice arrives.
Cohort Metering
Every OwnIQ chat or embedding request emits a usage event on the bus — billing meters it per tenant.
Budgets
Per-entity budgets with thresholds, alerts, and trend views.
Who it’s for
See utilisation, budget burn, and anomalies across every app — kill the 50%+ of licences nobody uses.
Set per-app, per-tenant quotas and get alerted before consumption blows the budget.
Meter the AI runtime accurately — every OwnIQ call is a usage event, attributed per tenant.
Perpetual Licence
OwnUsage is available as a perpetual licence. You own the software forever. Deploy on your infrastructure. No annual renewals, no per-seat pricing, no vendor lock-in. Prefer OpEx? A managed subscription is available too — switch between the two anytime, nothing to re-buy.
Every screen here also works without the screen.
OwnUsage implements the Own360 headless spec: a standard /api/v1 surface with OpenAPI, cursor pagination, idempotent writes, and entity.changed events — drivable from its own CLI, any HTTP client, MCP tools generated straight from its OpenAPI, and the OwnAgents runtime.
$ ownusage entities # 6 entities
$ ownusage meter list --limit 20
$ ownusage meter create --data '{…}'
$ ownusage domain ingestThe generated OwnUsage CLI — every entity and domain op, OwnAuth-authenticated, idempotent by default.
Entities
Domain ops
8 verified agent tasks · 3 cross-app workflows
- OwnBooks → OwnUsage — OwnBooks invoice → OwnUsage metering event referencing it
- OwnUsage → OwnBooks — OwnUsage meter + usage event → OwnBooks payment referencing the meter (usage-based billing)
- OwnUsage → OwnBI — OwnUsage meter -> OwnBI dashboard titled with the meter name
Inside OwnUsage
The full story — why it exists, what it replaces, every capability in detail, and real product screens.