Meterbird Start free

Deploys, errors, traffic and revenue. Every app, one place.

Other tools each see one of these, for one app. Meterbird connects them for every app you run, so when a release breaks checkout, one page shows the deploy, the new errors and the drop in checkouts. Missing data is shown as missing, never as zero.

No credit card required. Every workspace starts with 14 days of Founder.

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.

Free check · no account

Is your website responding?

Paste one https:// address. We check it now, follow its redirects, and show the status, how long DNS, connecting, TLS and the first byte took, and when the certificate expires.

Analytics, Stripe, uptime, Vercel, Sentry. 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 alert, not twenty. The page lists what happened in the hour before, so you can tell your own bug from your host’s outage.

  • The deploy just before, new errors, visitors and checkouts, and your providers’ status pages, each as a plain fact. A deploy is an association, not proof of cause.
  • DNS, connection, TLS and response checked separately, so you know which step failed.
  • Alerts by email, Slack, Discord or webhook, and a recovery note after two passing checks.
Incident 42 in the fictional Acme workspace.

When revenue moves

See where paying customers came from.

Connect Stripe, Polar, Lemon Squeezy or Paddle, or send payments through the API, 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.

Features

What else is included.

Traffic

  • Goals and outbound links from data attributes, no code.
  • Live view of who is on each site now.
  • Short links that count their clicks.
  • Exclusions by IP, path, host or country, so your own visits don’t count.
  • First-party proxy so blockers don’t hide visits.
  • Imports from Plausible and Google Analytics.

Revenue

  • Stripe, Polar, Lemon Squeezy, Paddle or your own payments API.
  • MRR movements: new, expansion, contraction and churn.
  • Trials, cohorts and failed payments.
  • A public revenue page with verified figures and an MRR badge.

Reliability

  • HTTPS monitors with keyword checks.
  • Heartbeat monitors for cron jobs and workers.
  • Releases from Vercel and GitHub.
  • Errors from Sentry and from the browser.
  • Provider status from your host’s and suppliers’ status pages.
  • An optional AI summary of each incident, labelled as possibly wrong.
  • Imports from UptimeRobot and Better Stack.

Sharing and alerts

  • Public status pages with badges.
  • Shared dashboard links for a cofounder or investor.
  • Incident posts to Bluesky and X.
  • A weekly digest email per workspace.
  • A read API and an MCP server for Claude and Cursor.

Integrations

Connects to what you already run.

Built works today, and you set it up yourself. Beta is built but waits on Meterbird’s app being approved by the provider, so we set it up with you.

Revenue

  • Stripe Built
  • Polar Built
  • Lemon Squeezy Built
  • Paddle Built
  • Shopify Built
  • Payments APIFrom your own server Built

Hosting and deploys

  • Vercel Beta
  • GitHub Beta
  • Netlify Built
  • Cloudflare Pages Built
  • Railway Built
  • Fly.ioThrough a CI step Built
  • RenderThrough a CI step Built

Errors and traffic

  • Sentry Built
  • CloudflareTraffic analytics Built

Sign-ins and email

  • Clerk Built
  • Auth0 Built
  • Postmark Built

Database

  • SupabaseProject health Beta

Marketing

  • Search Console Beta
  • Google Ads Beta
  • Meta Ads Beta

Imports

  • Plausible Built
  • Google Analytics Built
  • UptimeRobot Built
  • Better Stack Built

Pricing

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

Billing

Free

$0 a montha year

Apps
2
Events a month
10,000
Monitors
3, every 5 min
Members
Unlimited
History
30 days

Founder

$19 a month$190 a year

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

Studio

$89 a month$890 a year

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

Prices in US dollars, excluding sales tax and VAT, which Stripe adds at checkout where it applies. Billed monthly or yearly through Stripe. A year costs ten months. Change plan or cancel at any time. Every new workspace starts with 14 days of Founder, no card needed, then stays on Free unless you pay. Free can be used for commercial projects, and its limits are never cut for workspaces that already have them. Past the monthly event allowance, events are still stored up to twice the allowance and kept for 7 days, so a launch spike is not lost. Past twice the allowance, new events are counted but not stored. You are never charged extra.