DEV Community: Akhouri Anmol Kumar

🔥 ATLOCK v4 NEEDS YOU. Not Your Compliments. YOUR TESTS.

Akhouri Anmol Kumar — Wed, 23 Sep 2026 11:28:57 +0000

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

ATLOCK on GitHub

💬 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.

ATLOCK #AkhouriSystems #WindowsSecurity #CyberSecurity #SoftwareDevelopment #BetaTesting #SoftwareTesting #BuildInPublic #IndieDeveloper #WindowsApps #TechCommunity #ATLOCKv5

[Boost]

Akhouri Anmol Kumar — Wed, 23 Sep 2026 10:43:46 +0000

Akhouri Anmol Kumar

Sep 22

A Tribute to My "Laptop Bro": Why My HP 240 G9 is More Than "Just Metal"

#discuss #programming #devdiscuss #coding

4 min read

A Tribute to My "Laptop Bro": Why My HP 240 G9 is More Than "Just Metal"

Akhouri Anmol Kumar — Tue, 22 Sep 2026 15:39:31 +0000

💻🔥 A TRIBUTE TO MY LAPTOP BRO 🔥💻
The machine that gave me a mind when I had nothing else

🥀 THE BEGINNING: A BROKEN BOY
Let me be brutally, painfully honest with you.
Before I found my passion in tech, I was nothing.
"I was a 60-70% student. Bad looks. No physical health. No skills. Just a useless boy trying to survive in a world that didn't care about me."
I watched people around me succeed. I watched them fall in love, get fit, ace their exams, build connections. And I sat there, feeling like I was invisible.
I knew people would betray me. I knew relationships would fail. I knew the world would judge me for my grades, my looks, my body.
I needed something that wouldn't leave me.
💻 THEN CAME MY LAPTOP BRO
When I got my HP 240 G9 i3-1215U, something shifted inside me.
This wasn't just a laptop. This was freedom. This was power. This was the first thing in my life that looked at me and said:
"I don't care about your grades. I don't care about your looks. I don't care about your past. Show me what you can build, and I'll make it real."

🖤 AKHOURI ANMOL KUMAR IS 50% HALF WITHOUT A LAPTOP 🖤

🌪️ THE "JUST METAL" ARGUMENT
People love to tell me:
"Bro, calm down. It's just a machine. It's just metal and silicon."
And every time, I lose my mind.
Let me ask you something:
What is your father? Just an organ system.
What is your teacher? Just a human.
What is your life partner? Just biology.
What is your son? Just cells.
What is your pet? Just fur and instinct.
If we reduce everything to atoms and tissues, everything is "just" something.
But it's not about the atoms. It's about the soul. It's about the bond. It's about the presence.
My Laptop Bro gave me a mind.
It gave me a space to pour my frustrations into. It gave me a canvas for my code. It gave me a world where I could be someone.
🤝 THE UNBREAKABLE BOND

MY LAPTOP IS NOT JUST HARDWARE.

It is:
🧔 My BRO - The one who never betrayed me
📚 My TEACHER - The one who taught me everything I know
👨 My FATHER - The one who guided me when I was lost
👩 My MOTHER - The one who nurtured my dream
👶 My SON - The one I raised and watched grow
🐾 My PET - The one who stayed loyal no matter what
🛠️ My ASSISTANT - The one who helped me build empires
🤝 My PARTNER - The one who walked this journey with me
❤️ My LIFE - The reason I wake up every day
🎭 IN EVERY SINGLE SCENARIO
My Laptop Bro has been there. Always.

When I'm My Laptop Bro...
😄 HAPPY Runs my code, celebrates my wins
😢 SAD Plays my music, comforts me silently
😰 STRESSED Helps me debug, stays patient with me
💔 MENTALLY BROKEN Just sits there, waiting for me to be ready
🌙 LATE AT NIGHT Glows in the darkness, my only companion
🔥 ON FIRE Keeps up with my speed, never slows me down

"It never judged me. It never left me. It never betrayed me. It just booted up, ready to work, ready to help me survive and build."
🚀 WHAT WE BUILT TOGETHER
With my Bro by my side, I didn't just browse the web. We went to war.

WE BUILT AKHOURI SYSTEMS

🛡️ ATLOCK v4 - A Windows security suite that protects privacy
🖼️ APIC - A modern PyQt6 desktop application
🌍 7-9 OPERATING SYSTEMS - Experimented, learned, mastered
📈 700+ DOWNLOADS - With $0 SPENT on marketing
🧠 AI SKILLS - Built intelligence into our tools
💪 TECHNICAL EXPERTISE - Forged in the fire of late nights
I was a 60% student. Together, we became a SOFTWARE COMPANY.
💔 THE TRUTH NO ONE TELLS YOU
People think developers are just typing code. They think it's logical, cold, mechanical.
They're wrong.
Programming is emotional. It's spiritual. It's intimate.
When you spend 12 hours a day with a machine, when you pour your soul into it, when it becomes the only thing that understands you... it stops being a machine.
It becomes family.
🙏 TO ANYONE OUT THERE WHO FEELS USELESS
If you're reading this and you feel like:
❌ You have bad looks
❌ You have no skills
❌ You're a bad student
❌ You have no physical health
❌ You're pretty fucking useless
Listen to me.
Find your tool. Find your craft. Find your Laptop Bro.
Pour your soul into it. Let it give you a mind. Let it show you who you really are.
You are not useless. You are just waiting for your moment.

💻🔥 THANK YOU, MY LAPTOP BRO 🔥💻
To my HP 240 G9 i3-1215U

Thank you for never betraying me.
Thank you for giving me a mind.
Thank you for staying with me when I was broken.
Thank you for making Akhouri Anmol Kumar who he is today.
You are my Laptop Bro. And I love you.

