Event ingestion
Send events via API or batch upload. Automatic deduplication on every event key.
Usage Metering
Meter usage without losing trust in the bill
Your product tracks API calls, storage, or transactions. Gruv ingests the events, deduplicates, aggregates per period, and turns them into invoice line items. Your subscriber drills down to every event.
Deduplicated ingestionUsage-to-invoice resolutionDispute-ready event trail
Usage · this cycleOct 15 · 18:44 UTC
API calls
842,130 / 1,000,000/mo
Data transferred
128.4 GB / 150
Seats
22 / 25
Event streamlive
00:12api.invoke+12,820
00:14data.egress+0.42 GB
00:17api.invoke+8,104
00:19seat.added+1
Overage forecast
+$18.40 this cycleHow it works
Where usage-based billing breaks
Duplicate events inflate the bill
A network retry sends the same API-call event twice. Your metering pipeline counts it twice. The subscriber disputes the invoice.
Subscribers cannot verify the charge
The invoice says "12,847 API calls at $0.002." The subscriber asks "show me the calls." Your support team cannot drill down.
Pricing model and metering disagree
Your plan charges per tier. Your metering counts total volume. The invoice shows a number that matches neither. Finance escalates.
Disputes take days to investigate
A subscriber disputes $340 in usage charges. Tracing from raw events to aggregation to invoice takes three engineers and two days.
Metering around event quality and rating
Send raw events to Gruv. Get deduplicated, aggregated, rated, and invoiced usage back. Every step auditable, every line item defensible.
Deduplicated event ingestion
Every event carries a unique key. Gruv deduplicates automatically. Retries are safe. Your usage totals are accurate.
Track what your product cares about
API calls, seats, storage GB, transactions, or compute hours. Define your billable metric once. Gruv aggregates it every cycle.
Tiered, volume, and stairstep rating
First 10,000 calls at $0.002. Next 50,000 at $0.001. Gruv resolves usage into your exact pricing model.
Capabilities
What metering teams need
Custom metrics
API calls, storage GB, seats, transactions. Define the unit your pricing model uses.
Pricing-rule resolution
Usage resolves into tiered, volume, or stairstep charges automatically each cycle.
Threshold alerts
Alert subscribers at 80% usage. Alert your team at 100%. Prevent bill-shock escalations.
Dispute-ready trail
Trace any invoice line back to raw events, aggregation, and pricing rules. Resolve disputes in minutes.
How it works
From raw event to billed usage
More in Subscriptions
Related capabilities on the same workflow
Recurring Billing
Gruv automates recurring billing with predictable invoice timing, saved payment methods, and real-time charge status for
Pricing Models
Gruv lets your pricing team launch flat, tiered, volume, and usage-based plans from the dashboard, no engineering deploy
Lifecycle Management
Gruv tracks every subscription from trial to cancellation with clear state transitions, pause controls, and a timestampe
Frequently Asked Questions
How do we send usage events to Gruv?+
Via typed API or batch upload. Every event carries a unique key for deduplication. SDKs available in TypeScript, Python, Go, and Ruby.
Can we combine usage charges with a flat subscription fee?+
Yes. A $99/month base plus metered API calls is the most common hybrid. The invoice shows both components as separate line items.
How do we handle a usage dispute?+
Trace from raw event to aggregation to rated invoice line. Your support team resolves in minutes from the dashboard, no engineering help needed.
What happens with late or corrected events?+
You set the policy: apply to the current cycle, roll into the next cycle, or issue an adjustment. Gruv handles the recalculation and invoice update.
What does Gruv AI do across these features?+
Gruv AI automates payout routing, compliance gates, exception triage, and the Ask Gruv AI workspace. Every feature shares the same AI layer, so rules, holds, and reconciliation stay consistent.
Can I start with one feature and add more later?+
Yes. Gruv is modular. Start with one workflow and expand to additional modules as your needs grow.
How do I connect Gruv to our existing systems?+
Connect through APIs and webhooks, or start with file imports and exports for a fast evaluation. Email ingestion works for lightweight backfills.
What determines coverage, methods, and timelines?+
Coverage, methods, and timelines vary by market and are subject to compliance and policy checks. Confirm your target corridors and payout methods during evaluation.
Is this tax or legal advice?+
No. Tax and compliance features vary by jurisdiction and customer configuration. This content is for informational purposes and is not tax or legal advice.
Start metering usage.
Your product tracks API calls, storage, or transactions. Gruv ingests the events, deduplicates, aggregates per period, and turns them into invoice line items. Your subscriber drills down to every event.
Many teams start with a narrow launch in weeks.