We are the publisher of an iOS application available on the App Store, published under our Apple Developer account.
Our app is a B2B enterprise product where multiple independent enterprise server deployments — each operated by a separate customer organisation — send push notifications to their own end users through our single published app binary.
To support this multi-tenant architecture, we have designed the following push notification setup:
- A single iOS app published under our Apple Developer Team
- A single APNs P8 authentication key generated from our Apple Developer account
- One Firebase project provisioned per customer organisation, each configured with the same P8 key and the same iOS bundle ID
- Each customer's Firebase project independently delivers push notifications only to device tokens registered by that customer's users
- At any point in time, a single device is registered with exactly one customer's Firebase project — there is no concurrent multi-Firebase registration on a single device
We have technically validated that multiple Firebase projects sharing the same P8 key and bundle ID can each deliver push notifications to our app without conflict. APNs validates the JWT signed by the P8 key and the bundle ID claim, which is consistent across all projects.
Our question is:
Does this architecture — where multiple Firebase projects, all controlled by the app publisher or partners and provisioned with the same APNs P8 key and bundle ID, independently send push notifications to a single App Store app — comply with the Apple Developer Program License Agreement and Apple's APNs usage policies?
We want to confirm this before proceeding to production and App Store submission to ensure we are fully compliant with Apple's guidelines? Multiple server will send push notifications to single app store app via each separate firebase account per server, will it violate any apple policy?
Please let us know if any additional technical details would help clarify our setup.