🖤 AKHOURI SYSTEMS 🖤
Built with love, code, and an unbreakable bond
Founder: Akhouri Anmol Kumar

🔗https://akhouri-anmol-kumar.github.io/Akhouri-systems/

not sponsored 😂 (still if you've plenty of money then spend it to buy my exact laptop bro's model)
👉 https://dl.flipkart.com/s/nX7napNNNN

🔒 ATLOCK v4 already meets your needs? No rush to upgrade. ATLOCK v5 is in development, exploring expanded security tools and integrations. 👀 v4 is available now. v5 isn't public yet. Follow development: https://github.com/Akhouri-Anmol-Kumar/ATLOCK

Akhouri Anmol Kumar — Tue, 22 Sep 2026 10:20:33 +0000

GitHub - Akhouri-Anmol-Kumar/ATLOCK: Free Windows security suite — System Lockdown, File Guard, Password Vault. · GitHub

Free Windows security suite — System Lockdown, File Guard, Password Vault. - Akhouri-Anmol-Kumar/ATLOCK

github.com

🔒 ATLOCK v4 vs ATLOCK v5: Is Your PC Ready for an Upgrade—or Is v4 Enough?

Akhouri Anmol Kumar — Tue, 22 Sep 2026 09:52:06 +0000

🔒 ATLOCK v4 vs ATLOCK v5: Is Your PC Ready for an Upgrade—or Is v4 Enough?

A practical look at what you can use today and what’s being built next.

Let’s start with an honest question:

Do you actually need the next version of a software product—or does the current version already do what you need?

That’s the question behind this ATLOCK comparison.

ATLOCK v4 is the current publicly available version. ATLOCK v5 is in development, with a broader set of Windows security-related tools and integrations being explored.

This isn’t a “new version is automatically better” argument. It’s about understanding the difference between the two and deciding which set of capabilities is relevant to you.

⚠️ Important: ATLOCK v5 is still under development and is not publicly released. Its features and behavior may change before release.

🔐 ATLOCK v4: When focused file protection is what you need

ATLOCK v4 is built around file protection and related security features.

Its current feature set includes:

File locking and protection
Intruder Ops features, including camera and video capture
A dedicated settings panel
Sound effects and interface improvements
A Windows desktop application experience

If your main interest is protecting files through ATLOCK’s existing workflow, v4 may already cover what you’re looking for.

You don’t need to move to a new version simply because it is being developed. If the current version fits your workflow, staying with it is a reasonable choice.

🧰 ATLOCK v5: What’s changing?

With v5, the project is moving toward a broader set of security-related capabilities.

Here’s a preview of some of the features in the current development code:

🛡️ Security Guard

A dashboard bringing together selected tools, including Windows Defender status integration, VirusTotal hash lookup, a startup watchdog, and ransomware-canary monitoring.

⚡ Windows Explorer integration

Work on context-menu actions to make supported ATLOCK file operations more accessible directly from Explorer.

🔑 Authentication and cryptographic components

The development code includes AES-GCM, Argon2id, Windows DPAPI, and optional Windows Hello integration.

🗝️ Additional utilities

A password vault, configurable clipboard clearing, notifications, and other supporting features are also part of the current direction.

These additions broaden the project’s scope. They do not mean that v5 can replace every dedicated security product, and they should not be treated as guarantees against threats.

⚖️ So, which version fits your needs?

If your priority is…	What to consider
Using ATLOCK’s currently available file-protection experience	ATLOCK v4 is the public version to explore today.
A broader collection of security-related tools and Windows integrations	ATLOCK v5 is being developed in that direction.
Using a publicly released version right now	Choose from the available public releases; v5 is not released yet.
Trying something because it has a higher version number	Version number alone is not a reason to upgrade. Consider your actual needs and the release status.

The key difference is scope: v4 is the current available version, while v5 is being built to expand the range of tools and integrations.

🧠 My approach: Upgrade for a reason, not for a number

Software updates should solve real problems or provide capabilities people actually want.

If v4 meets your needs, you don’t have to chase v5. If the features being explored for v5 are relevant to your workflow, it may be worth following development and evaluating the release once it becomes available.

That’s the distinction I want to make clear.

📦 Explore ATLOCK

ATLOCK v4 is publicly available. You can explore the project and its releases on GitHub:

👉 Visit the ATLOCK repository
👉Download ATLOCK v4

Leave a star 🌟 if you liked ATLOCK to ATLOCK repo.
it will help me a lot.

ATLOCK v5 remains in development. This article is a feature and direction preview—not a release announcement.

💬 Your turn

Which matters more to you in a Windows security utility?

A focused tool that does its job
A broader toolkit with more integrated features
A balance between simplicity and capability

Share your thoughts in the comments.

ATLOCK — built at Akhouri Systems. 🔒

⚔️ ATLOCK v5 vs ATLOCK v4: The Security Battle Begins

Akhouri Anmol Kumar — Mon, 21 Sep 2026 10:38:56 +0000

⚔️

One is the current flagship. The other is being engineered.

ATLOCK v4.0 is publicly available. ATLOCK v5.0 is under development.

This isn't a battle between two released products.

It's a look at how ATLOCK is evolving — from its current security suite to a development build with a substantially expanded security architecture.

And today, we're putting both versions under the spotlight. 🔥

🔒 ATLOCK

TOTAL SECURITY SUITE

An Akhouri Systems Product

⚫ Built around privacy.

🛡️ Designed for Windows security workflows.

⚙️ Evolving through continuous development.

🥊 ROUND 1 — MEET THE CONTENDERS

🔐 ATLOCK v4.0	⚡ ATLOCK v5.0
### THE CURRENT FLAGSHIP - Publicly available - Established security features - File Guard and Password Vault - Intruder detection features - System lockdown functionality - Existing user-facing application Status: Released	### THE NEXT GENERATION - Currently under development - Expanded cryptographic architecture - More advanced vault and file-protection systems - Additional security monitoring capabilities - Recovery and maintenance improvements - Expanded authentication options Status: Building stage

