Usage metering and rating platform acquired by Zuora to power its consumption billing.
Togai is a metering and rating layer that sits between a product's usage events and the invoice. It ingests raw events, aggregates them into billable quantities, and applies pricing logic — tiers, volume rates, credits — so downstream billing gets clean, rated amounts instead of raw telemetry. It was built for SaaS and API businesses moving to usage-based pricing, and after its acquisition by Zuora it now serves as consumption infrastructure inside a subscription-era billing suite.
Which of the capability map's modules Togai covers — each links to the module's own page, with every tool that supports it.
| Module | Phase | Depth | Note |
|---|---|---|---|
| Fulfill & Bill | |||
| Usage Event Ingestion (API) | Consume & Meter | Core | |
| Aggregation & Rollups | Consume & Meter | Core | |
| Rating Engine | Rate & Bill | Core | Applies tiered, volume, and credit-based pricing to metered quantities before invoicing. |
Scored against UsagePricing's Usage-based billing & metering rubric v1.0 (0 weak · 1 adequate · 2 strong), assessed July 2026. Requirements we couldn't verify from public material stay unscored — never guessed. Read the method.
| Requirement | Score | Why |
|---|---|---|
| Real-time balances & drawdown Can a customer (and your product) see an accurate credit or spend balance mid-period? | 1 · Adequate | Credits and entitlement balances supported. |
| Correction & re-rating When a meter was wrong, can you fix history without hand-editing invoices? | 1 · Adequate | Correction workflows over ingested events. |
| Commits, credits & custom rate cards Can it express how enterprise AI deals are actually signed? | 1 · Adequate | Commit and ramp constructs for negotiated deals. |
| Billable-metric flexibility Can finance define a new meter without re-instrumenting the product? | 2 · Strong | Flexible metric definition over raw events was the founding pitch. |
| Invoice & proration correctness Do mid-cycle changes, consolidation, and multi-currency come out right? | 1 · Adequate | Usage-first invoicing; enterprise formats lean on the Zuora side post-acquisition. |
| Rev-rec & ERP handoff Can the numbers survive an audit once they leave the billing system? | 1 · Adequate | Now feeding Zuora's suite after the acquisition. |
| Ingestion scale & integrity Does the meter stay correct at production event volumes? | 2 · Strong | Event-scale ingestion designed for consumption businesses. |
| Price-change velocity How fast can you ship a pricing change safely? | 1 · Adequate | Pricing iteration without re-instrumentation, short of full simulation. |
Togai's distinction is where it ended up rather than standing alone: it gave Zuora a purpose-built consumption engine instead of usage bolted onto subscription objects. For teams already on Zuora, that means metering and rating designed for event-level data without swapping out the billing system of record.
Platform fee. Now sold within Zuora's portfolio following the acquisition.
1 of the companies the Blueprint tracks — from public job posts, engineering blogs, and filings. Every claim links to its evidence on the company page.
Togai was acquired by Zuora, and its metering and rating capabilities are being folded into Zuora's consumption billing stack. Evaluate it as part of a Zuora decision rather than as an independent metering vendor.
Togai handles the usage side — event ingestion, aggregation, and rating — while Zuora Billing handles invoicing, collections, and revenue workflows. Together they let a subscription-first Zuora deployment price genuinely consumption-shaped products.
By overlap on the capability map — computed, not curated.