Urgent.News

650+ sources. One page. See who else covered it.

Editions โ–พ

Tech

I Built a Windows Security Suite That Doesn't Need Your Account

What if a security application didn't need your email? No account. No cloud dashboard. No telemetry. No subscription. Just a Windows executable running locally on your machine. That's the philosophy behind ATLOCK v4, a Windows security suite I've been building as a solo developer. ๐Ÿ‘‰ Try ATLOCK v4: [ https://akhouri-anmol-kumar.github.io/Akhouri-systems/ ] Why local-first? Security software hasโ€ฆ

ATLOCK v4 is a Windows security suite developed by solo developer Anmol Kumar. It aims to provide security features without requiring an email account, cloud dashboard, telemetry, or subscription. The software is designed as a local-first application, meaning it runs directly on the Windows PC without any cloud dependency or account creation.

The suite includes four main components: Password Vault, NTFS File Protection, Intruder Ops, and Local Security Alerts. The Password Vault uses Fernet with key derivation through PBKDF2-HMAC-SHA256 to store credentials locally, removing the need for cloud synchronization. NTFS File Protection leverages Windows' existing permissions model rather than relying on a custom encryption layer.

Intruder Ops monitors repeated unauthorized access attempts and gathers locally stored evidence and alerts. Local Security Alerts notify users of potential security issues.

ATLOCK is distributed as a standalone Windows executable, making it easy to download, run, configure, and use without any installer dependency, account creation, or server setup. The developer encourages users to try the software and provide feedback on additional security features they would like to see in a local-first Windows security suite.

Written by urgent.news from Dev.to's reporting โ€” not their text. Machine-written โ€” may contain errors; check the original before relying on it.

Read the original at dev.to โ†’

More in Tech

Why I open-sourced the tool I built "just for myself"

Why I open-sourced the tool I built "just for myself" It started as a selfish project: a phone remote for my own desktop agent. Three reasons made me push it public. The third one surprised me.

  • Created DeepSeek Phone Harness for personal task automation
  • Open-sourced tool after discovering a critical bug
  • Open-sourcing improved code quality and sharing practice

My container diagram had three boxes. The actual pipeline had seven hops.

Three boxes. That's what our C4 container diagram showed for the EPCIS batch upload flow in ALSC. Upload API. Processing Service. Notification Service. Clean. Presentable.

  • Initial container diagram had three boxes: Upload API, Processing Service, Notification Service
  • Actual pipeline involved seven separate hops, more complex than diagram suggested
  • Discrepancy highlighted oversight in initial design, async pipeline lacks dynamic end-to-end view

More from Sunday 16 August โ†’