We Built a Phone Upgrade Cycle Into a Security App (S25 → S26, We See You)
Akhouri Systems · ATLOCK Security Suite
Let's talk about "upgrades" for a second.
Samsung drops the S25 Ultra, waits twelve months, slaps in a Snapdragon with a + next to it, adds a "privacy display" that just... dims when someone looks over your shoulder, and calls it the S26 Ultra. Ships it. Charges you full flagship price again.(in fact 15% more price than the launching price of s25 ultra)
And then there's the other guy. A fruit company. Forgot the bite mark was supposed to represent progress somewhere around 2015 and has been shipping the same titanium rectangle with marginally better glass ever since. The bite mark is doing more creative heavy lifting than the actual hardware roadmap at this point.
Meanwhile we've been sitting here at Akhouri Systems rebuilding our entire cryptographic core from scratch for a free desktop security suite, and nobody's even clapping yet. So let's fix that.
What ATLOCK Is
ATLOCK is a single-file, Windows-first, pure-Python security suite — screen lockdown, NTFS-ACL file guarding, an encrypted credential vault, and intruder-capture (photo + video) wired into one app(.exe). No subscription. No cloud. No telemetry phoning home to some VC's dashboard.
v4 is live right now: 👉 Download ATLOCK v4
v5 is done. Fully built. Sitting in the chamber. And it is not a "Gen+ chip and a privacy display" update — it's a ground-up rebuild of everything that actually matters in a security tool: the crypto, the storage format, and the attack surface.
The Technical Part (because talk is cheap)
Here's the actual diff, not marketing copy:
| v4 | v5 | |
|---|---|---|
| Vault encryption | Fernet (AES-128-CBC + HMAC) | AES-256-GCM, authenticated, chunked |
| Key derivation | PBKDF2-HMAC-SHA256, 200k iters | HKDF + hardened key sealing |
| File containers | basic encrypted blob | Container format v3.1 — chunked AES-256-GCM, key commitment, per-chunk subkeys, optional Padme size padding, header-bound AAD |
| 2FA | none | TOTP + FIDO2 hardware key support (YubiKey, WebAuthn) |
| Recovery | — |
Shamir secret sharing (--shamir-split / --shamir-join) — split your recovery key across multiple people/locations, no single point of failure |
| Public-key crypto | — | Full --pk-keygen / --pk-encrypt / --sign / --check-sig pipeline, plus signed-release verification so you can confirm a build actually came from us |
| Anti-rollback | — | HardenedState sealed anchors resist clock/state rollback attacks |
| Self-defense | — |
--selftest, --canary-selftest, --fuzz (stress-tests the container parser against random corruption), --audit-verify
|
| Known v4 weak spot | a documented stealth recovery bypass, flagged openly in the v4 source as a ship-at-your-own-risk tradeoff | gone — rebuilt around FIDO2 + Shamir recovery instead of a hidden master sequence |
| Legacy data | — | v1-v3 containers and v4/v5 JSON vault/guard/settings files are auto-migrated, nothing left behind |
This is what a real upgrade cycle looks like. Not "the same silicon, now 8% faster." A rewritten trust model.
The Pitch
v5 is 100% built, tested, and ready to ship. It is not gated behind more dev time, more testing, more "coming soon" vaporware energy. It's gated behind exactly one number:
Akhouri Systems is at 975 / 1000 total downloads across all products.
v5 unlocks at 1,000.
That's it. That's the whole gate. 25 downloads stand between you and a security suite that out-engineers products made by companies worth more than some countries' GDP.
So here's the move: go grab v4 right now — it's free, it's real, it works — and you personally become one of the 25 people who flip the switch on v5 for everyone.
Discuss
- What's the most embarrassing "flagship upgrade" you've ever paid for?
- FIDO2 vs TOTP vs Shamir recovery — which would you actually trust for a personal vault?
- Anyone want to pressure-test the v5 container format once it's out?
--fuzzis going to need friends.
Drop a comment, drop a download, let's hit four digits. 🔐
— Akhouri Anmol Kumar, Akhouri Systems
Top comments (1)
No Korean & Fruit was harmed in this post.
☠️