Created, built and run by Lèo Liebenberg
Vikelus
We don't wait for your devices to get breached. We watch them so they don't.
- Feeds
- CISA KEV · NVD · EPSS
- Checks
- Installed version, per machine
- Approval
- Two engineers, every time
- Output
- Insurer-ready proof report
What it does
It finds the overlap nobody has time to find.
Somewhere in the gap between “the world published 300 new vulnerabilities this week” and “this specific laptop, in this specific office, is running the specific version that's being exploited right now” lives the entire job of vulnerability management.
Vikelus lives in that gap. It closes it every morning, automatically, across every device under management — and then it proves it did.
Not “this company runs Chrome.” This laptop runs this build.
How it works
Five steps, every morning.
-
01
Ingest
CISA's catalogue of vulnerabilities attackers are actively exploiting. New critical CVEs from NVD. EPSS exploit-probability scores that separate the genuinely dangerous from the merely alarming.
-
02
Inventory
Pull the real installed version of every application, on every managed device. Not what the licence says. Not what was deployed last quarter. What is on the machine, right now.
-
03
Match
Overlap the two, per machine. This is where the noise dies: hundreds of scary headlines collapse into the handful of things that are genuinely exposed on hardware you actually own.
-
04
Stage
Rank by real risk and open a patch workflow. Two engineers must approve before anything touches a server. Every step lands in a ticket automatically.
-
05
Prove
Re-verify the installed version. Log it. Ship the report that shows what was checked, what was affected, and what was closed — the paperwork the cyber insurer asks for at renewal.
The proof
Anyone can render a green tick.
The tick is worthless unless something underneath it can be checked, argued with, and proven. So a finding in Vikelus closes when the machine is actually fixed and the version proves it — and not one moment before.
Who built it
Vikelus was created by Lèo Liebenberg.
Lèo Liebenberg is the sole creator of Vikelus. The idea was his, and so was the build: he designed the architecture, wrote the version-matching engine, the proof pipeline and the reporting, and he runs it in production. It began as Vuln-Watch and was renamed to Vikelus.
He is also a co-founder and co-owner of Vikelus, alongside co-founder Reza Marvasti, who leads growth and the partner network. Vikelus is an independent platform, owned by its founders, and it runs today across the client base of F1 IT Solutions — the Cape Town managed-service provider where Lèo works as a cybersecurity technical engineer.
It's built on self-hosted n8n for orchestration, SuperOps for the live device and asset inventory, Cloudflare Pages for the app and client portal, the Telegram Bot API for the morning digest, and the Anthropic API for the plain-English explanations and executive summaries that land on the monthly reports.
Contact
Want to see it run?
I'm happy to walk you through what Vikelus actually does — on a real fleet, not a demo deck.