A few months ago, I had a simple idea:
What if I could put several useful Windows security tools into one portable application?
Not another complicated enterprise dashboard.
Not another app that requires an account before you can even use it.
Just a Windows application you can download, open, configure, and use.
That idea became ATLOCK.
And today, I'm working on ATLOCK v4. 🚀
🛡️ So... What Does ATLOCK Actually Do?
ATLOCK brings several security-focused features together:
🔒 System Lockdown
Protect your workstation when you need to step away.
🛡️ NTFS/ACL File Protection
Use Windows' own filesystem permission system to control access to protected files.
🔑 Local Password Vault
Keep credentials encrypted locally instead of requiring a cloud account.
📸 Intruder Ops
Respond to repeated unauthorized access attempts with configurable local security actions.
🔔 Security Alerts
Get notified when important security events happen.
⚙️ Portable
No complicated installation workflow. Download it and run it.
💡 But The Feature List Isn't The Interesting Part
The part I'm most proud of is the philosophy behind it.
I wanted ATLOCK to be local-first.
That means asking:
Does this feature actually need my data to leave my computer?
If the answer is no, why make it leave?
That's why the core application doesn't depend on a cloud backend just to provide its basic security functionality.
🔐 Security Isn't Just About Encryption
Building ATLOCK also changed the way I think about security.
At first, it's tempting to think:
“Add encryption → problem solved.”
But then you start asking questions.
Where does the key come from?
Where does sensitive data live?
Who can access it?
What happens when something fails?
What happens when intrusion detection gets something wrong?
What happens to captured evidence?
Suddenly, security becomes much bigger than a cryptographic algorithm.
And honestly...
that's what made this project fun.
🧪 I Also Learned To Respect Windows
One of my favorite decisions was using NTFS/ACLs instead of trying to invent my own filesystem permission system.
Windows already has a security model.
Why rebuild something the operating system already knows how to enforce?
Sometimes good engineering isn't about building more.
It's about knowing what not to build.
📸 And Then There Was Intruder Ops...
This feature caused some of the most interesting engineering problems.
Webcam hardware isn't exactly predictable.
Sometimes a camera initializes instantly.
Sometimes another application is already using it.
Sometimes hardware behaves differently across machines.
And suddenly your “simple webcam feature” becomes a lesson in asynchronous operations, failure handling, and privacy.
It also raised an important question:
If security software captures evidence, how do you protect the evidence itself?
That's something I'm continuing to think about as ATLOCK evolves.
🚀 ATLOCK v4 Is Still Growing
I'm not pretending ATLOCK is the ultimate Windows security solution.
It isn't.
It's an independent project I'm building, testing, breaking, and improving.
And I'd rather have people tell me:
“This part could be better.”
than simply:
“Looks cool.”
Because that's how the next version gets better.
👀 Want to Try It?
If you're on Windows and interested in privacy-focused desktop software, I'd love for you to test it.
🔒 Try ATLOCK v4 → [https://github.com/Akhouri-Anmol-Kumar/ATLOCK]
Use it.
Break it.
Question it.
And tell me what you'd add.
What is the ONE security feature you wish Windows had built into it by default?
ATLOCK
"We Build What Others Forgot To Fix"
Top comments (0)