Clavem

How to sell Mac apps outside the App Store

You can sell a Mac app from your own website with an Apple Developer ID certificate, notarization, a payment processor, and your own license and update system. The Mac App Store takes 15% to 30% and handles payment, tax and updates for you. Direct sales keep more of each sale and move that work to you.

Three ways to get a Mac app to buyers

Mac App Store Direct with Developer ID Third-party store
Who takes payment Apple You, through a processor such as Stripe The store
Commission 30%, or 15% under the Small Business Program Processor fees only Set by the store
License keys Not allowed Yours to design Handled by the store
Updates Mac App Store only Your own mechanism Handled by the store
Review App Review before each release None, but you must notarize Store’s own review
Sandbox Required Optional Varies

The Mac App Store column comes from Apple’s pages. The commission is 30 percent of sales of digital goods, or 15 percent for developers in the Small Business Program, which Apple opens to developers with up to 1 million USD in proceeds in the prior calendar year. Guideline 2.4.5 requires apps to be sandboxed, to use the Mac App Store for updates, and not to “present a license screen at launch, require license keys, or implement their own copy protection”. Guideline 3.1.1 requires Apple’s in-app purchase for anything that switches on paid features.

The third column varies. Setapp’s developer page, for one, lists revenue-share models labelled 70/30, 75/15 and 75/25 and says it handles activation, licensing, billing, taxes and support. Read the store’s terms for what each split means. A store like that trades a share of revenue for distribution and for work you would otherwise do.

The rest of this article is about the middle column.

What direct distribution requires

  1. Apple Developer Program membership. Apple lists it at 99 USD per membership year. Only the Account Holder can create the Developer ID certificate.
  2. A Developer ID signature. Apple’s page says Gatekeeper checks for it on apps distributed outside the Mac App Store.
  3. Notarization. Apple’s support page says macOS Catalina and later requires notarized software by default. The commands and the error table are in how to notarize a Mac app.
  4. A way to take payment. Stripe Checkout or a Payment Link is the usual start. See how to sell software online with Stripe.
  5. Licensing. Something has to create keys, limit devices and answer your app.
  6. Updates. Sparkle is an open-source update framework for macOS apps. Its documentation says it reads an appcast, an RSS feed you host, compares CFBundleVersion values, and expects update archives signed with an EdDSA key. You can instead check your own release endpoint at launch.
  7. Tax. When you sell direct, you are the seller. See tax basics for indie software sellers.

What buyers see if you skip steps

If an app is unsigned or not notarized, macOS blocks it on first launch. Apple’s support page describes the override: open System Settings, choose Privacy and Security, scroll to the message about the app and press Open Anyway. That is a path for a user who trusts the source, and it is a conversion problem for a seller. Notarize every release.

A worked comparison: one $49 app

The numbers below use stated assumptions so you can swap your own. Taxes, refunds, chargebacks and currency conversion are left out.

  • Price: $49.00 per sale, one-time.
  • Mac App Store: 30% commission, or 15% in the Small Business Program.
  • Direct: card fee of 2.9% plus $0.30 per sale. That is an assumption based on the common US card rate. Stripe’s pricing page shows rates for your own country, and international cards and currency conversion cost more.
  • Direct with a merchant of record: Stripe Managed Payments adds 3.5% per successful transaction on top of payment fees, according to Stripe’s pricing page. In return Stripe handles sales tax, VAT and GST, disputes and invoicing for you.
Route Fee per sale You keep per sale 100 sales a month 500 sales a month
Mac App Store, 30% $14.70 $34.30 $3,430.00 $17,150.00
Mac App Store, 15% $7.35 $41.65 $4,165.00 $20,825.00
Direct, Stripe card fees $1.72 $47.28 $4,727.90 $23,639.50
Direct, Stripe plus Managed Payments $3.44 $45.56 $4,556.40 $22,782.00

Selling direct with card fees only keeps $5.63 more per sale than the 15 percent App Store tier, and $12.98 more than the 30 percent tier. Two caveats matter more than the arithmetic.

First, the direct rows cost nothing for discovery. The Mac App Store puts your app in front of people who are already browsing for apps. Selling direct, you bring the traffic. If your launch depends on store search, the commission may be cheaper than the audience you would otherwise buy.

