Ship a pricing change in an afternoon, not a quarter.
Orvarex is metering and billing infrastructure for API-first and AI companies. Send us raw usage events. We price them against models you can version, produce invoices finance can close on, and sync everything to Stripe and NetSuite.
Now onboarding design partners. Replies come from the founders, usually within a day.
of B2B recurring revenue is typically lost to billing leakage: unmetered usage, misapplied discounts, and invoices that never match the meter.
is what a single pricing model change usually costs an engineering team when billing logic is hand-rolled into the product.
finance teams at usage-based companies still reconcile metered revenue in spreadsheets before they can close the month.
Industry estimates drawn from published research on billing operations and monetization. Your numbers will vary. That is rather the point.
The billing layer you keep meaning to build
Your product already emits usage. Orvarex handles everything between that event stream and a correct number on an invoice.
Ingestion that survives production
SDKs for Node, Python, and Go, plus a plain HTTP API. Every event carries an idempotency key, so retries and replays never double-bill a customer. Sustained ingest of 100,000 events per second per account, with late events accepted until the invoice finalizes.
Pricing models with version control
Per-seat, per-unit, tiered, prepaid credits, and annual commitments with drawdown, composed in one console. Draft v5 of your pricing, replay last month's real usage against it, see the revenue delta per customer, then roll it out to new signups only, or to everyone.
Invoices finance can close on
Proration and mid-cycle plan changes are computed for you, down to the second. Invoices sync to Stripe for payment. Recognition schedules and journal entries land in NetSuite. Every line item traces back to the exact events behind it, which makes audit season boring.
Three steps, no rewrite
Most design partners send their first event within an hour and run their first shadow invoice the same week.
Send usage events
Instrument the places where usage already happens. One call per event, from any service.
orvarex.track({
customer: "cus_8h2k",
event: "api_call",
value: 1,
idempotency_key: "req_9f31"
})
Model pricing in the console
Define meters, tiers, credits, and commitments without touching product code. Back-test any draft against historical usage before it ever reaches a customer, and keep every prior version addressable for grandfathered contracts.
Invoices and rev-rec flow out
Draft invoices accrue in real time so customers see spend before the bill lands. On finalization, Stripe collects payment and NetSuite receives the recognition schedule. Finance closes from a ledger, not a spreadsheet export.
Flat platform pricing. Never a cut of your revenue.
We meter billing for a living, so yes, our own pricing is public and simple. No percentage of billed revenue at any tier.
Developer
- 250,000 events per month
- 2 active pricing models
- Stripe test-mode sync
- Full API and all three SDKs
- Community support
Growth
- 25M events per month included
- Unlimited pricing model versions
- Commitments, credits, and drawdown
- Proration and mid-cycle plan changes
- Stripe live sync + NetSuite rev-rec
- Shared Slack channel with our team
Enterprise
- Billions of events per month
- SSO, SAML, and audit log export
- Custom rev-rec rules and ERP work
- Migration support from in-house billing
- Uptime SLA and dedicated engineer
Questions CTOs actually ask
How do you make sure events are never dropped or double-counted?
Every event carries an idempotency key you control, typically your request ID. We deduplicate on that key over a 7-day window, so client retries, queue replays, and at-least-once delivery from your message bus all resolve to exactly one billable event. Ingestion is acknowledged only after the event is durably written.
You can also reconcile independently: the API exposes per-meter event counts and checksums for any window, so your data team can diff our numbers against your warehouse before an invoice ever finalizes.
Can we migrate off Stripe Billing gradually?
Yes, and gradually is the only way we recommend doing it. Orvarex runs in shadow mode first: we ingest your usage and generate parallel draft invoices while Stripe Billing keeps charging customers. Once the drafts match your production invoices, you cut over one customer cohort at a time. Stripe stays as your payment rail throughout, so cards, receipts, and dunning do not change from the customer's point of view.
What happens to events that arrive late?
Invoices stay in draft until their finalization date, and late events within the billing period are priced into the draft automatically. After finalization, late usage generates a documented adjustment on the next invoice or a credit note, your choice per contract. Nothing is silently absorbed or silently added.
Do you take a percentage of billed revenue?
No. You pay a flat platform fee based on event volume, listed above. We think a billing vendor taking a cut of your revenue creates the wrong incentives, and it makes your gross margin worse precisely when your product succeeds.
How do mid-cycle plan changes and proration work?
When a customer upgrades, downgrades, or amends a commitment mid-cycle, Orvarex splits the period at the moment of change and prices each side under the correct model version, prorated to the second. The invoice shows both segments as separate, labeled line items so nobody has to explain a mystery number to a customer or an auditor.
Your pricing should be a weapon, not a backlog item.
We are onboarding a small group of design partners ahead of general availability. If your team is hand-rolling billing today, or dreading the next pricing change, write to us. A founder will answer.