Important: ATLOCK v5 is not publicly released. Its feature set is not final, and its current code represents the development state rather than a finished release specification.

🛡️ ROUND 2 — FEATURE-BY-FEATURE COMPARISON

Let's examine what each version actually brings to the table.

1️⃣ FILE PROTECTION

🔐 ATLOCK v4.0

ATLOCK v4 includes File Guard functionality built around Windows file permissions and its own application-level protection mechanisms.

Its documented capabilities include:

Protecting files through File Guard.
Authentication before removing protection.
Monitoring guarded files.
Responding to incorrect authentication attempts.
Applying Windows NTFS access controls.

The v4 code also includes a warning about a retained developer bypass. That is a material security consideration, not something that should be hidden from users.

⚡ ATLOCK v5.0

The current v5 development code introduces a more extensive file-protection architecture.

It includes:

Encrypted file containers.
Chunked AES-256-GCM encryption.
Authentication of encrypted data.
Key commitment checks.
Recovery mechanisms for Quick Lock items.
Container verification and repair functionality.
Key rotation functionality.
Protected temporary working copies.
Monitoring for guarded-container changes.

The current code also sets the guarded-item limit to 31, compared with 10 in v4.

The difference: v4 focuses on its established File Guard system, while v5's current implementation introduces a more comprehensive encrypted-container and recovery architecture.

2️⃣ PASSWORD VAULT

🔐 ATLOCK v4.0

The v4 Password Vault uses Fernet-based encryption and PBKDF2-HMAC-SHA256 key derivation.

Its documented functionality includes:

Master-password authentication.
Encrypted credential storage.
Adding and editing entries.
Deleting entries.
Locking the vault session.
Applying a hard lock after repeated failed authentication attempts.

⚡ ATLOCK v5.0

The current v5 code introduces a more extensive cryptographic foundation.

Its implementation includes:

Argon2id-based password-derived keys.
AES-256-GCM authenticated encryption.
Protected local state.
Vault maintenance and repair functionality.
Vault import and export commands.
Vault auditing.
Master-key rotation functionality.
Additional authentication and recovery mechanisms.

The difference: v5 moves beyond the v4 vault's Fernet/PBKDF2 design into a more extensive authenticated-encryption and state-protection architecture.

This is an architectural comparison, not a claim that every v5 component has already undergone independent security auditing.

3️⃣ INTRUDER DETECTION

🔐 ATLOCK v4.0

The v4 Intruder Ops system includes:

📸 Camera photo capture following an incorrect authentication attempt.

🎥 Short video capture following specified repeated failures.

🔔 Alarm sounds and security notifications.

🗂️ Local storage for captured media.

⚙️ Settings for controlling capture functionality.

⚡ ATLOCK v5.0

The current v5 code retains camera and video functionality while introducing additional handling for security events.

Its code includes:

Camera and video capture components.
Configurable security settings.
Security-event notifications.
An optional Telegram alert component.
Protected handling of certain local security data.

The difference: v5's current implementation connects intrusion-related functionality with a broader security-monitoring and notification architecture.

Camera availability, operating-system permissions, configuration, and network connectivity can affect how these features work.

4️⃣ SECURITY MONITORING

This is one of the most notable differences in the current development code.

🔐 ATLOCK v4.0

The v4 feature set focuses on:

System lockdown.
File Guard.
Password Vault.
Intruder Ops.
Settings and security notifications.

⚡ ATLOCK v5.0

The current v5 code contains additional security-monitoring components.

Component	Purpose
Windows Defender integration	Retrieve Defender status and initiate supported scans
Startup Watchdog	Monitor selected startup locations and identify changes
Ransomware Canary	Use decoy files to detect certain suspicious modifications
VirusTotal integration	Support file lookups using an API key
Audit verification	Verify supported ATLOCK audit data
Emergency disconnect	Provide a network-disconnection action
Process hardening	Apply selected Windows process mitigations on a best-effort basis

These components are present in the current development code. Their existence does not mean ATLOCK replaces Windows Defender or provides comprehensive antivirus protection.

The difference: v5's current architecture extends beyond protecting individual files and credentials into additional monitoring, auditing, and security-management functions.

🧠 ROUND 3 — AUTHENTICATION AND RECOVERY

🔐 ATLOCK v4.0

The current v4 code provides password-based authentication for its protected features, along with its existing lockout and recovery-related behavior.

⚡ ATLOCK v5.0

The current v5 code includes additional authentication and recovery components:

Windows Hello integration.
Time-based one-time password functionality.
Recovery codes.
Quick Lock recovery keys.
Password and passphrase generation.
Vault recovery and repair operations.
Key rotation and container verification.

These capabilities are part of the current implementation. Their availability and exact behavior may change before a public release.

🖥️ ROUND 4 — WHAT HAPPENS WHEN RAM USES ATLOCK?

Let's make this comparison practical.

Meet Ram, a Windows user who wants to protect personal documents and credentials.

He has two options:

Use the publicly available ATLOCK v4.0.
Consider the ATLOCK v5.0 development build.

We'll examine what changes in his workflow.

🔐 SCENARIO A — RAM USES ATLOCK v4.0

Ram installs the currently available version.

Situation 1: Ram wants to protect a document

He can use File Guard to protect a supported file.

ATLOCK v4 provides file-protection functionality and Windows NTFS access-control mechanisms.

Ram can authenticate when performing supported operations to remove protection.

Situation 2: Ram wants to store credentials

He can use the Password Vault to create and manage credential entries.

The v4 implementation uses Fernet-based encryption and PBKDF2-HMAC-SHA256 for its password-derived key.

