Instead, I asked them to break it.
That changed everything.
Over the last few months, I've been building ATLOCK v4, a local-first Windows security suite.
I could write another post listing features.
Or I could ask something much more interesting.
If you had 10 minutes...
What would you try first to break a security application?
Would you test the password vault?
Try bypassing file protection?
Look for weak permissions?
Stress test the interface?
That's exactly the kind of feedback I'm looking for.
ATLOCK currently includes
🔒 NTFS-based File Protection
🔐 Encrypted Password Vault
📸 Intruder Ops (Webcam Photo & Video Capture)
🖥️ Desktop Lockdown
📋 Local Security Logs
Akhouri Systems has now crossed 500+ downloads, but I'd rather have 50 honest reviews than another 500 silent installs.
So here's my challenge to the Dev.to community:
👉 Download ATLOCK.
👉 Try to find something wrong.
👉 Tell me what you'd improve.
Whether it's the UI, workflow, usability, or security model—I genuinely want the criticism.
Every serious security product gets better because people question it.
Maybe you'll find something I've missed.
GitHub:
https://github.com/Akhouri-Anmol-Kumar/ATLOCK
Question for you:
What's the first thing you check before trusting a brand-new security application?
I'd love to hear your perspective.
"We Build What Others Forgot To Fix"
Top comments (1)
Sometimes a fresh angle is all it takes to see something new.👍️