About Trace

The number was never the question

Trace exists to end that argument — by naming the cause of every metric shift, the day it happens.

It reads every event you already collect, names the release that moved the number, and surfaces the drop-off you would otherwise find in a support ticket.

Meet our Customers

Our position

Dashboards show what. We built the why.

Product teams spend half the week deciphering their own numbers. More analysts and more dashboards never fixed it.

PLAIN LANGUAGE

Explanations, not charts

Every movement described in a sentence you can act on.

ANNOTATED RELEASES

Every deploy, marked

Releases are annotated the moment they ship.

CAUSE ATTACHED

Alerts arrive explained

Anomalies come with the reason already found.

COHORT SIGNALS

See exactly who felt it

Every change mapped to the cohort it reached.

By the numbers

Numbers you can build on

See the case studies

Weekly reach

12,800+

Product teams every week

Product, growth and data teams across 40 countries open Trace as part of their normal working week — not as a monthly reporting ritual.

Time saved

41%

Less time spent digging

Average reduction in hours spent tracing a metric back to whatever caused it, measured against the quarter before Trace was installed.

Weekly reach

9 min

From anomaly to named cause

Median time between a metric leaving its normal band and a Signalroom message naming the release, the cohort and the size of the impact.

Team

The people behind the answers

Nadia Fournier

Founder & CEO

Oskar Lindqvist

CTO

Priya Raghavan

Head of Data & AI

Tomas Beck

Design Director

Amara Boateng

Designer

Ruben Castillo

Lead Platform Engineer

Mei Tanaka

Head of Product

Layla Haddad

Head of Customer Success

The number was never the question

Dashboards show what. We built the why.

Numbers you can build on

The people behind the answers

Want to know why your numbers moved?

A guided first look, in 30 minutes

Questions before you book?