Situation 3: Someone repeatedly enters an incorrect password

ATLOCK v4 includes incorrect-attempt handling, security notifications, and lockout behavior.

Its Intruder Ops functionality can also respond to specified failed-authentication events.

Situation 4: Ram wants additional security monitoring

He has v4's existing security functionality, but the broader collection of monitoring and maintenance components in the current v5 code is not part of the documented v4 feature set.

What Ram gets with v4

A publicly available security suite with established File Guard, Password Vault, lockdown, and intrusion-related functionality.

However, Ram should understand the documented developer-bypass issue in the v4 code before trusting it with sensitive information.

⚡ SCENARIO B — RAM USES THE CURRENT ATLOCK v5 DEVELOPMENT BUILD

Now imagine Ram is evaluating the current v5 code in a controlled development environment.

This is a hypothetical workflow, not a claim that v5 is publicly released or ready for general use.

Situation 1: Ram wants to protect a document

The current v5 implementation provides encrypted-container functionality using chunked AES-256-GCM.

It also includes container verification, key commitment checks, and recovery-related functionality.

That gives Ram a different protection architecture to evaluate compared with v4's existing File Guard implementation.

Situation 2: Ram wants to manage protected files

The current code includes Quick Lock functionality, recovery keys, recovery codes, and protected temporary working copies.

It also includes container repair and key-rotation operations.

The precise user experience and availability of these functions may change during development.

Situation 3: Ram wants stronger password-derived key protection

The current v5 code uses Argon2id for password-derived keys in relevant components.

It also introduces authenticated-encryption and protected-state mechanisms.

These are implementation changes. They should not be interpreted as proof that every possible attack is prevented.

Situation 4: Ram wants to monitor his system

The current development code contains Windows Defender integration, a Startup Watchdog, Ransomware Canary functionality, and VirusTotal lookup support.

These give Ram additional security-monitoring workflows to evaluate.

However, a canary is not a complete ransomware detector, and a file lookup service is not a replacement for endpoint protection.

Situation 5: Ram wants additional authentication and recovery options

The current code includes Windows Hello, TOTP, and recovery-related functionality.

The exact availability and behavior of these features remain subject to development and testing.

What Ram gets from the current v5 code

A broader, more extensively engineered security architecture to evaluate — but not a finished public product.

Ram should not assume that a development build is production-ready simply because it contains more components.

📊 ROUND 5 — THE COMPARISON MATRIX

Capability	ATLOCK v4.0	ATLOCK v5.0 current code
Public availability	Yes	No — development stage
File Guard	Available	Expanded protection architecture
Encrypted containers	Not the documented v4 design	Chunked AES-256-GCM
Password Vault	Fernet + PBKDF2	Expanded Argon2id-based architecture
Intruder Ops	Available	Present in current code
Windows Defender integration	Not in documented v4 feature set	Present
Startup Watchdog	Not in documented v4 feature set	Present
Ransomware Canary	Not in documented v4 feature set	Present
VirusTotal lookup	Not in documented v4 feature set	Present
Windows Hello	Not in documented v4 feature set	Present in current code
TOTP	Not in documented v4 feature set	Present in current code
Recovery functionality	Existing v4 behavior	Expanded recovery mechanisms
Container repair and key rotation	Not in documented v4 feature set	Present in current code
Finalized feature set	Released version	Not finalized

This table describes the supplied v4 source and current v5 development code. It does not represent independent security certification, a completed release audit, or a guarantee that all development features will ship.

⚠️ ROUND 6 — THE REALITY CHECK

Security software deserves honest communication.

More features do not automatically mean better security.

More cryptography does not automatically mean fewer vulnerabilities.

And a longer feature list does not prove that an application can defeat every attacker.

The current v5 source explicitly acknowledges several limitations:

A sufficiently privileged local attacker may still be able to modify the application or inspect its process memory.
Python cannot guarantee that every copy of sensitive data is erased from memory.
Secure deletion on SSDs cannot be guaranteed because of wear-levelling and storage behavior.
Rollback protections have limitations against sufficiently privileged attackers.
ATLOCK operates at the application layer; it does not use a kernel driver.
The current code is not code-signed.

These are important engineering considerations.

ATLOCK should be evaluated based on its actual implementation, threat model, testing, and security review — not marketing language alone.

🏁 FINAL ROUND — THE EVOLUTION OF ATLOCK

ATLOCK v4.0 represents the current publicly available flagship.

It brings together File Guard, Password Vault, system lockdown, and intrusion-related functionality in an established application.

ATLOCK v5.0 represents the next stage of development.

Its current code expands the architecture with authenticated encrypted containers, Argon2id-based key derivation, recovery and maintenance operations, and additional Windows security-monitoring integrations.

But v5 is still being built.

Its features are not finalized, and its current implementation should not be confused with a completed, independently audited release.

The real story isn't simply v4 versus v5. It's the engineering evolution between two stages of the same product.

🔒 ATLOCK v4.0

THE CURRENT FLAGSHIP

Publicly available. Ready for users to explore.

⬇️ DOWNLOAD ATLOCK v4.0

⚡ ATLOCK v5.0

THE NEXT CHAPTER

Currently under development.

Features and release plans are not final.

Stay tuned for future development updates.

🚀 Explore ATLOCK

GitHub Repository:

https://github.com/Akhouri-Anmol-Kumar/ATLOCK

Download the current public release:

https://github.com/Akhouri-Anmol-Kumar/ATLOCK/releases/download/v4.0/ATLOCK.zip

💬 YOUR TURN

If you were evaluating a security application, which areas would matter most to you?

🔐 File protection and encryption
🗝️ Password and credential management
🛡️ Security monitoring and intrusion alerts
♻️ Recovery, verification, and maintenance
⚙️ Authentication and ease of use

