Apex
Features How it works Demo Threat model Suite Cryptography FAQ Tools Blog Compare Docs

See it actually work.

§ Live walkthrough

No vault on the laptop. The browser asks; your phone answers. Click the Apex button below and watch a real request travel - encrypted - to the phone, surface as a push, and fill the form only after you approve it with a tap.

Click Sign in with Apex to begin.

Vault never leaves the phone end-to-end encrypted · used once · wiped

Three hops. None readable.

§ Request flow
  1. 01

    Phone holds the vault

    Master phrase derives a key on-device via Argon2id. The vault is sealed with AES-256-GCM. The key lives in memory only while the vault is unlocked.

  2. 02

    Browser asks. Relay forwards.

    The Portal extension detects a login form and sends a request - encrypted to your phone's public key. Relay routes the opaque payload.

  3. 03

    You approve. The form fills.

    Your phone surfaces the request. Biometric approval. The credential travels back encrypted, decrypts in the browser, fills the field, and is wiped.

§ Get the suite

Your secrets, your device, your rules.

Apex is launching in stages. The mobile app and the relay are first. The browser extension and desktop agent follow.

No tracking pixels. No newsletter blast. One email when the apps ship.