Events double-counting. Customer dashboards that don't match the invoice. Charges support can't explain without a vendor ticket. You've evaluated the SaaS platforms — maybe more than one. The problem is still there. Because at scale, usage billing stops being a pricing page problem and becomes a data contract problem. ABAXUS deploys inside your Kubernetes cluster and fixes the architecture.
docker compose up -d
They all require your usage data to cross a network boundary to their API. At low volume, this works. At scale — across regions, with billions of events, with pricing models that change — that boundary becomes the bottleneck.
One engineer evaluated Stripe Billing, Metronome, and Orb sequentially. Still described the problem as unsolved. Because the gap isn't vendor selection — it's architecture. At scale, billing stops being a pricing page problem and becomes a data contract problem: who owns the definition of a billable event, who corrects it, and how do you change pricing without breaking closed invoices.
Deploys inside your Kubernetes cluster — co-located with your events. No network boundary to a third-party API. No throughput ceiling. No compliance exposure from usage data leaving your environment.
The failure modes differ. The root cause is identical: usage data crossing a network boundary to a third-party API that wasn't built for your scale or compliance posture.
B2B SaaS between $5M and $100M ARR, engineering team of 6 or more, running usage-based or hybrid pricing.
Ingestion, aggregation, and pricing — all deployed inside your cluster. No external API to push events to. No throughput ceiling. No compliance surface from data leaving your environment.
Receive, deduplicate, and durably store usage events. Mandatory idempotency keys. 202 Accepted, never 200 OK.
Multi-region event collection with centralised aggregation. Two query modes with explicit consistency: real-time for dashboards, exact scan for billing — never conflated.
Meter definitions are versioned — old events processed under old rules, new events under new rules. Pricing changes don't touch historical invoices. Models are data, not code.
From defining what to measure to charging a card — every step is an idempotent API call. Deploy once, wire your event sources, invoice your customers.
{
"customer_id": "cust_acme",
"metric_key": "api_calls",
"value": 1,
"timestamp": "2026-03-17T14:00:00Z",
"idempotency_key": "evt_acme_req_abc123" // mandatory
}Duplicate events, API calls, and calculations are all safe. Replay any request without side effects.
Every invoice line item traces back to raw events through stored computations and SHA-256 checksums.
Metrics, plans, calculations, events — all immutable historical record. Soft-delete only preserves audit integrity.
DECIMAL(20,10) in PostgreSQL, decimal library in code. Floating point in billing is a lawsuit waiting to happen.
Real-time queries always declare eventual. Billing computations always declare exact.
Structured JSON logs, Prometheus metrics, health endpoints. Required for on-premise where you have no direct access.
Meter definitions are versioned with time-bounded applicability. When pricing changes, old events compute under old rules. Historical invoices stay explainable.
Correcting upstream data retroactively uses formal adjustment entries — not silent overwrites. Closed invoices remain closed. The correction is auditable.
Every dependency was chosen to maximize deployability. If it doesn't help you run in an air-gapped environment, it's not in the binary.
ABAXUS is in active development. The first customers who deploy it and give feedback lock in a 75% lifetime discount on license and support — before GA pricing applies.
Limited to a small number of teams. Qualifying call required — we pick customers we can build with, not just for.
If engineering, finance, and support all answer differently — you have a data contract problem. Map your billing infrastructure failure points before they become customer escalations. A self-assessment for VPs of Engineering and CTOs operating usage-based pricing.
No spam. Unsubscribe anytime.
Your billing layer should be invisible infrastructure — not the reason support escalates, finance can't close, or invoices can't be explained. In 30 minutes we map your event sources, identify your data contract gaps, and show you exactly what fixing the architecture looks like. No sales pitch.
curl -sSL https://get.abaxus.io | sh