YOM

For SaaS platforms

Analytics inside your product, metered per customer.

Give every customer their own analytics without building a pipeline. Tag events with a sub-tenant, embed scoped reports, and read usage per customer to bill for it.

Start free, no credit cardRead the docs

The embedded-analytics gap

of SaaS companies already ship in-product dashboards (vendor survey)[1]
78%
is how users rate those dashboards in the same survey[1]
3.6 / 5
a month for 10K MTUs is where a CDP like Segment starts (third-party)[2]
$120

How it works

One project, with each customer’s sub-tenant created on first event.

Set subTenant in the SDK or on server events. In open mode the sub-tenant appears the first time it sends data, so you don’t need a provisioning call or any per-customer setup.

One YOM org connects to five client sub-tenants, each through a scoped key or embed token.

Illustration · sub-tenant ids are examples. A bound key or token is forced to its own sub-tenant; asking for another returns 403.

What you get today

Shipped

  • Zero-touch sub-tenants

    Open mode creates a customer partition on its first event.

  • Embed tokens

    Bound to one customer, with report and origin allow-lists.

  • Generic counters query

    Count, sum, unique sessions or visitors and percentiles, grouped by up to two dimensions or by time: the building block for your own charts.

  • Usage per customer

    Event volume by sub-tenant for your own billing.

  • White-label data-out

    Signed webhooks under your brand’s header prefix, so customers never see YOM.

  • Custom dimensions

    Map your own context (plan, region, cohort) into reportable dimensions and metrics.

  • Partner API

    Management keys create and suspend projects and mint their keys from your own backend. They can never read analytics data.

  • The <yom-report> element

    Drop a report into your product with one HTML element and an embed token; around 9 KB gzipped.

  • MCP server for agents

    Read-only report tools for Claude and other AI agents, authorised by a read-scoped key or an embed token.

  • Warehouse exports

    Hourly files to S3, GCS or R2, or BigQuery, so your data team works from the raw events.

Other solutions

Sources

Third-party figures as published by the cited source. Last verified . Prices and policies change; check the source before relying on a number.

  1. [1]Luzmo (vendor survey), “Dashboards: dead, dying or evolving?.” www.luzmo.com/blog/dashboards-dead-dying-or-evolving (third-party estimate)
  2. [2]Hardal, “Segment pricing.” usehardal.com/blog/segment-pricing (third-party estimate)

Start measuring

Measure what you can prove.

The first 100,000 events every month are free. No credit card, no sales call.

Start free, no credit cardSee pricing