Apple Developer Program: Cost, Tiers, and How to Enroll

Ninety-nine dollars a year. That's the figure everyone quotes for the Apple Developer Program, and Apple does list the membership at 99 USD per membership year. It's also the least useful number in the room if your actual job is getting an internal iOS app onto 300 company iPhones without anyone emailing a build around.

So this guide answers the company version of the question. What the membership buys you, what the 299 USD Enterprise Program really demands, why Custom Apps through Apple Business Manager has quietly become the default answer for internal apps, and the three mistakes that kill a deployment.

One clarification first, because the names collide. The Apple Developer Program is about building and signing apps. The old Device Enrollment Program, now Automated Device Enrollment, is about registering the iPhones and iPads you own so they enroll into an Apple MDM at first boot. If you came here to set up devices rather than ship an app, our guide to Apple mobile device management is the one you want.

What the program actually gives a company

Strip away the marketing and a membership does one thing that nothing else can do: it lets you sign code that Apple will accept. Without a signature chaining back to an Apple-issued certificate, your app will not install on an iPhone, managed or not. Everything else in the membership is downstream of that.

In practice, a company gets four things it can't get for free:

• Signing certificates and provisioning profiles, issued to your organization rather than to a person
• App Store Connect, where builds are uploaded, reviewed, versioned and assigned roles
• TestFlight, for pilots before a fleet-wide rollout
• The right to publish Custom Apps, private builds that never appear in public App Store search

The free Apple account tier is worth knowing about because it tempts people. You can download Xcode, read documentation, file bugs and run a build on your own iPhone. But a personal team's provisioning profiles expire after seven days and cap out at three devices, which makes it a learning tool, not a distribution channel. We've seen an internal app demo-ed on a free profile and presented as "ready to deploy". It wasn't.

For the short version of the definitions, our Apple Developer Program glossary entry covers the same ground in a page.

The real cost is not 99 dollars

The fee is trivial for any company with a mobile project. What costs money is everything around it.

Start with the enrollment itself. Organization enrollment needs a D-U-N-S number, a legal entity, and a verification step where Apple calls someone with authority to sign agreements. Budget two to four weeks, not an afternoon. Nonprofits, accredited schools and government entities can ask for a fee waiver, so for those the 99 dollars can genuinely be zero while the paperwork stays the same.

Then the renewal. Miss it and your apps come off the App Store, your certificates stop being trustworthy, and TestFlight builds go dark. One calendar invite, owned by a team rather than a person, prevents a week of panic.

The part nobody budgets is the annual rebuild. Apple's distribution certificates last three years, but in-house provisioning profiles expire after twelve months, which means an internally distributed app has to be re-signed and re-shipped every year even if not a single line of code changed. That's a developer's day, a QA pass and a deployment window, every year, per app. Multiply by the number of internal apps you run.

And if you sell anything through the App Store, the commission dwarfs the membership: 30 percent on digital goods, or 15 percent under the App Store Small Business Program if you earned under one million dollars in the previous calendar year. Enrollment in that program is a separate application, not an extra fee. For a company distributing only internal tools, none of this applies: there's no transaction, so there's no commission.

Individual or organization: the question that matters later

Individual enrollment is fast. You sign in with an Apple Account, pay, and you're a member, with your own legal name showing as the seller. Organization enrollment is slower because Apple verifies you exist: a D-U-N-S number from Dun and Bradstreet (free in most countries, usually a few business days), a legal entity that isn't a trade name or a branch, and an applicant who can bind the company.

Take the slow route. An individual account has one owner and no real role model, so the person who enrolled controls the signing identity, the app listings and the renewal. When they change jobs, you discover that your company doesn't own its own apps.

Organization enrollment gives you App Store Connect roles instead: an Account Holder, Admins, App Managers, Developers, Marketing. Hand your agency or contractor a Developer or App Manager role inside your team rather than letting them sign with their own account. Same work, and the certificate stays yours when the contract ends. If you already have an Apple Business Manager tenant, you've done the D-U-N-S and verification dance once already, and Apple Business Manager uses the same organizational identity.

Developer Program, Enterprise Program or Custom Apps

Three routes, and most companies pick the wrong one because the Enterprise Program sounds like the enterprise answer. It usually isn't, because Apple no longer lets most companies in.

The Apple Developer Enterprise Program costs 299 USD a year and requires 100 or more employees, a D-U-N-S number, a public website on your own domain, a separate Apple Account from your standard developer account, and a verification interview with Apple. Use is restricted to proprietary apps for your own employees, Apple evaluates that use continuously, and applications get rejected at Apple's discretion. It's a real program, not a paid upgrade.

