Most Windows security apps promise one thing.
"Lock your files."
I wanted to build something that thought beyond that.
So instead of asking,
"How do I lock a file?"
I asked,
"How do I make someone regret touching my PC?"
Traditional Security
🔐 Lock File
│
▼
Done.
ATLOCK Philosophy
🔒 Protect Files
+
📸 Detect Intruders
+
🎥 Capture Evidence
+
🔑 Secure Credentials
+
⚠️ Record Security Events
+
🛡 Desktop Lockdown
Security Isn't One Feature.
It's an ecosystem.
While building ATLOCK, I didn't want separate applications for every task.
I wanted one desktop application that could combine multiple protection layers.
🔒 File Guard
Uses Windows NTFS permissions to help protect selected files from unauthorised access.
🔑 Password Vault
Sensitive information is stored locally using authenticated encryption with strong password-based key derivation.
📸 Intruder Ops
Repeated failed authentication attempts can trigger webcam photos, video recording and audible alerts.
🔔 Security Notifications
Security-related events are logged locally so users can review activity later.
🛡 System Lockdown
A dedicated desktop lockdown mode designed to reduce unwanted interaction while the system is locked.
Someone Opens Your Laptop
│
▼
Windows Login
│
▼
ATLOCK Starts Protecting
🔒 File Guard
📸 Intruder Ops
🔑 Password Vault
🔔 Security Logs
🛡 Lockdown
Why I Built It
I wasn't trying to replace BitLocker.
I wasn't trying to replace VeraCrypt.
I wasn't trying to replace KeePass.
Those are excellent tools built for different jobs.
ATLOCK was built to become another layer in a Windows security strategy.
Because the strongest defence isn't one application.
It's multiple layers working together.
One Goal
When someone interacts with your computer...
I want security to be visible.
Not after the damage.
Before it.
Building ATLOCK has taught me one thing:
Good security isn't about making impossible promises.
It's about making attackers work harder.
And that's a challenge worth engineering for.
If you were designing a Windows security application today, what feature would you build first?
Try & Test ATLOCK beyond it's limit: https://github.com/Akhouri-Anmol-Kumar/ATLOCK
Direct Download Link(ATLOCK):https://github.com/Akhouri-Anmol-Kumar/ATLOCK/releases/download/v4.0/ATLOCK.zip
"We Build What Others Forgot To Fix"
Top comments (3)
Solid build. 👊
You didn't just build a file locker — you actually thought about the full loop: detect, capture, lock, log. Most people don't get that far on a first try.
Quick question — how'd you handle the webcam part? DirectShow or MediaCapture API? Ran into a few weird edge cases with camera access myself, wondering what route you took.
One thought: if you ever rewrite this, try opening with a real scenario — like "a friend's laptop got stolen" or something. Walk through what ATLOCK does when that happens. Stories hit harder than feature lists. Just a thought. 👊
Thanks a lot xulingfeng bro.
Really appreciate you taking the time to read it and leave such thoughtful feedback. 👊
For the camera, I went with OpenCV using the DirectShow backend (
cv2.CAP_DSHOW) on Windows rather than the MediaCapture API. It gave me more predictable open/release behaviour for what I was trying to achieve.The annoying part wasn't capturing a frame.....
it was dealing with all the little edge cases.
I ended up warming the camera up for a few frames because the first image was often too dark, handling cases where the camera wasn't available, running photo/video capture in a separate thread so the UI stayed responsive, and making sure everything was released cleanly afterwards.
And I really like your suggestion about the article.
You're right—I focused too much on the features. A real-world scenario would probably connect with readers much better, so I'll definitely keep that in mind when I update the post.
Thanks again for the feedback. I genuinely appreciate it. 👊
And bro,
keep giving such good suggestions.
Looking forward to your next update! 👊