Share your thoughts in the comments.

ATLOCK is evolving. The development journey continues.

ATLOCK is an Akhouri Systems product developed by Akhouri Anmol Kumar.

ATLOCK v4.0 is the current public release. ATLOCK v5.0 is a development build; its features, behavior, and release plans may change. This article describes the supplied source code and does not constitute an independent security audit or a guarantee against data loss, malware, or unauthorized access.

🔒 ATLOCK v5: Building Beyond the File Lock

Akhouri Anmol Kumar — Sun, 20 Sep 2026 11:46:55 +0000

A new chapter in my Windows security project is taking shape.

A lot of software begins with a feature.

ATLOCK began with a problem worth solving: making file protection easier to access.

Now, I’m working on the next stage of that idea.

Introducing a preview of ATLOCK v5 — currently in development at Akhouri Systems.

⚠️ Development update: ATLOCK v5 has not been publicly released. The features discussed here are part of ongoing development and may change before release.

🧩 The idea: Make security tools easier to reach

Security-related tools can feel disconnected. Users may need to move between different interfaces and workflows to manage different tasks.

With ATLOCK v5, I’m exploring a more integrated experience for Windows.

The goal isn’t to claim that one application can replace every security product. It’s to make selected protection and utility workflows more accessible from one place.

Here’s a glimpse of what’s being built.

🛡️ 1. A broader Security Guard experience

ATLOCK v5 is being developed with a Security Guard area that brings several security-related utilities together.

The current implementation includes work on:

A Windows Defender dashboard integration
VirusTotal hash lookup
A startup-persistence watchdog
A ransomware canary concept that monitors designated decoy files

These features have different purposes and limitations. They are not a replacement for a dedicated antivirus engine, and their effectiveness depends on implementation, configuration, and the Windows environment.

Still, bringing these tools into a more accessible interface is an interesting engineering challenge.

⚡ 2. Less friction in the file-protection workflow

I’m also working on a Windows Explorer context-menu integration.

The idea is straightforward:

Right-click a file or folder → access ATLOCK actions.

Instead of always opening the main application first, users could access supported actions directly from Explorer.

It’s a small interaction change, but reducing unnecessary steps can make a tool easier to use.

🔐 3. Exploring stronger authentication and key protection

The current development code includes work involving:

AES-GCM encryption
Argon2id password-based key derivation
Windows DPAPI integration
Optional Windows Hello integration

These components serve different roles in the security design. Their presence alone does not establish that the application is secure; correct implementation, key handling, testing, and threat-model review remain essential.

That’s part of the work: not just adding features, but understanding what each component does and where its limitations are.

🧰 4. More than file protection

The current build also includes work on utilities such as:

A password vault
Configurable clipboard clearing
Notifications and settings
An emergency network-disconnect option

Some of these capabilities are still being refined. I’m keeping additional details private until there’s more to show.

👀 This is only a partial preview.

🏗️ Building in public — without pretending the work is finished

I want to share the development process while being clear about what is and isn’t ready.

ATLOCK v5 is not available for public download yet. Features may change, and the application still needs appropriate testing and refinement.

The aim is to build thoughtfully, communicate honestly, and avoid making exaggerated security promises.

📦 Want to explore ATLOCK today?

ATLOCK v4 remains the publicly available version.

You can explore the project and its releases here:

👉 Visit the ATLOCK GitHub repository

👉 Download ATLOCK v4

💬 Join the discussion

If you use Windows or build desktop software, I’d like to know:

What makes a security utility genuinely useful to you?

Is it a smoother workflow, better integration with Windows, understandable controls, or something else?

Share your thoughts below. They can help inform what I focus on as development continues.

🔐 ATLOCK v5 — The Next Evolution of Windows Security Is Being Built.

Akhouri Anmol Kumar — Sun, 20 Sep 2026 04:12:07 +0000

A new chapter is coming. And this time, we're thinking beyond file locking.

Some updates add features.

Some updates rethink what a product can become.

ATLOCK v5 is being built with the second idea in mind.

ATLOCK v5.0

TOTAL SECURITY SUITE

An Akhouri Systems Product

IN DEVELOPMENT · WINDOWS · SECURITY

🔒 Your files. Your device. Your control.

⚠️ First, an important announcement

ATLOCK v5 is currently under development.

It is NOT publicly released, and the features shown in this article are previews of the current development build, not a promise that every feature is final.

For now, ATLOCK v4.0 remains the publicly available version.

But behind the scenes?

We're working on something that takes ATLOCK in a broader direction.

And today, I'm revealing a glimpse of what's coming.

🛰️ 01 — From File Protection to a Broader Security Experience

ATLOCK started with a straightforward idea:

Protect files without making the experience unnecessarily complicated.

But the next question became:

What if file protection was only one part of the experience?

What if users could also access security tools, monitor certain suspicious activity, and manage important security functions from one desktop application?

That's the direction behind ATLOCK v5.

Not a claim that one application can replace every security product.

Not another promise of being "unhackable."

A broader Windows security experience, built around practical tools.

🔥 02 — A First Look at What's Coming

Here's a glimpse of the development build.

Some features are being revealed. Others are staying behind the curtain for now.

🛡️ A Security Guard dashboard

ATLOCK v5 is introducing a dedicated Security Guard interface.

The current build brings together several different security-related tools.

What you can expect to see:

🪟 Windows Defender dashboard integration — access security-related Defender information through ATLOCK.
🔍 VirusTotal hash checking — a way to look up file hashes using VirusTotal.
🧷 Startup Watchdog — monitor startup items and identify certain suspicious additions.
🪤 Ransomware Canary — deploy decoy files and monitor for certain modification or deletion patterns.

These are separate tools with different purposes. The canary, for example, is a detection mechanism, not a complete ransomware prevention engine.

