A zero-knowledge Vault, engineered like a security product
Your secrets shouldn't need their own separate vendor. Avoryx includes a zero-knowledge credential manager, encrypted in your browser so even we can't read it. Each record has its own encryption, unlocking is gated behind TOTP, you hold the recovery key yourself, and any public share links you create expire on a timer.
Per-record envelope encryption — sharing never re-encrypts the secret.
Each record gets its own random AES-256 data key; the body is encrypted once, and the data key is wrapped per recipient via X25519 → HKDF-SHA256. Sharing a secret with one more person is a single key-wrap — not a re-encryption of the record. Every ciphertext is AAD-bound to its record type and id, so a malicious server can't swap one record's bytes into another. All crypto runs in your browser and funnels through one auditable file.
- Per-record AES-256-GCM body + X25519/HKDF-wrapped data key per recipient
- AAD binds every ciphertext to record type + id (defeats cross-record replay)
- Adaptive Argon2id: benchmarks the device and stores per-user KDF params
- Versioned envelopes so a future FIPS/PQ swap can coexist in the same column
Built with precision — every part of it.
Not a thin feature bolted onto a suite. Here's the real surface area, grouped.
Zero-knowledge core
- Client-side encryption — the server holds only ciphertext, salts and wrapped keys
- Audited primitive set: Argon2id (RFC 9106), AES-256-GCM, X25519, HKDF-SHA256
- Honest posture: NIST-approved primitives, but the JS impl is not FIPS-validated (a one-file swap)
Recovery & unlock
- Downloadable recovery key (base32, dashed groups) shown once — no vendor backdoor
- Master-password change re-wraps only the master envelope; the recovery key still works
- Unlock requires recent TOTP/MFA via a separate HMAC-signed 15-minute unlock token
Generate & check
- CSPRNG password generator with rejection sampling (no modulo bias), class guarantees
- Diceware-style passphrase generator from a 512-word list; two-mode strength meter
- Have-I-Been-Pwned breach check runs client-side via k-anonymity — the password never leaves the browser
Share, attach & automate
- Encrypted file attachments up to 100 MiB in 1 MiB chunks; the filename itself is encrypted
- Public share links: key lives only in the URL fragment; server-clamped TTL (≤24h) & ≤50 views; every probe logged
- Opt-in, per-record KMS path for CI: versioned keys, rotation, and IP-allowlisted, peppered API tokens
Everything 1Password does — plus what only one platform can.
Avoryx is licensed at the platform level — every module is included in one seat, not billed per module. See pricing. Competitor capabilities vary by plan; verified June 2026. Avoryx's Merchant-of-Record and payouts are on the roadmap; SOC 2 Type II is in progress, not certified.
Why one platform wins here.
The server can't read it
Client-side encryption means the platform stores only ciphertext it cannot decrypt — the master key, private key and per-record data keys never leave your browser.
You own recovery
A downloadable recovery key, wrapped separately from your master password, means account recovery without a vendor escrow or backdoor.
A real secrets-automation path
Promote a single record to machine-readable and it's wrapped under a tenant KMS key with versioned rotation and IP-allowlisted, peppered API tokens — a clean, auditable break in zero-knowledge only where you ask for it.
Common questions
Yes — all cryptography runs in your browser and the server stores only ciphertext, salts and wrapped keys it cannot decrypt. The one deliberate exception is the opt-in, per-record KMS path for CI, which you explicitly enable per record.
The rest of the platform
See it on your real numbers.
15 minutes, your stack, your per-seat math, the revenue back-office live.
