idempotent · edge ingest · replayable
Exactly-once metering
Idempotency keys are enforced at the edge, so retries, queue replays, and network weirdness never double-bill a customer. Every count is replayable from the raw event log.
Metering & billing infrastructure
Quanta counts the events your product emits — exactly once, at the edge, in 14ms — then turns them into priced line items and audit-grade invoices. Usage-based revenue without the spreadsheet archaeology.
events metered, last 30 days
threshold: entitlement cap
Metering revenue for platforms that cannot afford to count wrong
The integration
One SDK call meters the usage, prices it against your live ruleset, and lands it on the next invoice — exactly once, with the receipt to prove it.
meter.ts — three lines to a billable event
import { Quanta } from '@quanta/sdk'
const quanta = new Quanta(process.env.QUANTA_KEY)
await quanta.meter('tokens.generated', {
subject: 'org_4f2a', // who pays
quantity: 1_847, // what they used
idempotencyKey: req.id, // counted exactly once
})
// → priced by your live ruleset, lands on the next invoiceresponse
POST /v1/meter · 201 Created · 12ms
{
"event": "evt_01j9x4qb",
"subject": "org_4f2a",
"quantity": 1847,
"deduplicated": false,
"priced": { "rule": "tokens-tiered-v3", "amount_usd": "0.2956" }
}12.4B
Events metered every day
14ms
p99 ingest latency at the edge
99.999%
Metering availability, trailing 12 months
$0
Revenue lost to double-counting, ever
Platform
Six capabilities, one contract: every number traceable to the events that produced it.
idempotent · edge ingest · replayable
Idempotency keys are enforced at the edge, so retries, queue replays, and network weirdness never double-bill a customer. Every count is replayable from the raw event log.
tiers · credits · ramps · floors
Pricing is a versioned ruleset, not a spreadsheet: tiered, volume, credit-burndown, committed-use, and floor pricing compose in plain configuration with effective dates.
line items · proofs · exports
Every invoice line links back to the exact events that produced it. Finance gets a drill-down trail; your customers get an invoice they stop disputing.
limits · alerts · webhooks
Check a customer’s remaining quota in single-digit milliseconds, fire webhooks at thresholds, and cut over from trial to paid without a deploy.
ASC 606 · exports · close
Usage becomes recognizable revenue on a schedule your auditors already agree with. Month-end close exports to your ledger, not the other way around.
shadow mode · diff · cutover
Run Quanta in shadow against your current billing for a full cycle, diff every invoice to the cent, then cut over when the delta reads zero.
SOC 2
Type II, audited annually
PCI DSS
Level 1 service provider
GDPR
EU data residency available
ISO 27001
Certified ISMS
Pricing
A platform fee, a falling per-event rate, nothing else. No seats, no surcharges, no percentage of your revenue.
Sandbox
$0forever
Full platform against test data — build the integration before anyone signs anything.
Most teams
Growth
$499per month + usage
Production metering for products charging real customers for real usage.
Scale
Customannual agreement
For platforms metering billions of events with compliance teams in the loop.
Customers
Engineering, platform, and finance leaders on what provable counting changed.
“We shadow-ran Quanta for one billing cycle. It found $41k a month we were under-billing through retry double-writes cancelling real events. It paid for itself before we signed.”
Anneke Visser
VP Engineering, Vectorbase
“Pricing changes used to be a two-sprint project with a rollback plan. Now it is a ruleset version with an effective date. Product ships pricing like code.”
Tomás Iglesias
Head of Platform, Relaygrid
“Our auditors asked how we tie invoices to usage. We gave them read access to the event trail and the meeting ended forty minutes early.”
Grace Adeyemi
CFO, Plyline
Every unit, accounted for.
Shadow-run Quanta beside your current billing for one cycle — free, read-only, cent-level diff. If we do not find money or a bug, the coffee is on us.