Product
Cloud-hosted virtual certificates
The problem
Apple code signing needs a certificate and a private key. Keeping that key on every developer Mac
spreads custody risk. Moving signing to a shared HSM without a native Mac path breaks the tools
teams already use — codesign, Xcode, and CI on macOS.
The Liminal Keys model
Liminal Keys publishes the public certificate to the Mac and keeps the
private key non-exportable and software-protected in Key Vault. Hardware security module (HSM) custody is on the roadmap — contact us for more information. When Xcode or codesign asks to
sign, Liminal Keys for Mac sends the digest to the Liminal API, which signs in custody and returns
only the signature.
- No private key export to disk or agent memory as a usable PKCS#12
- Policy, enrollment, and audit live in Liminal Console (Microsoft, Google, and Apple sign-in)
- Sign audit records outcome, identifiers, and SHA-256 digest hash hex (DigestHashHex) — not raw digest bytes, CMS signatures, or private key bytes
Who it is for
Teams that ship macOS or iOS apps and want cloud key custody for signing identities, with a first-class Mac app, Liminal Keys for Mac, rather than a Windows-only or browser-only workflow. The first release is macOS signing only.
Example: WatchTeams
WatchTeams — an iPhone and Apple Watch companion for Microsoft Teams — uses Liminal Keys for release signing. WatchTeams 2.1.0 was archived, signed in GitHub Actions through Liminal Keys CI & automation, and uploaded to TestFlight end to end on 25 Oct 2026. The key never left Key Vault.
Read the WatchTeams customer story →
What you operate day to day
Identities
Import an existing Apple PKCS#12 into non-exportable custody, or generate a key in custody, download a CSR, submit it to Apple, and complete the identity with the issued public certificate. Pending or expired identities never appear on enrolled Macs.
Devices & enrollment
Each Mac enrolls with a short-lived code issued in Console. After enrollment, the host holds a device credential, lists assigned public certificates, and can request signatures. Revoking the device stops signs from that machine on the next request.
Policy rules
A rule answers: which identity may be used for sign, by whom (users, groups, and/or enrolled Macs), and optionally only inside a validity window. On-Mac confirmation prompts are coming soon. You list, add, change, enable/disable, and remove rules as drafts; Apply policy publishes the live set. No matching applied rule means deny. If one applied rule would allow and another would deny the same request, the result is deny.
Sign confirmation on Mac
On-Mac sign confirmation prompts are coming soon. Confirmation will be policy-driven from Console — not a separate app setting. Currently, rules requiring confirmation deny matching signs.
Audit trail
Every allow or deny produces an append-only audit record: tenant, device, certificate identity, outcome, timing, and DigestHashHex (SHA-256 hash of the signed digest). Console shows the first 16 hex characters with copy for the full value. Raw digest bytes, CMS signatures, and key material are not stored. Admins review history in Console.
How signing works on Mac
Install Liminal Keys for Mac. Its virtual smartcard presents virtual certificates to macOS so
you keep using familiar tools — no private key on the machine. After enroll and identity refresh,
select the Liminal virtual identity in codesign or Xcode the same way you would a
local certificate.
What you get
- API — enroll, list certs, sign, and related operations at
api.liminalkeys.com - Console — tenant admin UI at
console.liminalkeys.com - Liminal Keys for Mac — enroll, refresh identities, sign with Xcode and
codesign(confirmation prompts coming soon) - CI & automation — GitHub OIDC trust and ephemeral CI devices from Console; sign in GitHub Actions (CI & pipelines)