Skip to main content

Engineering & security research

Inkrypt Security Team

The engineers who build and maintain Inkrypt's encryption layer

The Inkrypt Security Team is the small group of engineers who write, review and maintain the cryptographic code that runs in your browser every time you create a note. Everything published under this byline is written by someone who has worked directly on the code being described.

That constraint is deliberate. A large amount of encryption writing on the web is produced by people who have read specifications but never shipped a key-derivation routine, and it shows: the advice is technically defensible but practically useless, because it omits the trade-offs you only discover when real users hit them. When we write that PBKDF2 at 310,000 iterations takes a noticeable moment on an older phone, it is because we measured it on one.

We write about what we have implemented, benchmarked, or deliberately chosen not to build. Where we are describing something outside that direct experience — a competing product's architecture, a standard we have read but not implemented — we say so in the text and cite the primary source.

Areas of expertise

  • Client-side encryption in the browser
  • Web Crypto API and SubtleCrypto
  • AES-GCM authenticated encryption
  • Password-based key derivation (PBKDF2, Argon2)
  • Zero-knowledge system design
  • Threat modelling for consumer privacy tools

Responsibilities on this site

  • Writes and technically reviews every article touching cryptography
  • Maintains the security architecture and threat model pages against the shipping code
  • Triages inbound vulnerability reports