Platform

From raw event to recognized revenue.

Usage flows in one side as events and out the other as invoices your auditors sign — every transformation visible, every number provable.

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.

tiers · credits · ramps · floors

Programmable pricing

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

Audit-grade invoices

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

Real-time entitlements

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

Revenue recognition

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

Drop-in migration

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.

Live entitlements

Quota answers in single-digit milliseconds.

The same counters that price your invoices serve entitlement checks from 41 edge regions, so gating a request on remaining balance costs less than a DNS lookup. When usage crosses a threshold, webhooks fire before the customer notices — upgrade prompts at 80%, hard stops at 100%, all configured per plan, none of it deployed.

usage vs. entitlement threshold

webhook armed at 80%

The integration

The whole API fits in your head.

Meter events, define rulesets, read invoices. Everything else is configuration.

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 invoice

response

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

Revenue lost to double-counting, ever

SOC

SOC 2

Type II, audited annually

PCI

PCI DSS

Level 1 service provider

GDPR

EU data residency available

ISO

ISO 27001

Certified ISMS

Every unit, accounted for.

Stop reconciling. Start proving.

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.

Get an API key Talk to an engineer