What if the next major security upgrade wasn't built just by a developer—but also by the people who challenged the previous version?
I'm building ATLOCK v5.
But before taking the next step, I want to put the current flagship, ATLOCK v4.0, through a serious round of community testing.
And I'm not looking for people who will simply download it, open it once, and forget about it.
I want people who will actually explore it, test its limits, identify bugs, and tell me what needs improvement.
Because real feedback matters more than empty praise.
🔒 MEET ATLOCK v4.0
ATLOCK is a Windows-focused security suite developed under Akhouri Systems.
Its current feature set includes:
🛡️ LOCKDOWN — System lock functionality with a countdown.
📁 FILE GUARD — Windows NTFS ACL-based file protection.
🔐 PASSWORD VAULT — A password-protected vault using Fernet encryption.
📸 INTRUDER OPS — Configurable camera capture, short video recording, and security alerts.
⚙️ SETTINGS — Controls for supported security features.
ATLOCK v4.0 is available now.
But the next chapter is already being built.
🧪 YOUR MISSION: TEST ATLOCK v4
I want you to approach ATLOCK like a tester, not just a customer.
Try the available features.
Explore the interface.
Test different workflows.
Look for unexpected behavior.
And if something breaks, document it.
Here are some areas worth investigating:
🔍 1. Stability testing
- Does the application behave consistently during normal use?
- Are there unexpected crashes or freezes?
- Do you encounter errors during repeated operations?
📂 2. File Guard testing
- Do supported file-protection operations behave as expected?
- Are there unusual edge cases involving file access?
- Does the application communicate errors clearly?
🔑 3. Password Vault testing
- Do normal vault operations work consistently?
- Are incorrect credentials handled appropriately?
- Are there unexpected failures during repeated operations?
⚙️ 4. Interface and usability
- Are any controls confusing?
- Are error messages understandable?
- Which workflows need improvement?
📋 5. Feature requests
- What functionality is missing?
- What would make the application more practical?
- What should receive attention in the next version?
🚀 ATLOCK v5 — THE NEXT CHAPTER
Now, let's talk about what's coming.
ATLOCK v5 is currently in development, with approximately 70% of the development work completed.
I'm not revealing the entire implementation. The development code stays private.
But here's a glimpse of the direction.
⚡ A rebuilt foundation
The v5 codebase includes a rebuilt cryptographic, storage, and anti-tamper core beneath the existing interface.
🔐 A more structured security architecture
The new implementation includes authenticated encryption, protected local state, and additional integrity-related mechanisms.
🛠️ A focus on hardening
The development work includes defensive measures intended to improve resistance to certain forms of tampering and reduce the impact of common failure scenarios.
These mechanisms have limitations. They are not a guarantee against a determined attacker with control of the same Windows account or machine.
And that's exactly why testing, feedback, and security review matter.
This is a glimpse, not the complete v5 feature list. More details will be revealed when the relevant development work is ready to be discussed.
🧠 WHY I'M ASKING YOU TO TEST v4
Here's the reality of software development:
A developer can test an application repeatedly and still miss problems that appear when other people use it differently.
Different machines. Different configurations. Different workflows. Different expectations.
That's why I want feedback from people outside my own development environment.
Your findings can help identify problems that deserve attention as ATLOCK evolves.
I cannot promise that every reported issue will be fixed or that every suggestion will make it into v5.
But constructive, reproducible feedback gives me something concrete to investigate.
📥 READY TO TEST ATLOCK v4.0?
Download ATLOCK v4.0
Explore the source repository
💬 FOUND SOMETHING?
If you discover a bug, unexpected behavior, or a potential security issue:
- Describe what happened.
- Explain the steps that led to it.
- Include your Windows version and relevant error messages.
- Share your findings through the project's GitHub repository.
For security-sensitive findings, avoid publishing exploit details or sensitive information publicly. Report them responsibly.
THE BOTTOM LINE
ATLOCK v4.0 is the current flagship.
ATLOCK v5.0 is the next major development milestone.
And right now, I want to learn what v4 does well, where it struggles, and what deserves improvement.
Don't download ATLOCK just to tell me it's great.
Download it. Test it. Challenge it. Report what you find.
Because the goal isn't simply to release another version.
The goal is to keep improving the software.
🔒 ATLOCK — An Akhouri Systems Product
Built by Akhouri Anmol Kumar.
Top comments (0)