I didn't build ATLOCK because I thought Windows needed another random utility.
I built it because I wanted to experiment with something different:
How much useful desktop security can you put into one local-first application?
Today, reached 532 downloads.
That's a small number compared with established software.
But for an independently built Windows application, every download means someone decided:
"I'll give this a try."
And that's the part that matters to me.
What is ATLOCK?
ATLOCK v4 currently brings several security functions together:
🔒 NTFS-based File Protection
🔐 Local encrypted Password Vault
📸 Intruder Ops
🖥️ Desktop Lockdown
🔔 Local security notifications
⚙️ Configurable security settings
The password vault uses Fernet with PBKDF2-HMAC-SHA256 for key derivation.
The application is designed around a local-first approach, without requiring a mandatory account or cloud service.
But here's what I actually need now
I don't need another person telling me:
"Nice project."
I need Windows users to download it and actually use it.
Try the File Protection.
Open the Password Vault.
Look through the settings.
Test the workflow.
Then tell me what you don't like.
Because criticism from someone who actually used the software is worth far more than another compliment.
🔒 Try ATLOCK v4
GitHub:
https://github.com/Akhouri-Anmol-Kumar/ATLOCK
If you download it, I'd genuinely like to know:
What was the first feature you tested?
532 downloads so far.
Let's see what happens when more Windows users actually put it through its paces.
"We Build What Others Forgot To Fix"
Top comments (1)
Fernet with PBKDF2-HMAC-SHA256 is a solid, boring choice for the vault, boring is exactly right for encryption. Worth being explicit about the KDF iteration count, since that's what actually determines brute-force resistance if the vault file leaks.
"Criticism from someone who used it beats a compliment" is the right ask, harder to get too, since it means someone trusting real files to it, not just leaving a comment.
If I downloaded it, File Protection is what I'd test first, a vault failing just loses saved passwords, but file protection failing silently on real files is a different category of risk.