Skip to main content
Unomiq computes cost and usage at fine-grained resolution by correlating cloud billing data and pricing metadata with OpenTelemetry traces. It derives per-request cost across distributed services, enabling precise visibility into the cost of individual operations—whether database workloads, pipeline executions, API requests, or LLM invocations. This provides deterministic cost attribution at the unit level, allowing teams to evaluate contribution margins per customer, feature, or workload. As a result, engineering and finance can make faster, data-driven decisions around scaling, pricing strategy, and resource allocation.

​
How it works

  1. Send traces — Instrument your application with OpenTelemetry and send traces to the Unomiq Gateway API.
  2. Attach a unit — Tag traces with a unomiq_unit attribute (e.g., customer ID, tenant ID) to group costs by the entities that matter to your business.
  3. Connect billing data — Export your cloud billing data (e.g., GCP detailed billing to BigQuery) so Unomiq can match costs to traces.
  4. Query costs — Use the Unomiq Engine API or Dashboard to analyze per-request costs, filter by unit, and understand where your money goes.

​
Get started

Getting Started

Start sending & monitoring traces

​
Guides

Sending traces

Send OpenTelemetry traces to the Unomiq Gateway using a Collector Sidecar or directly from your application.

Attaching a unit to traces

Link traces to logical entities like customer IDs or tenant IDs with the unomiq_unit attribute.

GCP detailed billing export

Enable detailed usage cost export to BigQuery for resource-level cost analysis.

How cost computation works

Learn how Unomiq matches billing data with traces to compute per-request costs.

​
API reference

Gateway API

OAuth and trace ingestion endpoints.

Engine API

Query traces, spans, and cost metrics.

Management API

Manage organizations, applications, and API keys.