stubkit

RevenueCat alternative

The RevenueCat alternative that charges a flat fee, not a revenue share.

Stubkit gives you Apple, Google Play, and Stripe subscription validation on a single API — with a paywall builder, global edge entitlement cache, and flat monthly pricing that does not scale with your revenue.

Free forever on 1,000 MAU · No credit card · Full API + SDKs included

Feature-by-feature — Stubkit vs RevenueCat

FeatureStubkitRevenueCat
Pricing modelFlat monthly — $29/mo1% of tracked revenue
Free tier (MAU)1,000 MAU forever$2.5k MTR / then paid
Apple Server Notifications V2
Google Play RTDN
Stripe subscriptions
Global edge entitlement cacheEU / US / Asia replicasUS region only
Paywall builder (no-code)7 templates + custom fonts
A/B experiments on paywallUnlimited variants
Onboarding flow builder
Audiences + event triggersSuperwall-style, server-evaluatedBasic segments
Server-side ad conversion forwardingGoogle Ads + Meta CAPI built-inIntegrations only
Virtual currencies
App groups (multi-brand)
GDPR data export + delete (self-serve)Support request
Team roles + invitationsTeam plan only
SupportEmail on every plan, priority on BusinessCommunity / paid plans only
Revenue share0%1% above free tier

Migrate from RevenueCat in under a day

Your existing subscription data stays intact. Stubkit reads the same Apple notifications and Google RTDN messages RevenueCat does — point them at our webhook endpoint and your existing entitlements keep working.

  1. 1

    Open a free Stubkit account and create your first app — no credit card required.

  2. 2

    Point your Apple App Store Server Notifications V2 URL at Stubkit. Google Play RTDN and Stripe webhooks are configured the same way. Existing RevenueCat webhooks keep working in parallel during the switchover.

  3. 3

    Import the Stubkit SDK in iOS, Android, or web. Replace your RevenueCat entitlement checks with Stubkit's — the API surface maps one-to-one (hasActiveEntitlement, purchase, restore).

  4. 4

    Run Stubkit and RevenueCat side-by-side for a week. Reconcile any mismatches via the admin dashboard's audit log.

  5. 5

    Flip your clients to Stubkit-only, uninstall the RevenueCat SDK, and cancel your RevenueCat subscription.

Frequently asked questions

How long does the migration take?+

Most teams complete the migration in 1-2 days. The webhook pipeline and entitlement API map cleanly onto the existing RevenueCat integration, so you're not rewriting business logic — only swapping the SDK package and updating a few endpoint URLs.

Do I need to ask users to re-subscribe?+

No. Your existing subscriptions continue to renew through Apple, Google, or Stripe as before. Stubkit reads the same notifications those platforms already send out, so the entitlement state is reconstructed automatically — no user action needed.

What happens to RevenueCat's historical data?+

Stubkit can import your existing customer list and active entitlements via CSV or API. Historical revenue analytics remain in RevenueCat for your records; going forward, Stubkit tracks the full event stream.

How is Stubkit's pricing different from RevenueCat?+

Stubkit is a flat monthly fee ($0 Free, $29 Pro, higher tiers for scale). There's no revenue share and no per-event charge. RevenueCat bills 1% of tracked revenue above the free tier, which means your costs grow in lockstep with your success.

Is there a risk of downtime during the switch?+

Zero — you run both providers in parallel during the cutover week. Both receive the same Apple and Google webhooks, so entitlement state is kept in sync on both sides. You only stop sending to RevenueCat once you've validated Stubkit in production.

Which SDKs does Stubkit support?+

JavaScript/TypeScript, Swift (iOS/macOS), Kotlin (Android), Flutter/Dart, and direct REST from any backend language. Each SDK exposes the same entitlement API surface, published to npm / SPM / Maven / pub.dev.

Ready to switch from RevenueCat?

Start free, migrate on your own schedule, and only upgrade when you outgrow the 1,000 MAU free tier.

Start free