Use case · Creative apps
Licensing for creative apps
Editors, design tools, and audio software get used on planes, in studios, and across two or three machines. Their licensing must never break the creative flow.
Start FreeFor developers of creative Mac software — photo and video editors, design tools, audio and music apps, illustration software — sold directly to artists and studios.
- Creative work happens offline — on planes, on location, in studios with no internet by design.
- Artists routinely work across a desktop and a laptop and expect one license to cover both.
- A licensing prompt that interrupts a render or a recording session is unacceptable.
Updated March 2026
Creative software is used in a particular way, and that way is unkind to most licensing schemes. Artists work offline, work across multiple machines, and work in long uninterrupted sessions. A licensing model that ignores any of those will, sooner or later, break someone’s flow at the worst possible moment. This page covers how to license a creative Mac app so it never does.
Creative work happens offline
A photographer culls a shoot on a laptop on the flight home. A video editor cuts on location with no connectivity. A music producer works in a studio that is air-gapped on purpose, to keep a noisy network out of the signal chain. Offline is not an edge case for creative software — it is a normal working condition.
An app that can only validate its license through a server call has no good answer in any of those situations. It either refuses to run — locking out an artist who paid, mid-session, through no fault of their own — or it runs without a real check, which means the check was never enforcing anything. Neither is acceptable.
Offline license validation removes that failure entirely. The license is a signed key — the app ships with a public key and verifies the signature locally, in memory, with no network call. The app launches and unlocks instantly whether the machine is online or not. A periodic background revalidation picks up revocations when a connection is available, but it never gates the app from running.
Sessions must not be interrupted
The second hard rule of creative software: do not interrupt a working session. A render is in progress. A multi-track recording is live. A long export is running. A modal “verifying your license…” dialog, or worse a “could not validate” error, in the middle of any of that is unacceptable — and for some sessions, genuinely costly.
Signed-key licensing respects this because the only license work that happens is a local signature check at launch. There is no per-action validation, no mid-session call home. Revalidation against the server is a background task scheduled across launches; it has no UI, blocks nothing, and degrades silently when the machine is offline. From the artist’s perspective, after the app opens, licensing has simply ceased to exist — which is exactly correct.
One artist, several machines
Creative professionals rarely work on a single computer. The common setup is a powerful studio desktop and a portable laptop, sometimes a third machine. An artist who buys your app expects one purchase to cover the way they actually work.
A licensing layer handles this with a device activation limit. Set it to two or three for a standard license and the artist activates the app on their desktop and their laptop under one key; the activation system tracks the devices, and a self-service portal lets them swap a machine out when they upgrade hardware. A studio license can carry a higher limit for a shared team of artists.
The limit still does its job — it stops one key being shared across an unrelated group — but a generous limit plus easy self-service means a legitimate multi-machine artist never feels it. For creative customers in particular, a stingy one-device license reads as hostility; a sensible multi-device default reads as understanding how they work.
Doing it with Keylight
Keylight issues each license as an Ed25519-signed lease your creative app verifies locally. A Stripe payment mints and delivers the license automatically; you set the device limit per tier. The Mac SDK is the same checkOnLaunch() and state model used across all Apple-platform apps:
import KeylightSDK
await licensing.checkOnLaunch()
switch licensing.state {
case .licensed:
enableCreativeFeatures()
case .trial(let daysLeft):
showTrialBanner(daysLeft: daysLeft)
case .expired:
showRenewalPrompt()
case .invalid:
showActivationSheet()
}
checkOnLaunch() verifies the cached signed lease locally — instant, offline — and revalidates in the background only when due and only when connected. The artist’s session is never the thing waiting on the network.
License creative software the way artists work: offline by default, never interrupting a session, generous across the two or three machines they actually use. See offline license validation for the verification model, device activations for multi-machine licenses, and Pricing — from $19/month with a free tier.
Frequently asked
How should I license a creative Mac app?+
With a signed key verified offline. Creative work frequently happens with no internet, so the app must confirm its license locally and never block a working session on a network call.
Can one license cover an artist's desktop and laptop?+
Yes. A license carries a device activation limit. Setting it to two or more lets an artist run the app on a studio desktop and a travelling laptop under one purchase.
Will license validation interrupt a render or recording?+
No. Validation is a local signature check that happens at launch. Revalidation is a background task that never blocks the UI or an in-progress session.
Start licensing your app today
Drop in the Swift SDK, point it at your dashboard, and sell paid apps in under a minute. Free forever tier included.
Start Free