New — Try passkeys in your browser

Your passkeys,
bound to silicon.

Titanium Passkey is an offline credential provider for iPhone, iPad, and Mac. Private keys live in the Secure Enclave, gated by Face ID or Touch ID. No cloud. No sync. No account. Just signatures that never leave the device.

Get on App Store See how it works
iOS 17 · iPadOS 17 · macOS 14 Secure Enclave Zero telemetry
Built on silicon

Designed around the Secure Enclave.

Every passkey is a P-256 key pair generated inside Apple’s dedicated security coprocessor. The private half can never be exported — not by us, not by iOS, not by you.

Biometric gating

Every assertion is gated by Face ID or Touch ID — no passcode fallback. SecAccessControl enforces it at the hardware level, not a checkbox in software.

Secure Enclave keys

EC P-256 keys created with kSecAttrTokenIDSecureEnclave. Signatures happen on-chip. Private key material never touches RAM accessible to iOS.

Zero network

No backend. No telemetry. No analytics. The Credential Provider extension — the process that touches every passkey — ships without a network entitlement. Nothing to exfiltrate, even if we wanted to.

WebAuthn native

Standard ES256 (COSE alg -7) over WebAuthn. Works with every passkey-capable site — GitHub, Google, your bank, your self-hosted app.

AutoFill integration

Registers as a Credential Provider via AuthenticationServices. Sign-in sheets appear natively in Safari and every iOS app that speaks WebAuthn.

No vendor lock-in

Delete the app and the keys go with it — exactly as they should. Nothing to cancel, no backups to shred, no account to close.

WebAuthn Level 3

More than the baseline.

Most authenticators implement the core create and get operations and stop there. Titanium Passkey goes further — so the sites that care about modern passkey UX can use it.

Fast authentication

When exactly one passkey matches the request, skip the picker. Face ID or Touch ID fires immediately — one glance and you’re in. Turn it off if you prefer explicit confirmation.

Conditional mediation

Sites that ask for passkeys through the conditional UI flow get offered a matching credential inline, without interrupting the password field. Native support, no shims.

Silent registration

Upgrade a password login to a passkey in the background while the user signs in. iOS’s SupportsConditionalPasskeyRegistration flag is on — sites that opt in get seamless upgrades.

PRF extension

The prf extension (WebAuthn’s hmac-secret) is fully supported. Web apps that bind encrypted data to a passkey — e.g. E2EE document apps — get deterministic, per-site secrets derived in the Secure Enclave.

Optional iCloud tier

The default tier is silicon-bound, single-device. If you want a specific credential to sync through iCloud Keychain instead, flip it on per-passkey. The trade-off is explained in-app, not hidden in settings.

Hybrid transport

Sign in from any desktop — Windows, macOS, Linux, Chromebook — without a passkey manager installed there. On the browser’s passkey prompt pick “Use a Device Nearby” / “Other Options”, scan the QR code, approve with Face ID or Touch ID on your iPhone. Over Bluetooth, the way Apple’s spec intends.

The flow

From tap to signature.

iOS routes WebAuthn requests to the Credential Provider extension. Titanium Passkey responds — or stays out of the way.

Step 01

Site requests a passkey

A website or app issues a WebAuthn challenge. iOS surfaces enrolled providers.

Step 02

You pick Titanium

Select Titanium Passkey from the AutoFill sheet. The extension wakes up in-process.

Step 03

Biometrics gate the key

Face ID or Touch ID unlocks the private key inside the Secure Enclave. One glance.

Step 04

Signed. Done.

The assertion is signed on-chip and handed back to iOS. You’re in. No round-trips.

Context

Three ways to hold a passkey.

There are three rough schools of passkey storage. Each trades something different away. Titanium Passkey is built for the threat model the other two don’t fully cover — theft of the device itself.

Cloud-synced

iCloud Keychain · Google · Microsoft

  • Private keys replicate through vendor clouds
  • Recovery is tied to a vendor account
  • Metadata crosses the network whether you notice or not
  • Convenient across all your devices

Hardware tokens

YubiKey · Titan · SoloKey

  • Keys stay on the token — no cloud
  • Most are possession-only by default — a stolen token is a usable token
  • A PIN, if set, is a knowledge factor — shoulder-surfable, and once entered unlocks every credential on the token
  • Separate object to carry, lose, or forget

Titanium Passkey

Secure Enclave · biometric-gated

  • The key can’t be copied. Locked inside the security chip Apple made for this. Not even we can reach it.
  • The key can’t be used without you. Every sign-in needs your face or fingerprint — at the moment it happens. A stolen phone signs nothing.
  • Nothing to carry. The security chip is already in your pocket.
  • Changing biometrics wipes the keys. No quiet way to hand over access.

YubiKey Bio and similar models do add on-device fingerprint verification — they’re closer to what we do, but the sensor is tiny, fingerprint-only, and newer. Face ID adds depth and liveness detection that a capacitive pad on a USB token can’t match. Titanium Passkey rides on hardware that’s had a decade of anti-spoof work baked in.

Privacy by construction

Most password managers are built around sync.
We built this one around the opposite idea.

Design thesis
Technical

Under the hood.

For the engineers.

Platform iOS 17.0+ · iPadOS 17.0+ · macOS 14.0+
Key type EC P-256, ES256 (COSE -7)
Storage Keychain · kSecClassKey + metadata
Access control biometryCurrentSet + privateKeyUsage
Integration AutoFill Credential Provider · AuthenticationServices
Attestation none — privacy-preserving
Scope Device-bound by default · optional iCloud Keychain tier
Built with Swift 6 · The Composable Architecture 1.25 · Apple CryptoKit

Passkeys. Without the cloud.

Titanium Passkey is in development. Follow along for the App Store release.

Get the app Contact us