Pgyer Docs
iOS Signing & Devices

iOS Signing Certificate Types

Apple Developer account types, the differences between Ad Hoc, In-House, and App Store signing, and how each is labeled in Pgyer.

For an iOS app that hasn't shipped to the App Store yet, installation depends on the signing certificate, provisioning profile, distribution method, and device requirements for the exported .ipa. This page covers the signing methods Pgyer supports and which certificate types each kind of Apple Developer account can use.

Apple Developer Account Types

The table distinguishes common enrollment types in the Apple Developer Program from the Apple Developer Enterprise Program. A membership program, signing certificate, and distribution method are different concepts.

Program / Enrollment TypeAnnual FeeApp Store DistributionAd Hoc Device Registration LimitEligibility Summary
Apple Developer Program — IndividualUSD 99 per membership year, or local pricingSupportedUp to 100 per device family per membership yearLegal age of majority, identity, account, and other enrollment requirements
Apple Developer Program — Organization / CompanyUSD 99 per membership year, or local pricingSupportedUp to 100 per device family per membership yearLegal entity, authority to sign agreements, D-U-N-S Number, and other applicable Apple requirements
Eligible educational institutions and other qualifying organizationsMay request an Apple Developer Program fee waiver; free only after Apple approves the waiverAccording to the membership programUp to 100 per device family per membership yearMust meet fee-waiver requirements; education does not automatically mean free membership
Apple Developer Enterprise ProgramUSD 299 per membership year, or local pricingThis program is not for App Store distributionThe same 100-per-family, per-membership-year limit applies when using Ad HocAt least 100 employees, a legal entity, proprietary internal-use apps, Apple verification, and other requirements; a D-U-N-S Number alone is insufficient

Ad Hoc registration limits apply to the developer team per membership year and per product family; iPhone and iPad are counted separately. This is not a separate allowance for each app or signing certificate. Disabling a device during the membership year does not restore an available slot. In-House does not use Ad Hoc's device-by-device registration workflow, but it has the internal-use restrictions described below.

See Apple's full enrollment requirements, fee-waiver requirements, device registration limits, and Enterprise Program requirements.

For export steps, see Build an iOS IPA.

Signing Methods and How Pgyer Labels Them

This page compares three common iOS distribution methods. Pgyer detects the certificate used in the installer and labels the release accordingly on the download and management pages:

Signing MethodLabel in PgyerWho Can InstallApplicable Accounts
Ad HocBetaDevices registered in the Apple developer account and included in the Ad Hoc provisioning profile used for exportIndividual, Company, Education, Enterprise
In-HouseEnterpriseEmployees within the organization, subject to valid signing, compatibility, and trust requirementsEnterprise
App StoreApp StoreInstallable only through the App StoreIndividual, Company, Education

Distributing iOS apps through Pgyer typically uses Ad Hoc or In-House:

  • For Ad Hoc: register each target device, include it in the provisioning profile used for export, and export the IPA. Xcode can manage profiles with automatic signing. Signing certificates and provisioning profiles are distinct; device lists belong to the profile. See Apple's Ad Hoc provisioning profile workflow.
  • For In-House: eligible Apple Developer Enterprise Program organizations may distribute their proprietary internal-use apps privately and securely to employees within the organization. Not requiring per-device UDID registration is not permission to distribute to the public or a guarantee that every device can install the app.

On this page