Private beta · waitlist open

Traffic, revenue and app health in one place.

Meterbird tells you which of your apps needs attention, what changed and what it did to revenue. Every figure says how fresh it is, and missing data is shown as missing, never as zero.

Join the waitlist Try the clickable prototype

The Meterbird overview for a workspace of four apps. Two need attention: Invoicely's checkout endpoint has been down for 12 minutes, and Tallyho's tracker has sent no events since 07:12. Below, a table lists each app's health, visitors, conversion, revenue and data freshness. — The clickable prototype. Acme and its four apps are fictional.

Analytics, Stripe, uptime, Vercel, GitHub. Five tabs every morning, and still no answer to one question: did yesterday’s release cost us sales?

The morning check

Know which app needs you in under a minute.

Every app on one page, worst first, with the reason in words rather than a red dot. When nothing needs you, it says so and lets you get on with your day.

A silent tracker counts as needing attention. It is never shown as healthy.
Visitors, conversion and revenue beside each app’s health, each currency on its own.
Every figure says when it was last updated.

The attention queue: Invoicely is down, with Incident 42 open since 14:20; Tallyho is stale, with no events since 07:12. Each row says where to go next.

When something breaks

One alert, and a page that answers “is it me?”

An incident opens after two failed checks, not one, and you get one email, not twenty. The page shows what shipped just before, which step failed and who was on the site.

The deploy five minutes earlier, labelled as an association, not proof of cause.
DNS, connection, TLS and response checked separately, so you know which step failed.
A recovery email after two passing checks.

Incident 42, Checkout endpoint down. The timeline shows deployment 7c1e9a2 at 14:15, the first failed check at 14:20 and the incident opened at 14:21. A side panel shows DNS, connect and TLS passed and the response failed with HTTP 502.

When revenue moves

See where paying customers came from.

Connect Stripe and each payment is linked to the visit that brought it: source, campaign, landing page, country or device.

Money we cannot link stays in its own Unattributed row. It is never spread across channels.
The attribution model and lookback window are always on screen.
Each payment says how it was linked: by checkout, user ID or email.

Where paying customers came from, in euros: €4,962 attributed and €1,880 unattributed. Google leads with €1,890 from 44 payments. The unattributed row is hatched and the total is €6,842.

Pricing

Priced on the two things that cost us: events and monitors.

Free

Nothing to pay

Apps: 1
Events a month: 10,000
Monitors: 3, every 5 min
History: 30 days

Founder

Price set during the beta

Apps: 5
Events a month: 250,000
Monitors: 10, every minute
History: 1 year

Studio

Price set during the beta

Apps: 25
Events a month: 2 million
Monitors: 50, every minute
History: 2 years

These are planned allowances, not final. We will set prices with our first users and publish them before anyone is asked to pay. There is no billing during the private beta.

Private beta

Join the waitlist.

We are starting with founders and small teams who run two or more live web products. We will email you when your invite is ready.

We use your email for the invite and, if you tick the box, one request for a call. Nothing else. Ask us any time and we will delete it.