LocknAlert didn't start in a boardroom. It started with a simple question: why should you keep paying monthly fees to access an alarm system you already own?
In December 2024, Raine had a logical idea. His home was already fitted with a Paradox alarm system — sensors covering every room, detectors watching every angle outside. He wanted to use those sensors for home automation: when the kitchen sensor picks up movement at 2am, turn on the kitchen light. When someone approaches the front door, light up the porch. The sensors were already there. The logic was obvious. The implementation, it turned out, was not.
Every solution he found came with a catch. Monthly subscription fees of R149–R200, just for remote access to your own alarm. Cloud-dependent platforms that stopped working the moment your internet dropped. Clunky apps with poor Home Assistant integration. Your alarm data — zone trips, arm states, movement history — sitting on someone else's server.
"You've already paid for the hardware. You own the sensors. Why does accessing your own alarm require a monthly debit order? It doesn't make sense."
With a computer science background and the stubbornness to solve things properly, Raine decided to build something himself. He dug into the Paradox serial protocol, figured out how to talk directly to the panel through its built-in TTL serial port, and started prototyping. Several months of tinkering, testing, and refining later, the LocknAlert Bridge had taken shape.
In August 2025, LocknAlert launched — not as a startup with investor backing, but as a South African product built by one person, solving a real problem that nobody else was solving correctly.
Built the hard way — by actually using it, testing it, and listening to the people who bought it.
The frustration hits. Every existing Paradox-to-Home Assistant solution either costs monthly fees, relies on cloud services, or has poor integration. The decision is made: build something better.
Months of prototyping. Understanding the Paradox serial protocol. Building the Bridge. Testing it on a real alarm panel, in a real home, until it worked reliably — no cloud, no subscriptions, no compromises.
LocknAlert launches. First customers. Real feedback. The product improves with every order. One person builds it, ships it, supports it — and answers the phone when you send a WhatsApp.
These aren't policies. They're the reasons LocknAlert exists.
When you buy a LocknAlert device, you own it completely. There are no debit orders. No annual renewals. No "upgrade to keep access." You paid once. It's yours. The idea that you should keep paying for something you physically own never made sense to us — and it still doesn't.
LocknAlert has zero access to your alarm data. It never leaves your home network. Your zone states, arm history, movement patterns — none of it touches our servers because we don't have servers for your data. Local-first isn't just a feature. It's how we built everything from day one.
Load-shedding is real. Internet outages happen. A smart alarm that stops working the moment the power or internet goes down isn't smart — it's a liability. LocknAlert keeps working through both. Because that's what South African homes actually need.
LocknAlert is Raine Pretorius — one engineer in Johannesburg who got frustrated, built something, and kept going. Every order is built by hand. Every support message gets a real reply. Got a question? It goes straight to the person who built it.