TL;DR: Togai is an active, independent usage-billing platform covering metering, pricing and billing as three modules, aimed at API companies, fintech and CPaaS. Two things distinguish it: a JavaScript rule engine for expressing custom billing logic, and dedicated solution engineers as part of the offering rather than an upsell. In a market where the venture-backed specialists were all acquired during 2026, remaining independent is itself worth noting. The starter tier is free with pay-as-you-go pricing on event volume and invoiced amounts; enterprise is quoted.
A note on this page: an earlier version was written in the first person as a hands-on review, with quoted feedback from reviewers. That testing did not happen and those quotes had no source. It has been rewritten as what it can honestly be — an assessment of where Togai sits and how to evaluate it — with no invented experience.
Where it sits
Togai covers the full path: metering, pricing and billing. That puts it in the same category as Lago and Flexprice rather than alongside metering-only tools like OpenMeter — it is a billing platform, not a counting layer.
Its stated focus is API companies, fintech and CPaaS providers, which is a narrower and more coherent target than "all SaaS". Those businesses share a shape: high event volumes, pricing that is genuinely complex rather than complex-sounding, and a commercial team that changes prices more often than the engineering team wants.
The two things that actually differentiate it
A JavaScript rule engine. Custom billing rules expressed as code, combining usage metrics and revenue data as inputs. This is unusual and it is a real answer to a real problem: every billing platform eventually meets a pricing model its configuration UI cannot express, and the normal outcome is a bespoke service in front of the biller. Being able to write the rule inside the platform is a meaningful alternative.
It is also a trade, and worth naming as one. Rules-as-code means your pricing logic is now software: it needs review, versioning, testing and someone who understands it when they leave. A configuration UI constrains you, and constraint is sometimes the feature. Ask how rules are versioned and whether a past invoice can be recomputed under the rule that was in force when the events happened — if the answer is that rules are edited in place, no past invoice can be reconstructed, and that is the failure mode that makes disputes unwinnable.
Implementation support as part of the product. Dedicated solution engineers to configure complex pricing. For a mid-sized team without a billing specialist this is genuine value, and it is the thing the larger enterprise vendors charge separately for. The flip side is the usual one: work out how much of your configuration only the vendor's engineer understands, and what happens at renewal.
Independence, which now counts for something
During 2026 Stripe acquired Metronome, Adyen acquired Orb for $335 million, Salesforce acquired m3ter and Kong acquired OpenMeter. Togai is still independent and not attached to a payment rail.
Be precise about what that buys you, because "independent" does three different jobs in most comparison writing. Togai has corporate independence — nobody owns it — which is the most fragile kind, and exactly what every acquired vendor had the day before its announcement. It does not have licence independence: it is commercial, not open source, so unlike Lago, Flexprice or OpenMeter there is no code you keep regardless. Processor neutrality it does have today.
That is not a criticism. It is the same position Amberflo occupies, and it is a perfectly reasonable one — it just should not be read as the same guarantee an AGPL or Apache licence gives you.
How to evaluate it
The questions that matter are the same ones that matter for any metering vendor, and the bad answers are more informative than the good ones:
- What is the dedupe window, in seconds? Clients retry; a metering API that double-counts on retry fails silently onto an invoice. "It's idempotent" is not an answer.
- Is the idempotency key scoped per account? Globally-scoped keys mean the first customer to use
1takes it from everyone else. - What happens to an event timestamped inside a closed period? Fold it in, reject it, or attribute it to now — all defensible. Silence is not.
- Are prices and rules versioned? Especially relevant here, given the rule engine. If either is edited in place, past invoices cannot be reconstructed.
- Can you export raw events continuously, in a documented format? Events, not invoices. If leaving means re-instrumenting your product, the switching cost is a quarter of engineering.
Where UsageBox fits, stated accurately
It is not a Togai competitor, and an earlier version of this page claimed otherwise on the basis of features that do not exist — "built-in policy controls", portals, and "less guesswork around entitlements and receipts". To be clear about what is actually here:
UsageBox is a metering layer. Idempotent ingest with a documented dedupe window, per-account key scoping, a stated late-event policy, monthly rollups, exportable raw events, and an open-source storage engine (usagedb, in Rust). It has no rating engine, no invoicing, no credits, no entitlements engine and no customer portal. Togai does the things UsageBox does not.
The only overlap is the narrow case where you already have a biller you intend to keep and want the counting to happen in a layer you can point anywhere.