How it works
ABAXUS turns product usage into paid invoices. Run the open core in your own infrastructure or use ABAXUS Cloud, where we host it. Every call is idempotent. Every number is exact.
Metrics, price plans, customers, subscriptions. Done once, versioned forever.
Jump to setupSingle events, batches of 500, backfills. Retries can't double-bill.
Jump to ingestionExact usage, calculated lines, issued invoice, charged payment, all audited.
Jump to invoicingIf you can draw your billing system on a whiteboard, you can defend it in an audit. This is the whole thing.
Modular by design
ABAXUS is built from small, separable modules: ingestion, metering, pricing, invoicing, payments. The two components that carry infrastructure weight, storage and messaging, are defined as interfaces with adapters behind them. Metering, pricing and invoicing logic never touches a concrete database or broker.
Start with the defaults: one Go service and PostgreSQL. Swap an adapter when your scale or your platform standards call for it, without rewriting your pricing or invoice logic.
Self-hosted Core: you define how ABAXUS is composed in your own VPC, which adapters, which topology, which dependencies, and you own that definition. ABAXUS Cloud: we define and operate the composition for you.
01 · SETUP
POST /v1/metricsWhat you measure: API calls, storage bytes, seats. Aggregate by sum, count, max or unique count.POST /v1/price-plansPer-unit, tiered, volume, package or flat fee. Reusing a plan ID creates a new version.POST /v1/customersOptionally attach a payment method. Provider credentials are set once in Settings.POST /v1/subscriptionsBinds a customer to a pinned plan version. Entitlements apply immediately, no sync job.# 1. what to measure curl -X POST /v1/metrics -d '{ "key": "api_calls", "aggregation": "sum" }' # 2. how to price it curl -X POST /v1/price-plans -d '{ "id": "plan_growth", "currency": "USD", "charges": [ { "metric": "api_calls", "model": "tiered", "tiers": [ { "up_to": 10000, "unit": "0.001" }, { "up_to": null, "unit": "0.0005" } ] } ] }' # 3. who pays curl -X POST /v1/customers -d '{ "id": "cust_acme" }' # 4. bind them curl -X POST /v1/subscriptions -d '{ "customer_id": "cust_acme", "plan_id": "plan_growth", "start_date": "2026-01-01" }' → { "id": "sub_a1b2c3", "status": "active" }
booleanSSO, priority supportlimitseats, monthly API callscustomrate limits, allowlistsGET /v1/entitlements/check returns granted and exceeded, so "not on plan" and "over limit" are never confused.02 · INGESTION
POST /v1/events202One event, queued asynchronously. Never blocks your request path.POST /v1/events/batch207Up to 500 events, each with its own status. One bad event doesn't block the rest.POST /v1/events/backfillmigrationsHistorical data straight to the events table. Affected aggregates are invalidated automatically.curl -X POST /v1/events -d '{
"idempotency_key": "req_7f3a-0001",
"customer_id": "cust_acme",
"subscription_id": "sub_a1b2c3",
"metric": "api_calls",
"value": "1",
"properties": { "region": "eu-1" }
}'
→ 202 Accepted
# network blip, client retries the same key
curl -X POST /v1/events -d '{ "idempotency_key": "req_7f3a-0001", … }'
→ 202 Accepted · duplicate skipped, counted once03 · INVOICING
GET /v1/usage/summary · POST /v1/usage/computeSummary for dashboards, compute for the exact invoice figure.POST /v1/pricing/calculateLine items per tier and metric, stored as a calculation the invoice references.POST /v1/invoicesPeriod runs from the last invoice to your cutoff date. $0 invoices are rejected.POST /v1/invoices/:id/chargeStripe PaymentIntent on the saved method. The intent ID lands in the audit trail.A · usage → "85000" api_calls
B · calculate → total "127.50" USD
C · invoice → inv_abc · issued
D · charge → paid · pi_xxx
Fewer moving parts means fewer pages at 3 a.m. and a shorter security review.
ABAXUS Cloud runs this same pipeline for you, hosted and operated by ABAXUS, and adds spike control at ingestion and an agent that resolves metering disputes at invoicing.
Compare Core and CloudA free 30-minute architecture review with the engineer who built the pipeline.