Ruba product infrastructure

Know the margin behind every customer

Put service cost beside revenue, then read profit and lifetime value from one event stream.

Revenue minus attributed event cost gives you customer profit. Accumulate that profit over time and you have lifetime value based on what the customer actually costs to serve.

Live ledger engine

Instrument the event you already send

The event keeps its customer and usage context. A _cost annotation adds the expense of serving it without creating a second record.

Event identityname + customer

Usage contextexisting metadata

Service expense_cost amount + currency

Resultcost attributed to customer

Architecture overview

Choose what belongs in cost

Any expense that can be tied to a customer event can enter the same calculation.

01
Model and AI calls
Record the provider cost behind tokens, images, audio, or any routed inference request.
02
Infrastructure usage
Attribute compute, storage, bandwidth, or database work to the customer that caused it.
03
External services
Include email, SMS, voice, search, and other vendor calls made for a customer.
04
Internal operations
Allocate the expense of an internal service, queue, or processing stage.

Cost enters with the event

Add a _cost object containing an amount and currency to an event you already send through the Ruba API. That one annotation marks the expense of serving the event.

Ruba aggregates the annotation beside the revenue and usage data it already holds. There is no separate cost database, export job, or reconciliation pipeline to keep aligned.

The resulting figures are available in the dashboard and through the Metrics API, so the same source can drive an internal report or a customer-level profitability view.

Capability matrix

Three answers from one stream

Choose any reporting window and inspect the economics at customer level.

Attributed cost

Expense side

The sum of every cost-bearing event associated with the customer.

Customer profit

Revenue less expense

Recognized revenue less the cost attributed to the same customer.

Lifetime value

Cumulative profit

Cumulative customer profit from the beginning of the relationship.

Cost-bearing events

Add amount and currency without changing event ingestion.

Event traceability

Inspect the exact calls that contributed to service cost.

Metrics API

Query cost, profit, and value for your own reporting.

Dashboard analysis

Review customer economics without maintaining a second model.

One record of revenue and expense

Cost Insights extends the events used for usage billing instead of introducing a parallel analytics product. Usage, revenue, and cost stay comparable because Ruba derives them from the same customer activity.

Build with Ruba

Add cost to your next event

Attach _cost to an ingestion request and let the existing stream do the accounting.