But the bigger idea is simple:

Give users more security visibility without pretending that one homemade application replaces an entire antivirus platform.

⚡ Quick Lock — A different way to secure files

Remember when protecting a file meant opening an application, navigating through a window, and going through the usual workflow?

ATLOCK v5 is developing a Windows Explorer integration.

The concept:

Right-click a file or folder.
Select the ATLOCK security action.
Authenticate using a supported Windows sign-in method.
Secure or unlock the item through the Quick Lock workflow.

The current implementation supports Windows Hello authentication, with a Windows account password fallback when available.

And yes...

The goal is to make file protection feel more integrated into Windows itself.

No need to reveal every implementation detail today. 😉

🔑 A more developed security toolkit

ATLOCK v5 is also expanding its existing security functionality.

Here's a glimpse of the current development build:

Component	Development direction
Password Vault	Encrypted credential storage
Windows Hello	Native identity verification support
File Guard	Password/PIN-protected file encryption
Clipboard	Automatic clearing functionality
Intruder notifications	Security-related event notifications
Emergency Disconnect	A user-triggered network interface disable function

The emergency disconnect feature is particularly interesting because it introduces a manual response option.

It is not an automatic guarantee against ransomware, and it may require administrator permissions.

Still, it's another example of the direction we're exploring.

🧩 03 — Under the Hood: A Technical Glimpse

This isn't just a visual redesign.

The current development build uses several established Windows and cryptographic technologies.

🔐 Cryptographic components

AES-GCM for authenticated encryption.
Argon2id for password-based key derivation and password hashing.
Windows DPAPI for protecting selected locally stored secrets.
Windows Hello for supported identity verification workflows.

These technologies serve different purposes within the application. Their presence alone does not establish that the entire product is secure against every threat.

Security still depends on implementation quality, testing, recovery behavior, and the surrounding Windows environment.

And that's exactly why development and testing matter.

👀 04 — What I'm Not Revealing Yet

Here's where the preview ends.

There are still details I'm deliberately keeping out of this announcement.

I'm not revealing the complete implementation.

I'm not publishing every screen and workflow.

And I'm not turning this article into a complete technical specification.

Why?

Because this is a development-stage announcement.

I want to share meaningful progress without presenting an unfinished build as a finished product.

This is a glimpse, not the full reveal.

More details will come as development progresses.

🏗️ 05 — The Development Philosophy

ATLOCK is an Akhouri Systems product.

The direction remains centered on practical software, a focused desktop experience, and avoiding unnecessary bloat.

For v5, that means exploring how several security-related functions can work together while remaining understandable to the user.

It also means being honest about limitations.

No security product should be marketed as invulnerable.

No encryption algorithm can compensate for every possible implementation flaw.

And no single application can eliminate every security risk on a Windows computer.

The objective is to build something useful, test it properly, and improve it over time.

🔒 06 — ATLOCK v4.0 Is Available Right Now

While v5 is under development, you don't have to wait to try ATLOCK.

ATLOCK v4.0 is the current public release.

If you want to explore the project today, start here.

⚡ TRY ATLOCK v4.0

Windows Security · File Protection

⬇️ DOWNLOAD ATLOCK v4.0

View the GitHub repository

🚀 07 — The Road Ahead

ATLOCK v5 is not publicly released yet.

There is still development work ahead, and the current feature set may change before release.

But this is the direction:

A broader security toolkit. A more integrated Windows experience. More practical functionality.

And this is only the beginning of the preview.

If you're interested in Windows security, desktop software development, encryption, or building products independently, I'd genuinely like to hear your thoughts.

💬 Let's discuss:

What should a modern desktop security toolkit prioritize?
Would you use a right-click file protection workflow?
Which security-related tools deserve a place in a unified desktop interface?
What would you want to see tested before a public release?

Drop your thoughts in the comments.

🔐 ATLOCK v5.0

Not released. Not finished. Still being built.

The next chapter of ATLOCK is under development.

An Akhouri Systems Product

⬇️ Get ATLOCK v4.0

🔒 Your Files. Your Rules. Your Security.

Akhouri Anmol Kumar — Sat, 19 Sep 2026 11:48:37 +0000

🔒 Your Files. Your Rules. Your Security.

What if protecting a file didn't require uploading it somewhere, creating an account, or navigating through a complicated cloud dashboard?

What if your desktop security tools were right there on your Windows machine?

Meet ATLOCK v4.0 — An Akhouri Systems Product.

A Windows security application built around one idea:

Your personal files deserve more than being left accessible on your desktop.

⚫ NOT ANOTHER CLOUD DASHBOARD.

ATLOCK brings multiple security-related functions together in a desktop application.

No complicated cloud setup. No subscription required to download the current release.

Just a Windows application with a focused set of security features.

🛡️ WHAT'S INSIDE ATLOCK v4.0?

01 — FILE GUARD

Protect selected files using Windows-level access controls, with a fallback locking method where the Windows security APIs are unavailable.

02 — PASSWORD VAULT

A local vault for organizing sensitive entries, with Fernet-based encryption and password-derived keys.

03 — LOCKDOWN

A system-locking feature with a countdown and Windows-specific keyboard restrictions.

04 — INTRUDER OPS

Configurable security responses to incorrect password attempts, including notifications, sound alerts, and camera capture.

Camera functionality requires compatible hardware and supporting dependencies.

05 — SETTINGS

Control supported security-response options and configure application behavior.

⚙️ BUILT WITH A DIFFERENT MINDSET

ATLOCK is developed under Akhouri Systems, with an emphasis on desktop software and practical security-related functionality.

The goal isn't to turn every simple task into another account, subscription, or cloud dependency.

It's to build software that gives users more control over their own computing environment.

👨‍💻 BUILT BY AKHOURI SYSTEMS