Custom Apps sit inside the standard 99 dollar membership. You build a private app, submit it for review like any other, and Apple makes it visible only to the organizations you name, through Apple Business Manager or redemption codes. It never appears in public search. For most internal apps, that's the route, and it's why the Enterprise Program has shrunk to a niche.

Our opinion after seeing both in the field: take Custom Apps unless your release cadence genuinely can't live with App Review, or your app does something Apple wouldn't approve even privately. The Enterprise Program buys speed and pays for it with an audit relationship and a certificate that can be revoked. Both routes feed the same enterprise app store on the device, so the user experience is identical either way.

Getting an internal app onto devices without the public App Store

Here's how the three channels actually behave once a device is in your fleet.

Custom Apps plus MDM is the clean path. Apple approves the build, it appears in the Custom Apps section of your Apple Business Manager account, you claim licenses in Apps and Books (the section everyone still calls VPP), and your MDM assigns them by device serial number. On a supervised device the install is silent: no Apple Account on the phone, no password typed 300 times, no prompt. Updates land the same way. Licenses return to your pool when a device is wiped.

That install is also what makes the app a managed app, which is the part that matters for offboarding. Managed means the MDM can configure it before first launch, keep its data away from personal apps, and remove the app and its data when someone leaves. An app a user installed themselves gives you none of that.

Enterprise in-house distribution skips review. You sign with an enterprise certificate and your MDM or your own hosting serves the build. Faster, and the certificate and profile expiry dates become your problem rather than Apple's.

TestFlight is for pilots and people keep misusing it as a distribution channel. Builds expire 90 days after upload and can't be extended, external testers need Beta App Review on the first build of each version, and testers install by accepting an email or a public link, which is the opposite of managed. Fine for twenty volunteers in a two-week pilot. Not fine for the warehouse.

None of these channels help if the device isn't enrolled yet. That's the other half of the problem, and zero-touch enrollment is what closes it: a phone out of the box registers itself, gets supervised, and has your internal app installed before the user reaches the home screen.

One note on the EU, since it comes up in every meeting now. Since iOS 17.4 in March 2024, the Digital Markets Act opened alternative marketplaces and web distribution in the European Union, and Apple is changing the eligibility rules for operating a marketplace from 1 October 2026. For a company that just needs its field app on its own phones, this changes nothing useful. Running a marketplace to distribute one internal app is absurd. Custom Apps plus MDM remains the answer.

Three traps worth a calendar reminder

The expired profile. An enterprise-signed app whose provisioning profile has expired refuses to launch. Not degraded: dead, on every device, the same morning. You can push a fresh profile through MDM to devices that already have the app, but new devices need a rebuilt binary. Track the expiry date somewhere a human will see it, and rebuild a month early.

The account that belongs to a person. Agencies sign client apps with their own membership all the time, because it's faster. Then the contract ends, or the developer who enrolled leaves, and the signing identity walks out with them. Hold the membership in your company's name, use App Store Connect roles for everyone else, and put the Apple Account on a shared mailbox with two-factor on a device the team controls.

The review rejection nobody planned for. Custom Apps go through App Review like public apps. If your app hides behind a corporate login, Apple needs working credentials and sample data, or it gets rejected for being untestable. Build that into the submission checklist and your first review takes days instead of three rounds.

How Appaloosa fits

Appaloosa distributes internal iOS apps whichever way you chose to sign them. Custom Apps approved in Apple Business Manager arrive through the Apps and Books sync and install silently on supervised devices. Enterprise-signed IPAs are uploaded to your private catalog with full version history, assigned per device group, and updated without user action. Version history shows when each build was signed, which is the reminder most teams are missing when a provisioning profile gets close to its expiry date.

Public App Store apps, your own builds and managed configuration all sit in the same catalog, on iOS and Android, as described on the Mobile Application Management page.

FAQ

Do we need the Apple Developer Program just to deploy App Store apps to our fleet?

No. Buying and assigning App Store apps happens in Apple Business Manager, which is free, and your MDM pushes them from there. You need a paid membership only when your organization builds or commissions its own app and somebody has to sign it.

Is 299 USD a year worth it compared to 99?

Only if you clear Apple's bar (100 or more employees, the interview, the continuous evaluation) and you genuinely need to ship builds without App Review between them. Otherwise the 99 dollar membership with Custom Apps gives you private distribution, silent installs and license management for less money and less obligation.

What happens to our internal apps if the membership lapses?

Public and custom listings come off the store, so nobody new can install. Apps already on devices keep running until their provisioning profile expires, then they stop launching. Renewing after the fact doesn't bring a lapsed build back to life: you rebuild and redistribute.

If you're choosing a route right now, the short version is this: enroll as an organization on the 99 dollar membership, publish your internal app as a Custom App, and distribute it through MDM. Reserve the Enterprise Program for the rare case where App Review genuinely blocks you, and put the profile expiry date in a shared calendar before you forget.