November 28, 2025
Missiles meet living rooms
OS Malevich – how we made a system that embodies the idea of simplicity (2017)
Missile‑grade home security? Fans cheer, geeks demand Linux answers
TLDR: Ajax launched a new RTOS-based security hub OS promising missile-level reliability, but commenters immediately questioned the swipe at Linux, asking why its real-time version wasn’t considered. The community is split between applauding the ambition and demanding technical receipts, making this a reliability vs. transparency showdown.
Ajax just unveiled OS Malevich, a new brain for its home security hub, bragging it’s “missile‑grade” reliable thanks to a real‑time operating system (RTOS)—a type of software that does tasks on strict deadlines, like elevators and car brakes. The crowd? Split and spicy. One camp is swooning over the ambition: “this feels like lab‑level tech shipped to your living room,” cheering the blend of research and real products. The other camp is clutching their penguin plushies, firing back: “Hold up—Linux can do real‑time too.” When the article claimed Linux isn’t used in pro security because tasks wait in a queue, commenters pounced, asking why the Linux real‑time kernel wasn’t even mentioned. Techies demanded receipts, expecting a side‑by‑side justification, not a drive‑by diss.
Memes flew fast: “Ballistic missiles in my smoke detector?”; “OS Malevich, but make it Grade 2 drama.” Folks loved the global wishlist—Norwegian instant fire‑alarm chaining, German standards, Italian installer roles, Malaysian smart‑home swagger—but also asked, can this ‘simple’ system scale without turning into spaghetti? In short: applause for the bold RTOS path, side‑eye for the Linux shade, and plenty of popcorn for the feature‑creep future. The security brain is here; the comment wars are just getting started.
Key Points
- •Ajax developed OS Malevich as a new hub operating system to improve reliability and scalability for its security system.
- •The team evaluated C, RTOS, and Linux; RTOS was chosen for strict timing and reliability, while C and Linux were rejected for scalability and safety concerns.
- •Development took 1.5 years and produced an OS supporting advanced multi-channel communications, radio device management, and robust alarm transmission.
- •Post-release market demands included direct hub connections, rapid fire alarm interlinking, Grade 2 compliance, keyboard support, home automation, and installer role separation.
- •Existing architecture limited rapid feature expansion, prompting a need for higher-level abstractions and separation between hardware and software to maintain RTOS reliability with greater scalability.