erdiknowsSign in

Erdi was watching.

Every deploy, release, price change and support spike lands on the same timeline as your metrics. When the numbers move, the fortnight before it is already there.

Daily active users

UsersEvent
3Aug 1Aug 21

Aug 14

  • deployv1.4.0 — paywall rewrite
  • ticket3 reports: sign-in fails on iOS 18
  • externalPrice raised to EUR 9

Click a marker. That list is the whole product.

Set it up once, then forget it

Two lines in your CI and events arrive on their own. No dashboard to keep up to date, nothing to remember on release day.

Keep the tools you already have

Push your numbers from whatever you use now. Nothing to install on your site, no second analytics tool to reconcile.

Rule things out in seconds

Often the useful answer is that nothing shipped that fortnight. That is when you stop suspecting your own code and start looking outward.

What it won't tell you

The cause. At indie data volumes the noise is usually louder than the signal, and a tool that names a culprit for every random dip just manufactures false certainty. Mobile releases make it worse: a release is a ramp, not an edge. Erdi shows the markers and the window. The judgement stays yours.