Skip to content

About

We got tired of refreshing.

We built RevTrakkr because every other indie dev we talked to was opening App Store Connect 30 times a day and still finding out about churn from a digest email.

The problem isn't that App Store Connect doesn't have data. It does — eventually. The problem is the gap. Apple aggregates daily. Stripe is real-time but only for half your revenue. By the time your dashboard catches up, the trend you needed to see has already happened.

So you tab between them. You build a spreadsheet. You set a reminder to "check numbers Tuesday morning." And when something goes wrong — a refund spike, a failed-renewal cluster, a price-mismatch bug — you find out three weeks late from someone tweeting at you.

The version that didn't work

We tried the obvious thing first: a daily email digest. Founders ignored it. We tried weekly. They ignored that too. Turns out nobody wants another email.

What people actually wanted, when we asked, was a phone that buzzed when something happened. A trial converted. A renewal failed. A refund hit. Tell me. Now. Don't wait for tomorrow morning's roundup.

What RevTrakkr is, and isn't

RevTrakkr is a least-privilege revenue feed across App Store Connect and Stripe. It tells you when revenue moves. That's the whole product.

It is not a paywall (use RevenueCat). It is not a billing platform (use Stripe). It is not a finance tool for your accountant. If your job is to ship products and your problem is finding out what just happened to revenue, this is for you.

What we believe

  • Notifications should be a privilege

    Five events on by default. Quiet otherwise. We'd rather under-notify than become another email digest you mute.

  • Least privilege is non-negotiable

    We use App Store Connect API keys and Stripe restricted keys scoped for ingestion and webhook setup. We don't need permissions to initiate refunds, change subscriptions, or charge anything.

  • Indie pricing for indie founders

    $7.99/mo. No per-app, no per-event, no usage tier. We'd rather charge a fair price than build freemium machinery we can't sustain.

  • iOS-first, web-second

    The phone is where the alert is most useful. We start there.

If this sounds like your day, try it.

14 days. We'll show you what a live revenue feed feels like.