Customer story
WatchTeams is a shipping Apple Watch and iPhone client for Microsoft Teams — chat, calls, and notifications on the wrist and phone.
Release signing for TestFlight needs Apple identities, but parking private keys on developer Macs (or sharing a PKCS#12) spreads custody risk across the team.
TestFlight builds shipped with Liminal Keys, including build 1.7.0. Signing keys stayed in cloud HSM custody for the Mac that signed.
Shipping iOS and watchOS builds means code signing with an Apple distribution identity. Keeping that private key on every laptop — or copying a PKCS#12 between machines — creates the custody problem Liminal Keys is built to remove: usable key material on endpoints that do not need it.
WatchTeams release signing uses the standard Liminal Keys path for macOS:
codesign / Xcode request signatures as usual; digests are signed remotely.
WatchTeams published TestFlight releases through this path. Build 1.7.0 is one concrete release signed with Liminal Keys — virtual certificates on the Mac, private key only in cloud custody, Console policy and audit in the loop.
This is a working product reference, not a marketing claim about store rankings or enterprise logos. The point for prospects: real Apple app signing, keys off the laptop.
If you ship Mac, iOS, or watchOS builds and want cloud key custody without abandoning native Apple tooling, WatchTeams is a concrete example of the same model: enroll, apply policy, sign through CryptoTokenKit, keep private keys in custody.