RevenueHog
log instart free →

// comparison

RevenueHog vs RevenueCat

These are different tools that happen to share a word. RevenueCat sells purchase infrastructure; RevenueHog sells visibility. Here's an honest feature table, when each is the right choice, and how to use both at once.

last updated 2026-07-11 · by revenuehog

tl;dr

Building in-app purchases (paywalls, entitlements, cross-platform)? Use RevenueCat. Watching App Store revenue (live events, MRR, churn, alerts) with no SDK and no cut of your revenue? Use RevenueHog. Already on StoreKit 2 with your own purchase code? RevenueHog gives you the analytics without adopting infrastructure you don't need. And because RevenueHog forwards Apple's verbatim payloads, "both" is a real option.

What each product is

RevenueCat is in-app purchase infrastructure: an SDK for iOS, Android and web that runs your purchase flow, keeps entitlements consistent across platforms, and adds paywall tooling, experiments, webhooks and charts on top. Pricing is usage-based: free up to $2,500 of monthly tracked revenue, then 1% of MTR (as of 2026-07-11, revenuecat.com/pricing).

RevenueHogis revenue telemetry for App Store developers: connect an App Store Connect .p8 key and every app on the key imports with about a year of daily history (Apple's daily-report limit); Apple's Server Notifications V2 stream into a live feed with MRR, churn, trials and customer LTV on top, and get forwarded, verbatim, to any endpoints you configure. No SDK (optional SDKs add user-level attribution only). Everything on the web is free; the only paid thing is the iOS push-alerts subscription ($4.99/mo or $39.99/yr). Never a percentage of your revenue.

Feature table

RevenueCat cells reflect revenuecat.com (pricing & public docs) as of 2026-07-11; verify current capabilities with RevenueCat before deciding.
RevenueHogRevenueCat
Data sourceYour App Store Connect API key + Apple Server Notifications V2Its SDK in your app + server-side receipt/transaction handling
SDK requiredNo. Nothing ships in your app (optional SDKs add user-level attribution only)Yes: the SDK (or a server integration) is the product's foundation
PriceFree on the web, all of it; the only paid thing is the iOS alerts subscription ($4.99/mo or $39.99/yr)Free up to $2,500/mo tracked revenue (MTR), then 1% of MTR (as of 2026-07-11)
PlatformsApple / App Store only (today)iOS, Android, web and more
Live purchase eventsYes: Apple's Server Notifications V2, verified and streamed to a live feedYes: its own webhook events derived from store notifications
Event forwardingYes: relays Apple's verbatim signedPayload, so downstream signature verification still worksWebhooks + integrations in RevenueCat's own event format
Paywalls & A/B testingNo, not what RevenueHog doesYes: paywall tooling and experiments (a core RevenueCat strength)
Entitlements at runtimeNo. RevenueHog doesn't sit in your purchase pathYes: entitlement checks via SDK/API (a core RevenueCat strength)
MRR / churn analyticsYes: MRR, churn, trials, revenue/day, per app or portfolio-wide; freeYes: charts and metrics on tracked revenue
Customer LTVYes: per-customer LTV and purchase history derived from transactionsYes: customer profiles and LTV
Push alerts on your phoneYes: iOS app with per-event alerts, $ thresholds, quiet hours, MRR milestones (the $4.99/mo subscription)Via integrations (e.g. Slack) rather than a first-party alerts app
Home/lock-screen widgetsYes: iOS widgets (today's haul, MRR sparkline, trials)—

When RevenueCat is the better choice

Pick RevenueCat over RevenueHog if any of these are true:

  • ▸You're building or rebuilding your purchase flow. Paywall tooling, remote paywall config, and A/B price experiments are RevenueCat's home turf; RevenueHog has none of that, on purpose.
  • ▸You ship on Android or cross-platform. RevenueHog is Apple-only today; RevenueCat unifies iOS, Android and web subscriptions in one system.
  • ▸Your app logic needs runtime entitlement checks. "Is this user premium right now, on any device?" is a purchase-infrastructure question, and RevenueCat answers it.
  • ▸You want managed receipt/transaction validation inside your product's critical path, rather than running your own StoreKit 2 server logic.

When RevenueHog fits

  • ▸StoreKit 2 already handles your purchasesand adopting an SDK just to see charts feels backwards. RevenueHog reads Apple's data directly; nothing ships in your app.
  • ▸You want analytics without integration work: one .p8 key, every app on it imports, about a year of history appears, and the live feed starts when the (one-paste or one-click) notification wiring is in.
  • ▸You don't want a tool taking a percentage of your revenue.RevenueHog never does; growth doesn't change what you pay.
  • ▸You want the events on your phone: renewals, trials, churn as push alerts, plus widgets, with thresholds and quiet hours so it's signal, not noise.

Use both

Apple allows exactly one production Server Notifications URL per app, which usually forces a choice. RevenueHog's forwarding removes it: point Apple at RevenueHog, then add RevenueCat's Apple notification URL (and/or your own backend) as forwarding endpoints. RevenueHog relays Apple's verbatim signed payload(not a re-signed or reformatted copy), so every downstream consumer's signature verification keeps working exactly as if Apple had called it directly. Details in the Server Notifications V2 guide.

FAQ

Is RevenueHog a RevenueCat alternative?
For subscription analytics, yes, and it's free with no SDK. For purchase infrastructure(building the purchase flow, entitlements, paywalls), no: RevenueHog deliberately doesn't do those jobs. If StoreKit 2 already handles your purchases, RevenueHog gives you the visibility layer without new code in your app.
Can I use RevenueHog and RevenueCat together?
Yes, and it works well: point Apple's Server Notifications at RevenueHog and add RevenueCat's Apple notification URL as a forwarding endpoint. RevenueHog relays Apple's verbatim signedPayload, so RevenueCat's own signature verification keeps working. You get the live feed and free analytics without giving up RevenueCat's infrastructure.
Does RevenueHog take a percentage of my revenue?
No. Never a percentage of your revenue. Everything on the web is free; the only paid thing is the iOS alerts subscription ($4.99/mo or $39.99/yr). RevenueCat is free up to $2,500 MTR and then charges 1% of monthly tracked revenue (as of 2026-07-11).
Do I need to change my app to use RevenueHog?
No SDK required. You connect an App Store Connect API key and optionally paste one notification URL into App Store Connect (or let RevenueHog set it with one click, which needs an Admin key). Optional SDKs exist only to add user-level attribution.
Does RevenueHog support Android / Google Play?
No. RevenueHog is Apple / App Store only today. If you need cross-platform coverage in one tool, that's a genuine reason to pick RevenueCat (or run both, per above).
How far back does RevenueHog's history go?
About a year of daily history on import: Apple's daily-report limit, not ours. From the moment you connect, history accrues forward, and the live feed captures events as they happen.

Ready to see your own numbers? Start free, or check pricing first (short version: free).

sources

RevenueCat pricing — revenuecat.com/pricing (free ≤ $2,500 MTR, then 1% of MTR; checked 2026-07-11).

Apple: App Store Server Notifications V2 — developer.apple.com/documentation/appstoreservernotifications (one production URL per app).

RevenueHog pricing — this site's /pricing (prices from the same source the app bills from).

// related

App Store Server Notifications V2 →The mechanism behind the live feed, and the one-URL limit that makes forwarding matter.Pricing →Free on the web; the iOS alerts subscription is the only paid thing.Create an App Store Connect API key →The five-minute prerequisite for no-SDK telemetry.Documentation →Setup guide and settings reference.