StoreKit 2 gives you the building blocks, but you still need server-side verification, entitlement management, paywall UI, and cross-platform support. Tierux wraps all of that into one API — with AI-agent setup in minutes. Our App Store path is newer than our Google Play path, and the table below is honest about it.
| Capability | Tierux | StoreKit 2 (DIY) |
|---|---|---|
| Setup | AI-agent over MCP — Bundle ID + one prompt | Manual JWS parsing, server-side code, key management |
| Server-side verification | Store-verified on our servers, zero-trust client | Build and maintain your own verification server |
| Entitlement management | Built-in — queryable via REST API | Build your own entitlement state machine |
| Remote paywall config | Yes — change without app release | Hardcoded in your app |
| Cross-platform (Android) | Yes — unified entitlement model | Google Play Billing requires separate implementation |
| Pricing | Flat $39/mo up to 1,000 subscribers | Free — but engineering hours are your cost |
| Time to launch | Minutes via AI agent | Weeks to months of engineering |
| Subscription lifecycle sync | App Store Server Notifications wired — hardening in progress; Play RTDN fully handled | Build your own webhook handlers |
| Win-back / cancellation offers | Google Play — yes; App Store — not yet | Requires custom implementation |
| Maintenance burden | Zero — managed platform | Ongoing — store API changes, security patches |
StoreKit 2 is Apple's native framework and is free to use. The cost is in engineering time — building server-side verification, entitlement state management, paywall UI, and ongoing maintenance. Tierux provides these as a managed service.
You want to ship subscription billing fast without building server-side infrastructure. You need cross-platform support — Google Play today, App Store in progress. You value predictable flat pricing and want your AI agent to handle the setup over MCP.
You have engineering capacity to build and maintain server-side verification, your app is iOS-only, you have no need for remote paywall configuration or entitlement analytics, and you want zero external dependencies.