Cross-platform Player Identity
Guest, Apple, Google and more. Link accounts and keep your players.
Player identity, in-app purchases and entitlements made simple. Integrate once and focus on your game.
Get Started FreePowerful features without the enterprise complexity.
Guest, Apple, Google and more. Link accounts and keep your players.
Handle purchases, receipt verification and restoration.
One entitlement system across App Store and Google Play.
No backend team required. Save time and ship faster.
Use a single SDK and let Open4ID handle the complexity.
Start free. Upgrade as you grow — or pay only for what you use.
Join indie and small studios building with Open4ID.
What studios ask before they integrate Open4ID.
Open4ID is one SDK and hosted API for player identity, in-app purchases and entitlements in mobile games. Your game calls the SDK to sign players in and to submit a purchase, and Open4ID verifies the App Store or Google Play proof on its servers before it grants an entitlement — so you do not build or run that backend yourself.
There is a free plan with one application, 1,000 monthly active users and a monthly transaction allowance — no credit card required. Paid plans add more applications, MAU and transactions, pay-as-you-go bills per application, MAU and transaction, and Enterprise pricing is negotiated. The pricing section above always shows the current prices and limits.
iOS and Android, with server-side verification for App Store (StoreKit) and Google Play Billing purchases. Open4ID ships SDKs for Android, iOS, Flutter and JavaScript, and games that keep their own purchase UI — Unity IAP, RevenueCat or native billing — can submit the store proof for verification instead.
No. Sign-in, receipt verification, entitlement state and purchase restore run in the hosted Open4ID API; your game calls the SDK and reads entitlements. Server-to-server verification is available when your own backend needs to check a player token or a purchase.
A player who is active in your game during the calendar month. Each plan includes a monthly MAU allowance and a monthly transaction allowance, and the dashboard shows current usage against them so you can upgrade or move to pay-as-you-go before you outgrow a plan.
Open4ID processes player data as a processor for your studio: your game decides what is collected and your privacy policy applies to players. Account data, retention, deletion and cookies are described in the Privacy Policy, GDPR page and Cookie Policy linked in the footer.