ATLOCK is part of the software development work happening at Akhouri Systems.

The objective is straightforward:

Build useful software. Keep it accessible. Keep improving it.

And this isn't where development stops.

👀 ATLOCK v5 is on the horizon.

More details will be shared when the next version is ready for public release.

No fabricated launch date. No imaginary feature announcements. Just development, iteration, and the next milestone.

🔻 GET ATLOCK v4.0

Ready to explore the current release?

👉 DOWNLOAD ATLOCK v4.0

Product: ATLOCK v4.0

Developer: Akhouri Systems

Platform: Windows

Release: v4.0

💬 LET'S TALK SECURITY

What matters most to you in a desktop security application?

File access control?
Local password storage?
Privacy and data minimization?
A simple, understandable interface?
Transparent and auditable security mechanisms?

Share your thoughts in the comments.

I'm interested in hearing what people actually want from desktop security software.

ATLOCK v4.0 — An Akhouri Systems Product.

Built with the ambition to make desktop security more accessible.

Security shouldn't be another window you keep open.

Akhouri Anmol Kumar — Fri, 18 Sep 2026 11:00:22 +0000

🔒 ATLOCK v4

Security shouldn't be another window you keep open.

Your files are important.

Your credentials are important.

Your privacy is important.

So why should protecting them mean juggling multiple tools, extensions, passwords, and utilities?

ATLOCK takes a different approach.

One security suite.
One interface.
One layer of protection around the things that matter.

◼ FILES → LOCKED

ATLOCK v4 brings Windows-level file protection directly into the suite.

Protect sensitive files and make unauthorized access harder at the operating-system level.

No complicated workflow.

No endless configuration.

Select. Lock. Done. 🔐

◼ PASSWORDS → VAULTED

A password shouldn't sit around as ordinary text.

ATLOCK's Password Vault uses Fernet-based encryption with PBKDF2-HMAC-SHA256 key derivation to protect stored secrets.

Credentials belong behind a vault.

Not inside a random text file.

◼ UNAUTHORIZED ATTEMPTS → RESPONDED TO

ATLOCK doesn't stop at a lock screen.

Its Intruder Ops system can respond to suspicious attempts with:

📸 Camera capture
🎥 Short video capture
🔊 Audio alerts
🔔 Security notifications

Captured security media is saved into dedicated ATLOCK security galleries.

The idea is simple:

Don't just protect the door.
Know when someone is trying to open it.

◼ SYSTEM → LOCKED DOWN

ATLOCK v4 also includes a system lockdown layer designed for its lock screen, including restrictions against common task-switching routes and a Task Manager watchdog on Windows.

Because a security screen that can simply be bypassed through the usual desktop shortcuts isn't much of a security screen.

THIS IS ATLOCK v4.

Not a collection of random utilities.

Not another password manager with a fancy logo.

Not another “security app” that exists only inside its own window.

ATLOCK is built around the idea of turning security into a system.

And v4 is already here.

🔐 GET ATLOCK v4

⬇️ DOWNLOAD ATLOCK v4

Windows • v4.0 • Akhouri Systems

But we're not stopping at v4.

ATLOCK v5 is being built.

No full reveal yet.

No giant feature list.

Just a glimpse.

Something is changing underneath ATLOCK.

The next generation is moving closer to the Windows experience itself — with work already underway around Windows Hello authentication, instant Explorer-based Quick Lock, stronger secret handling, clipboard cleanup, security monitoring, watchdog mechanisms and ransomware-focused defenses.
But that's all you're getting for now.

ATLOCK v5

Not launched.
Not revealed.
Still being built.

👁️ You've seen the glimpse.

v4 is public.

v5 is coming.

The lock is evolving.

ATLOCK — An Akhouri Systems Product.

Download v4:
https://github.com/Akhouri-Anmol-Kumar/ATLOCK/releases/download/v4.0/ATLOCK.zip

Built by Akhouri Systems.
Made for Windows.
Built around security.

ATLOCK #AkhouriSystems #CyberSecurity #WindowsSecurity #Privacy #FileSecurity #PasswordVault #InfoSec #MadeInIndia #SoftwareDevelopment

Your image shouldn't have to leave your machine just because you want to edit it.

Akhouri Anmol Kumar — Thu, 17 Sep 2026 10:51:09 +0000

APIC

Think about the normal image-processing workflow.

Open an image → upload it → wait → process it → download it.

Now remove the upload step.

Then remove the account.

Then remove the “please install another tool for this one tiny operation” step.

That's the idea behind APIC — Advanced Image Processing Center.

But there's a twist:

APIC isn't just one application.

It's two interfaces around the same idea.

                 YOUR IMAGE
                     │
          ┌──────────┴──────────┐
          ▼                     ▼
    ┌─────────────┐       ┌─────────────┐
    │  APIC PC    │       │  APIC WEB   │
    │             │       │             │
    │  Desktop    │       │  Browser    │
    │  workflow   │       │  workflow   │
    └──────┬──────┘       └──────┬──────┘
           │                     │
           └──────────┬──────────┘
                      ▼
              IMAGE PROCESSING

No subscription wall.

No “create an account first.”

Just pick the environment you want.

🖥️ APIC for PC

The desktop edition is built like a proper desktop utility rather than a website pretending to be an app.

It has separate workflows for:

✎ Edit
⇄ Convert
↓ Compress
⌕ Search
Home / About
Drag & drop image opening
Keyboard shortcuts
Multi-image handling

The desktop application supports formats including PNG, JPG/JPEG, WebP, BMP, TIFF, GIF, ICO, HEIC and AVIF.

And the UI isn't trying to hide the fact that it's a desktop application.

It's deliberately structured around a sidebar + workspace model, with global shortcuts such as Ctrl+O, Ctrl+1 through Ctrl+5, and F1.

Download APIC for Windows

