ferno

Product analytics that tells you why metrics moved.

Ferno watches your product events, flags the numbers that changed, and shows you the cause with the evidence behind it.

npm install @fernohq/analytics-next
Sample data

Signals

Why did fewer people finish signing up this week?

Likely causeHigh confidence

Tuesday’s update broke the Continue button on the Android sign-up form.

Tuesday’s update
  • The drop began within an hour of Tuesday’s update.Supports
  • Sign-ups on iPhone and web stayed normal.Supports
  • Ad traffic held steady, so fewer visitors isn’t the reason.Not the cause
Suggested fix: Roll back the sign-up form changeChecked deviceapp_versionsignup_source

01 / The questions behind the change

The graph moved.
The questions start there.

  • What changed?
  • Who felt it?
  • Is it real?
  • What happens next?

02 / One investigation

From change
to cause.

A signal arrives. Ferno compares the baseline, tests the strongest explanations, and keeps the evidence attached.

  1. Did it really change?

    Done
  2. Who and where?

    Done
  3. What else explains it?

    Checking now
  4. What should happen next?

    Up next

Investigation in progress

Did the release cause the activation drop?

Broke the change down by

platformversionacquisition_source
Holds
The change is concentrated in new browser projects.
Doesn’t hold
The same release is healthy in existing projects.
Next check

The first-event path for new projects.

03 / The handoff

Bring an answer
to the room.

A recommended next move, with the evidence and the open questions attached.

Recommended next moveIllustrative

Revert the first-event change for new browser projects.

Activation for new browser projects dropped right after v1.8.4. Existing projects on the same release stayed healthy.

Still open Acquisition mix hasn’t been ruled out yet.

Moderate confidence, with evidence attached

Nothing runs until someone on your team approves it.

Create workspace (opens in a new tab)

04 / Connect the product

Start with the events you already send.

Ferno’s browser and Node SDKs take track, identify, page, screen, group, and alias calls. Keep the event names your team already understands.

analytics.tsTypeScript
import { AnalyticsBrowser } from
  '@fernohq/analytics-next'

const analytics = AnalyticsBrowser.load({
  writeKey: 'ferno_pk_••••••'
})

analytics.track('checkout_started')
Listening for change

05 / Questions

Before you connect anything.

No. Ferno’s browser and Node SDKs are built on Segment’s open-source analytics library, so track, identify, page, screen, group, and alias work the way your team already writes them. Point them at your Ferno project key and keep your event names.

Ferno compares each project’s most recent 24 hours of events with the previous 24 hours. When something moves enough to matter, it opens an investigation instead of just raising an alert.

Every report states its confidence, shows the queries Ferno ran and what they returned, and lists what it couldn’t rule out. Your team can check the reasoning instead of taking it on trust.

No. Investigations are read-only. Ferno recommends a next move, and anything that touches a connected tool, like your Linear workspace, needs someone on your team to approve it first.

Every API key belongs to one workspace and project, and Ferno decides where events go from the key itself. Keys are stored as a one-way digest, and connected integration credentials are encrypted at rest.

Read the security overview