Second, the direct rows leave out the work. Licensing, update hosting, tax and refund handling are yours. A licensing service costs money too: with Clavem’s Indie plan at $29 a month, 100 sales a month leave $4,698.90 in the direct row. That is still ahead of both Mac App Store rows, but the gap shrinks at low volume. At 10 sales a month the direct route keeps $472.79 before the $29 and $443.79 after, against $416.50 for the 15 percent tier, so the fixed cost cuts the advantage to $27.29. Below about six sales a month, the 15 percent tier comes out ahead. A fixed monthly fee only pays off once volume covers it, and the free plan’s 50 active licenses cost nothing while you find out.

Licensing and updates for a direct Mac app

The flow is the same for any direct app. A Stripe payment creates a license key. The buyer enters it in the app. The app activates a device once, then validates at launch.

With Clavem, the app calls the License API with no secret in the binary. This Swift code ran against the public demo license:

struct Validation: Decodable {
    let valid: Bool
    let error: String?
    let token: String?
}

func validate(licenseKey: String) async throws -> Validation {
    var request = URLRequest(url: URL(string: "https://clavem.io/v1/licenses/validate")!)
    request.httpMethod = "POST"
    request.setValue("application/json", forHTTPHeaderField: "Content-Type")
    request.httpBody = try JSONEncoder().encode(["license_key": licenseKey])
    request.timeoutInterval = 8
    let (data, _) = try await URLSession.shared.data(for: request)
    return try JSONDecoder().decode(Validation.self, from: data)
}

It printed valid: true error: none token prefix: sgt1.. The token is an Ed25519-signed statement your app can verify offline with CryptoKit. The verification code is on the offline verification page, together with the claims to check (pid, valid, exp, refresh_by).

Two Mac-specific details are worth deciding early:

  • Fingerprint. Send a hash of a stable machine identifier as fingerprint when you activate. Activating again on the same Mac then returns the same seat instead of using a second one.
  • Offline behavior. The token’s refresh_by is 14 days after it was issued. Validate online at launch. If the network is down, trust the stored token while it is fresh, and ask the user to connect once it is stale.

When the Mac App Store is the better choice

Pick the store if you want Apple’s discovery and family features, you prefer that Apple handles tax and payments entirely, and your app fits inside the sandbox. Pick it too if you are happy with in-app purchase for paid features, because license keys are not allowed there. If your app needs capabilities outside the sandbox, such as broad file access or a helper that runs with higher privileges, direct distribution may be your only option.

Many apps do both, with a store build that uses in-app purchase and a direct build that uses license keys.

Doing this with Clavem

Clavem covers the licensing and delivery steps of the direct route, not signing, notarization or tax. After a Stripe payment it creates the key, emails the buyer an order page with the download, limits the number of devices, and answers your app’s validate calls. A free plan covers 50 active licenses, and paid plans start at $29 a month with no cut of your sales. Clavem is not a merchant of record. If you want tax handled for you, that is a Stripe Managed Payments decision, and Clavem works the same either way. Start with the quickstart and the Stripe guide.

Questions

Do I need the 99 dollar Apple Developer Program to sell outside the App Store?

In practice yes. Apple's Developer ID page says the Account Holder of a team in the Apple Developer Program generates the Developer ID certificate, and Gatekeeper checks for that certificate. Apple lists the membership at 99 USD per year.

Can the same app be in the Mac App Store and sold directly?

Yes, usually as two builds. Apple's guidelines forbid license keys and non-App Store updates in Mac App Store apps, so the license check and the update mechanism belong only in the direct build.

What happens if I skip notarization?

macOS shows a warning and blocks the first launch. The user can approve the app in System Settings, under Privacy and Security, with the Open Anyway button, but most buyers will not.

Sources

  1. Apple Developer Program membership details, fees and commission (as of November 2026)
  2. Apple App Store Small Business Program (as of November 2026)
  3. Apple App Review Guidelines, sections 2.4.5 and 3.1.1 (as of November 2026)
  4. Apple, Signing Mac software with Developer ID (as of November 2026)
  5. Apple Support, Safely open apps on your Mac (as of November 2026)
  6. Sparkle documentation (as of November 2026)
  7. Setapp for developers (as of November 2026)
  8. Stripe pricing, Managed Payments rate (as of November 2026)