Everything Erdi puts on the timeline

Timeline

Every deploy, release, price change and support spike sits on the same line as the numbers, so the fortnight before a dip is already assembled.

Bundled markers

Events on the same day share one marker with a count, so a busy release day does not smear the chart.

Breakdown

Metrics that belong together — scans, sources, countries — plot as a group under the primary line.

Compare projects

When two products share a role, the all-projects view indexes them together so you can see which one moved.

Export

Download the chart as CSV from the project, or take a full copy of the account from Settings → Your data.

Vercel

Production deploys land as deploy markers. Preview stays off the timeline.

GitHub

Published releases and tags become markers; closing an issue labelled user-facing becomes a task.

Sentry

New error and fatal issues appear once, next to the deploys from that day.

Netlify

Production deploys become deploy markers. Other contexts do not.

RevenueCat

Purchases count as a daily metric; cancellations and billing issues become events.

Stripe

Revenue and new customers are pulled from charges, with a restricted key.

App Store Connect

Downloads, updates and proceeds, two days late, the way Apple reports them.

Play Console

Installs and uninstalls from the statistics bucket, also two days late.

Plausible

Visitors, pageviews and visit duration, pulled from the Stats API.

Umami

Visitors, pageviews and visit duration from Umami Cloud or your own instance.

Generic endpoint

Anything else posts deploys, releases and daily numbers to one HTTP endpoint — no adapter to wait for.

The board

Cards you move to done write an event with source board, so the board is a source, not a side channel.

Support forwarding

Point your existing support address at Erdi. Critical tickets become markers; the rest only count, so the timeline stays readable.

Alerts

Five conditions: below, above, drops by %, rises by %, and no data. Erdi checks them once a day on the same cron as the daily mail — it is not an hourly watcher — and the mail already contains the events from the fortnight before, or says that nothing shipped.

Daily digest

What shipped, what came in, and how the numbers moved, in one mail when the day is over.

Weekly digest

The week's events sit next to how the numbers moved, so the fortnight is already in the inbox.

EU hosting

The database and authentication run in Frankfurt.

Encrypted keys

Webhook secrets and connector keys are stored with AES-256-GCM, not in config.

DPA

A data processing agreement under Art. 28 GDPR is published at /dpa.

No cookie banner

The marketing site sets no cookies, so there is nothing to consent to. A session cookie exists only after you sign in.

No AI training

We do not train models on your events, metrics or mail.

Export

CSV from the project, a full archive from Settings → Your data.

Deliberately not built

Erdi is built for one person watching their own products. These exist in other tools because teams need to coordinate — that is not what this is.

• Teams — Erdi is for one person watching their own products.
• Time tracking — It records what shipped, not how long it took.
• Comments — The timeline is events and numbers, not a discussion.
• Assignment — There is no one to assign a card to.
• Recurring tasks — A card is a thing that ships once, not a repeating chore.
• Tracking script — Erdi never runs on your users’ devices.