Skip to content
jimmylabs

Security

Secure fromthe first commit.

Not bolted on at the end.

01 / 03

Encrypted end-to-end.

TLS 1.3 on the wire, authenticated encryption on disk.

02 / 03

GDPR & PIPA by default.

Personal data handled by the rules, from day one.

03 / 03

Tested before every release.

We try to break it before anyone else can.

The quantum era

Harvest now,decrypt later.

Today’s encryption will not last. Anything recorded now can be read once a big enough quantum computer exists.

What breaks

RSA
Broken by Shor’s algorithm
Elliptic curve
Broken the same way
Diffie–Hellman
The key exchange is exposed
AES · SHA
Weakened, not broken

How we prepare

Swappable algorithms
Change them without rebuilding the app
Following the NIST standards
ML-KEM for key exchange, ML-DSA for signatures
Hybrid key exchange
Old and new algorithms together, so nothing gets weaker
Bigger keys
AES-256 and SHA-384 keep a wide margin

The regulatory clock

The deadlines are already set. Where do you stand?

You are here
  1. 2027CNSA 2.0 procurement gateNew national-security purchases must be post-quantum by default.
  2. 2030RSA & ECC deprecatedRSA-2048 and P-256 allowed only with a written risk sign-off.
  3. Written risk sign-off required · 2030–2035
  4. 2033CNSA 2.0 phase-out completeNational-security systems finish migrating.
  5. 2035DisallowedThe old algorithms are removed from the standards.

The standards are final

  • ML-KEMFIPS 203Final
  • ML-DSAFIPS 204Final
  • SLH-DSAFIPS 205Final
  • HQCBackup KEM · selected 2025Pending
  • FN-DSAFIPS 206 · draftPending

NIST IR 8547 · NSA CNSA 2.0

Built, not borrowed

We write the standard algorithms ourselves, in Rust, and check them against the official KCAVP test vectors. The code is public.

See the modules

Our lab is measuring how far AI can push attacks on this kind of crypto.

See the discovery

Day to day

Least privilege

Every part gets only the access it needs.

Secrets stay secret

Keys and passwords never live in the code.

Dependencies watched

Third-party packages are scanned before release.

Reviewed before merge

Every change gets a second look before it goes in.

Less data

We only collect what a feature needs.

Logged

Sensitive actions are logged, so odd ones can be traced.

Need to meet a standard?

Talk to us