People ask about the name more than you’d think. Login Alert makes sense on its own, everyone gets that part immediately. It’s the X that throws people off. So here’s the actual story, not the tidied-up version.
I’ve always kept two laptops, one personal and one for work, and I’ve always had this small paranoia about both. Not hacking, nothing dramatic, just the mundane question of who’s actually in front of my machine when I’m not. I’d step out for coffee and wonder about it on the walk back. My cousin visited home once while I was out, and I had no real way of knowing whether he’d sat at my desk or never gone near it. Probably hadn’t. But not knowing bothered me more than it should have.
I mentioned this to a friend, half expecting her to think I was being strange about it. She wasn’t. She’d wondered the same thing about a colleague at her office, whether he was logging into her machine when she stepped away. Same question, different setting. That’s when it stopped feeling like my own oddly specific anxiety and started feeling like an actual gap.
So I looked for something that would just tell me. Not enterprise monitoring software built for a company with an IT department, just something simple for one person. I couldn’t find it. Plenty of tools existed for businesses. Nothing for someone who just wanted to know.
I’m a developer, so I built it myself, badly, as a weekend project. A basic script wired to Windows Task Scheduler, firing on login and sending me an email. It worked for exactly one scenario: someone logging in fresh. Nothing for a screen unlock, a failed password, or the machine simply powering on. I’d solved maybe a quarter of the question. So I rebuilt it properly in C#, hooking directly into the Windows events I actually cared about instead of one scheduled trigger. That version worked.
A few days into getting these emails, I realized something I probably should have thought of earlier. Knowing a login happened and knowing who actually did it are two different problems. An email that just said “a login occurred” didn’t tell me whether it was me forgetting I’d already unlocked the laptop, or someone else in the room entirely. So I added a webcam capture that fired the moment a login happened, a quick photo of whoever was actually sitting there. Then a screenshot of whatever was on screen right after, and a short clip of audio picked up around the machine in that moment. The alert stopped being “someone logged in” and started being “here’s who, here’s what they opened, here’s what was being said.” That’s roughly the point it stopped feeling like a notification and started feeling like actual evidence.
Then I ran into a much less technical problem. My email is a mess, and an alert buried in a crowded inbox isn’t much better than no alert at all. So I moved it to WhatsApp instead, wired through the Twilio API, since that’s a place I actually look at. A message would land the moment someone logged in, and I’d glance at it and know. Mostly it just confirmed nothing had happened, which was most of the time. That quiet confirmation was really the whole point.
I gave it to my friend, the one with the colleague worry. She started using it too, and it solved the same problem for her that it had for me.
Two people using something isn’t really a product, but it felt like one. I cleaned up the code and put it out publicly, expecting more or less nothing to happen.
Something did happen, just not what I expected. People signed up, and pretty quickly I noticed they weren’t all asking for the same thing. Small office owners wanted alerts in Slack or Teams, since that’s what they already had open all day for work. A run of requests came in for Discord, from people running home gaming setups, which took me a second to place until I remembered that Discord is basically a gamer’s notification center. And plenty of people wanted exactly what I’d wanted originally: email, WhatsApp, sometimes Telegram.
So I added the channels as the requests came in, one at a time, until the same login event could land wherever someone actually looked. Once it was clear some people didn’t want to go through a chat app at all, I built an Android companion app too, so the honest answer to “how do I get notified” could just be “however you want.”
Somewhere in the middle of all that, watching it stretch across offices and gaming setups and people with the exact worry I’d started with, it stopped feeling like a tool with an audience and started feeling like a tool with any audience. The worry had never really been specific to us in the first place.
Which brings me to the name. Login Alert is the easy part, it just says what the app does. The X is what people actually ask about, and the answer is simpler than it sounds. X was whoever needed this enough that I’d bother building it for them. First that was me, standing outside a coffee shop wondering about my own laptop. Then it was my friend, and the colleague she wasn’t sure about. Then it was everyone who showed up once this went public, asking for Slack, for Discord, for a version of the exact same worry I’d had.
X was never meant to be one fixed person. X is whoever needed the peace of mind, whoever’s reading this right now and already knows the feeling before I finish the sentence. If you’ve ever wondered the same thing about your own machine, that’s you. You’re the X.
That’s roughly where things stand today. Login AlertX now watches 23 different Windows events, logins, failed passwords, brute force attempts, screen lock and unlock, RDP sessions, and power states among them, and scores every one of them against your normal patterns, so a login at 3am from an unfamiliar network gets flagged very differently from the one you make every morning at nine. Every alert can still carry the webcam photo, the screenshot, and the audio clip that started all of this, along with the IP address, location, and network details behind it. Everything stays local and encrypted on your own device, nothing routed through anyone’s servers but yours. You can get it on email, WhatsApp, Telegram, Slack, Teams, Google Chat, or Discord, or straight through the Android companion app if you’d rather have it pushed to your phone with a full history you can scroll back through.
It’s crossed more than 10,000 downloads at this point, and you’ll find it on the Microsoft Store, Softpedia, MajorGeeks, and Uptodown, among other places.
None of that changes what it’s actually for, though. It’s still just trying to answer the same question I had outside that coffee shop, did anyone use this while I wasn’t looking. Everything else got built around getting you that answer as simply as possible.