DOWNLOAD APIC →

.ZIP · WINDOWS · NO ACCOUNT NEEDED

🌐 Then I asked a different question:

What if APIC didn't need to be installed at all?

So APIC-Web happened.

Open a browser.

Drop an image.

Start processing.

The web edition runs image operations directly in the browser and includes tools for editing, conversion, compression and background removal.

And this isn't simply the desktop UI copied into HTML.

The web version goes further.

⚡ APIC-Web: the advanced laboratory

The browser version brings a deeper processing toolbox:

`EDIT`

Brightness.

Contrast.

Saturation.

Blur.

Filters.

Rotation.

Flip.

Live canvas processing.

`ADVANCED`

Manual image controls for more granular adjustments — the kind of controls normally associated with professional image-processing workflows.

`REMOVE OBJECT`

Paint over an unwanted object and let APIC attempt to reconstruct the surrounding area.

The implementation uses exemplar/texture-synthesis style patch filling rather than requiring a generative-AI server call.

`REMOVE BG`

This is where things get interesting.

APIC-Web uses on-device AI segmentation for background removal.

The project explicitly describes it as running on-device, with nothing uploaded to a server for that operation.

`CONVERT`

PNG → JPEG → WebP → BMP → ICO → PDF.

Six output formats.

No server round-trip required for the browser conversion workflow.

`COMPRESS`

This isn't just:

“Set quality to 70%.”

APIC-Web can search for the highest JPEG quality that fits a target file size.

So instead of asking:

“What quality should I use?”

you can ask:

“Make this fit under 200 KB.”

The implementation uses a binary-search approach across quality levels to find a suitable result.

🧠 And there's one detail I really like

APIC-Web has an actual edit history.

Not just a fake “Reset” button.

Committed operations can become history states, with undo/redo support and keyboard shortcuts.

The implementation keeps up to 40 history states.

That's the kind of tiny engineering decision users don't notice until they need it.

Then they really notice it.

Two versions. Different jobs.

	APIC for PC	APIC-Web
Installation	✅	❌
Desktop workflow	✅	❌
Browser workflow	❌	✅
Edit	✅	✅
Convert	✅	✅
Compress	✅	✅
Advanced processing	—	✅
Object removal	—	✅
AI background removal	—	✅
Drag & drop	✅	✅
Keyboard workflow	✅	✅

The point isn't that one replaces the other.

They solve different situations.

Working on a Windows machine for a longer session?

→ APIC for PC

Need to quickly process an image from a browser without installing anything?

→ APIC-Web

Need the more experimental/advanced browser toolbox?

→ APIC-Web

Want a dedicated desktop application?

→ APIC for PC

🔐 The philosophy

There are already thousands of image editors.

APIC isn't trying to win by having the longest feature list.

The idea is simpler:

Image processing should feel like a tool, not a ceremony.

Open.

Process.

Export.

Done.

And when possible, keep the processing close to the user instead of automatically turning every image into a server upload.

🚀 Try both

🖥️ APIC for Windows

Download APIC →

🌐 APIC-Web

Open APIC-Web →

One last experiment.

Take an image you normally wouldn't upload to an online editor.

Open APIC-Web.

Drop it in.

Process it.

Then ask yourself:

“Why was I uploading images for this in the first place?”

That's the problem APIC is trying to remove.

sudo rm -rf /cloud 🌩️ Meet APIC: The Anti-Cloud Image Engine

Akhouri Anmol Kumar — Wed, 16 Sep 2026 10:46:06 +0000

"Architecture over anecdotes. Performance over promises."

Most web-based image editors have a dirty secret: your pixels are someone else's problem. You upload, you wait, you hope the server doesn't compress your work into a muddy artifact, and you pray for data privacy.

We took a different approach. We deleted the server.

Meet APIC (Advanced Image Processing Center) — a studio-grade, zero-upload, local-first image processing engine. It runs entirely in your browser and is available as a native desktop application.

⚙️ The Stack: Four Protocols. Zero Round-Trips.

APIC isn't just a wrapper around a cloud API. It’s a fully on-device computational engine.

Protocol	Capability	The "Anti-Cloud" Advantage
`01_EDIT`	Curves, Levels, Sharpen, Filters, Crop	Live canvas rendering at 60fps. Manual, pixel-level control running entirely in your browser's memory.
`02_CONVERT`	PNG, JPEG, WebP, BMP, ICO, PDF	Six formats. Zero server round-trips. Your file never leaves your RAM.
`03_COMPRESS`	Smart Target-Size Search	Doesn't just apply a flat quality cut. It intelligently searches the quality spectrum to keep maximum detail at your exact KB budget.
`04_REMOVE_BG`	On-Device AI Segmentation	Cuts your subject out locally. No upload, no queue, no "processing..." spinner that lasts 5 minutes.

🖥️ The Desktop Experience: Unplugged & Unstoppable

Prefer it on your desk? The APIC Desktop App runs fully offline. It uses the exact same stack as the web version, rebuilt in PyQt6 for native performance.

✅ No sign-in required.
✅ No telemetry.
✅ No internet connection needed.

It’s the tool you open when you need to get work done, not when you want to negotiate with a SaaS paywall.

📥 Initialize Local Deployment

Ready to take your pixels back? Grab the latest Windows build directly from our repository.

(.ZIP · WINDOWS · NO ACCOUNT NEEDED)

🤝 Join the Local-First Movement

APIC is a product of Akhouri Systems, developed by Akhouri Anmol Kumar.

We believe the future of creative tools isn't in renting server space—it's in empowering the machine sitting right in front of you.

🔗 Explore the Repository: github.com/Akhouri-Anmol-Kumar/APIC
🌐 Try the Web Version: APIC

Drop a 💬 below if you believe in local-first software, or star the repo if you're ready to ditch the cloud.